Skip to main content
NetApp Knowledge Base

LDAP status down during domain controller upgrade

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9.17.1P7
  • LDAP

Issue

  • Vservers show LDAP status as down during domain controller upgrades and do not fail over to other available LDAP servers
  • Authentication failures for SMB and NFS users observed
  • Service disruption reported for affected Vservers
  • EMS logs show repeated connection failures to domain controllers on ports 389 and 88
  • Example error messages:
    • Vserver:HKGPROD03SVM01
    • LDAPStatus:down
    • LDAPStatusDetails:Error: Validate the Ldap configuration procedure failed
    • [0ms] Hostname found in Name Service Cache
    • [0] Resolved LDAP servers: 10.133.193.34
    • [1] Successfully connected to ip 10.133.193.34, port 389 using TCP
    • [13] FAILURE: Could not authenticate as 'hkgnasldap_svc@JEFFERIES': Cannot find KDC for requested realm (KRB5_REALM_UNKNOWN)
    • [20] Unable to connect to LDAP(NIS&NameMapping) service on hk.ad.jefco.com (Error: Strong(er) authentication required)
    • [20] No servers available for LDAP_NIS_AND_NAME_MAPPING
    • [20] Unable to make a connection (LDAP(NIS&NameMapping):), Result: RESULT_ERROR_SECD_NO_SERVER_AVAILABLE

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.