Recurrent LSA unavailable errors

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 68

Visibility:: Public

Votes:: 0

Category:: ontap-9

Specialty:: NAS

Last Updated:

Applies to

Ontap 9

Issue

Recurrent EMS messages for LSA server not being available similar to the following one

[?]  Thu Jul 17 13:20:11 +0300 [node-01: secd: secd.lsa.noServers:EMERGENCY]: None of the LSA servers configured for Vserver (svm1) are currently accessible via the network.

[?]  Thu Jul 17 13:20:11 +0300 [node-01: secd: secd.unexpectedFailure:error]: Unexpected SecD failure in Vserver "svm1". Details: Error: Lookup of CIFS account SID procedure failed   

[3001 ms] Successfully connected to ip 10.10.11.11, port 445 using TCP  

[  6016] Unable to connect to LSA service on dc1.example.com (Error: RESULT_ERROR_SPINCLIENT_COMMAND_TIMED_OUT)  

[  6016] Successfully connected to ip 10.10.11.12, port 445 using TCP   

[  9021] Unable to connect to LSA service on dc2.example.com (Error: RESULT_ERROR_SPINCLIENT_COMMAND_TIMED_OUT)  

[  9021] No servers available for MS_LSA, vserver: 4, domain: example.com. **

[  9021] FAILURE: Unable to make a connection (LSA:EXAMPLE.COM), Result: RESULT_ERROR_SECD_NO_SERVER_AVAILABLE  

[  9023] Could not find Windows SID 'S-1-5-21-123456789-1234567-123456789-1234'   

[  9023] SID lookup failed   [  9023] Retry requested, but the retry window (7000 ms) has expired; giving up.

A packet trace will confirm that domain controllers are either responding to the smb negotiate command after more than 3 seconds or that DC is responding to a session setup with STATUS_INSUFF_SERVER_RESOURCES