topic Re: Multiple EMS Events : None of the LSA servers configured for Vserver are currently acessible in ONTAP Discussions

Multiple EMS Events : None of the LSA servers configured for Vserver are currently acessible

krishna556 — Wed, 04 Jun 2025 13:57:01 GMT

I see multiple EMS events logged into cluster from multiple vservers. Any way we can troubleshoot this issue.Any direction is appreciated.

Event:

secd.lsa.noServers: None of the LSA servers configured for Vserver are currently accessible via the network.

Message Name:

secd.lsa.noServers

Sequence Number:

329062

Description:

This message occurs when none of the configured LSA servers are accepting connections.

Action:

Ensure that all configured LSA servers are responding to requests. Ensure that there are no networking issues stopping the cluster from communicating with the configured LSA servers.

Re: Multiple EMS Events : None of the LSA servers configured for Vserver are currently acessible

Dr_Goldman — Thu, 08 Mar 2018 07:26:24 GMT

Same to me.

Re: Multiple EMS Events : None of the LSA servers configured for Vserver are currently acessible

maffo — Mon, 12 Mar 2018 11:57:16 GMT

Hi krishna556 and Dr_Goldman,

what version of ONTAP are you currently using? This might be an instance of BURT 1041972, in which case it is an internal ONTAP issue which is addressed starting with ONTAP 9.1.

If you confirm that there is no issue accessing the data from the clients, then it can also be safe to ignore those messages.

For further information please see https://kb.netapp.com/app/answers/answer_view/a_id/1005337.

Lorenzo

Re: Multiple EMS Events : None of the LSA servers configured for Vserver are currently acessible

GidonMarcus — Mon, 12 Mar 2018 14:07:17 GMT

Hi @maffo 🙂

@Dr_Goldman @krishna556 see also https://community.netapp.com/t5/Data-ONTAP-Discussions/secd-conn-auth-failure/m-p/138372#M30515 in case you already on the fixed version that @maffo suggested.

Re: Multiple EMS Events : None of the LSA servers configured for Vserver are currently acessible

geelsu — Wed, 13 Feb 2019 14:32:55 GMT

Re-addressing this issue which just appeared in our events. They started occurring yesterday after our Domain Functional Level was raised on all our Domain Controllers due to them all being upgraded to Windows 2016 i.e. level 7 when a dsquery is performed.