stopped svm with "secd.ldap.connectFailure". Why'

brauntisc — Thu, 05 Jun 2025 04:30:21 GMT

Hi All

Can someone explain me following behaviour?

Have a stopped SVM:

vserver show -fields admin-state
vserver admin-state
----------- -----------
svm0007 stopped

Also cifs is down:

cifs show -vserver svm0007

                         Vserver: svm0007
                         CIFS Server NetBIOS Name: SVM0007
                         NetBIOS Domain/Workgroup Name: PROD
                          Fully Qualified Domain Name: PROD.COM

           Default Site Used by LIFs Without Site Membership:
                         Authentication Style: domain
                        CIFS Server Administrative Status: down

But I become following Message from the Node:

Filer: stc0002

Time: Thu, Apr 23 03:37:05 2015 +0200

Severity: LOG_ERR

Message: secd.ldap.connectFailure: vserver (svm0007) could not make a connection over the network to LDAP server (xxxxxxx) at address

(xx.xx.xx.xx) and received error (Can't contact LDAP server)

Description: This message occurs when the server could not establish a TCP connection to a Lightweight Directory Access Protocol (LDAP) server.

Action: From a LDAP client workstation, make sure that the LDAP server is responding to requests. Also make sure that the portmapper on the LDAP server is responding to requests. Make sure that there are no networking issues stopping the cluster from communicating with this LDAP server.

Source: secd

Index: 7455291

Why try a stopped SVM to connect to AD?

TIA

Thomas

topic stopped svm with "secd.ldap.connectFailure". Why' in ONTAP Discussions

stopped svm with "secd.ldap.connectFailure". Why'