Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 13 results
    • EMS error secd.ldap.noServers when using OpenLDAP with LDAPS
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/EMS_error_secd_ldap_noServers_when_using_OpenLDAP_with_LDAPS
      Applies to ONTAP 9 OpenLDAP Secure Lightweight Directory Access Protocol (LDAPS) Issue ONTAP is correctly connected to OpenLDAP server: vserver services name-service ldap check EMS logs shows recurren...Applies to ONTAP 9 OpenLDAP Secure Lightweight Directory Access Protocol (LDAPS) Issue ONTAP is correctly connected to OpenLDAP server: vserver services name-service ldap check EMS logs shows recurrent error: EMERGENCY secd.ldap.noServers: None of the LDAP servers configured for Vserver (mnas25-nfs-p1) are currently accessible via the network for LDAP service type (Service: LDAP (NIS & Name Mapping), Operation: NetgroupMembersFromName)
    • How to enable LDAPS on a CIFS SVM
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_enable_LDAPS_on_a_CIFS_SVM
      Applies to ONTAP 9.5+ LDAPS Description There is a need to enable LDAPS on a CIFS SVM
    • Periodic secd.ldap.noServers error messages in EMS after using start-TLS on port 636
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Periodic_secd_ldap_noServers_error_messages_in_EMS_after_using_start-TLS_on_port_636
      Active Directory (AD) LDAP server 4/29/2020 14:22:14 node-01 EMERGENCY secd.ldap.noServers: None of the LDAP servers configured for Vserver (vserver1) are currently accessible via the network for LDAP...Active Directory (AD) LDAP server 4/29/2020 14:22:14 node-01 EMERGENCY secd.ldap.noServers: None of the LDAP servers configured for Vserver (vserver1) are currently accessible via the network for LDAP service type (Service: LDAP (Active Directory), Operation: SiteDiscovery). LDAP server port specified in ONTAP ldap client configuration is set to 636 as per vserver services name-service ldap client show -fields port Configuring domain discovery to none does not resolve the issue
    • Can SnapCenter use LDAPs/636 or Signed LDAP binding?
      https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/Can_Snapcenter_use_LDAPS_636_or_Signed_LDAP_binding
      Applies to SnapCenter 4.0 - 4.5 LDAPS Answer Support for LDAPS over SSL is first introduced into SnapCenter starting in version 4.6 Additional Information SnapCenter 4.6 Release Notes (What’s new in S...Applies to SnapCenter 4.0 - 4.5 LDAPS Answer Support for LDAPS over SSL is first introduced into SnapCenter starting in version 4.6 Additional Information SnapCenter 4.6 Release Notes (What’s new in SnapCenter Software 4.6, pg. Support for LDAPS over SSL Support for LDAPS over SSL protocol to communicate with Windows active directory. Use of authorized CA certificate ensures that the communication is secure
    • Why after securing LDAP communication with LDAPS there are still connections with LDAP server on port 389?
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Why_after_securing_LDAP_communication_with_LDAPS_there_are_still_connections_with_LDAP_server_on_port_389
      Applies to LDAP LDAPS Domain Controller Discovery (DC Discovery) DC Discovery is the procedure that uses port 389 in communication with DC's while discovering LDAP servers Dynamic server discovery is ...Applies to LDAP LDAPS Domain Controller Discovery (DC Discovery) DC Discovery is the procedure that uses port 389 in communication with DC's while discovering LDAP servers Dynamic server discovery is used by ONTAP for discovering Domain Controller's (DC's) and their associated services, such as LSA, NETLOGON, Kerberos, and LDAP It discovers all the DC's, including preferred DC's, as well as all the DC's in the local site and all remote DC's every 4 hours What is Domain Controller Discovery?
    • SECD encounters a panic when using Secure LDAP (LDAPS)
      https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/SECD_encounters_a_panic_when_using_Secure_LDAP_(LDAPS)
      Applies to ONTAP 9.5+ Issue SECD encounters a panic when using LDAPS with the following error in EMS: Fri Aug 21 05:09:16 PDT [nodename: secd: ucore.panicString:error]: 'secd: Received SIGSEGV (Signal...Applies to ONTAP 9.5+ Issue SECD encounters a panic when using LDAPS with the following error in EMS: Fri Aug 21 05:09:16 PDT [nodename: secd: ucore.panicString:error]: 'secd: Received SIGSEGV (Signal 11) at RIP 0x806d86ec4 accessing address 0x10 (pid 67823, uid 0, timestamp 1566367572)' Fri Aug 21 05:09:16 PDT [nodename: spmd: spm.secd.process.exit:EMERGENCY]: Security daemon with ID 67823 exited as a result of signal signal 11. The service will attempt to restart.
    • LDAPS users cannot authenticate on OnCommand Insight
      https://kb.netapp.com/data-mgmt/OCI_Kbs/LDAPS_users_cannot_authenticate_on_OnCommand_Insight
      OnCommand Insight 7.3.9 + Linux installation (OCI) LDAPS is enabled in OnCommand Insight LDAPS users fail to authenticate on OCI with error in ldap.log: “2020-06-22 11:53:32,467 ERROR [default task-1]...OnCommand Insight 7.3.9 + Linux installation (OCI) LDAPS is enabled in OnCommand Insight LDAPS users fail to authenticate on OCI with error in ldap.log: “2020-06-22 11:53:32,467 ERROR [default task-1] ldap (LdapUser.java:666) - Failed to find user:<username>@<domain_name> url:ldaps://<ldaps_server_url> sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    • After upgrade to OnCommand Workflow Automation 5.1.x the authentication over LDAP does not work anymore
      https://kb.netapp.com/Legacy/OnCommand_Suite/After_upgrade_to_OnCommand_Workflow_Automation_5.1.x_the_authentication_over_LDAP_does_not_work_anymore
      OnCommand Workflow Automation ( WFA ) 5.1RC1 OnCommand Workflow Automation ( WFA ) 5.1 OnCommand Workflow Automation ( WFA ) 5.1.1 After Upgrading OnCommand Workflow Automation to version 5.1.x the LD...OnCommand Workflow Automation ( WFA ) 5.1RC1 OnCommand Workflow Automation ( WFA ) 5.1 OnCommand Workflow Automation ( WFA ) 5.1.1 After Upgrading OnCommand Workflow Automation to version 5.1.x the LDAP authentication fails, more specifically LDAP is affected. 2020-03-04 09:40:34,381 ERROR [com.netapp.wfa.ldap.LdapWrapper] (default task-5) Failed to find user in LDAP: javax.naming.CommunicationException: qbitdcp001.operation.lan:636 [Root exception is java.lang.NullPointerException]...
    • Unable to import LDAPs Certificate on the OnCommand Insight(OCI) server
      https://kb.netapp.com/data-mgmt/OCI_Kbs/Unable_to_import_LDAPs_Certificate_on_the_OnCommand_Insight_OCI_server
      Applies to OnCommand Insight(OCI) 7.3.x Issue Unable to import the LDAPs certificate in the OCI server.
    • OCUM : LDAPs authentication fails due to sha-1 certificate
      https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/OCUM___LDAPs_authentication_fails_due_to_sha_1_certificate
      LDAPs does not function with a SHA-1 certificate and Unified Manager shows error ERROR [admin] [default task-34] [service.logging.SimpleRemoteLoggingService|logOnServer] [c.n.n.c.u.a.e.ApplicationErro...LDAPs does not function with a SHA-1 certificate and Unified Manager shows error ERROR [admin] [default task-34] [service.logging.SimpleRemoteLoggingService|logOnServer] [c.n.n.c.u.a.e.ApplicationErrorHandler] Cannot establish communication to the host IP-Adress over SSL The client and server cannot communicate, because they do not possess a common Algorithm
    • E-Series SANtricity System Manager LDAP server communication fails using secure LDAP on initial install
      https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/E-Series_SANtricity_System_Manager_LDAP_server_communication_fails_using_secure_LDAP_on_initial_install
      Secure LDAP (For SANtricity Access Management Feature) LDAP server initial connection fails only while using LDAP secure port (i.e 636), but works with non-secure LDAP port (i.e 389). The connection f...Secure LDAP (For SANtricity Access Management Feature) LDAP server initial connection fails only while using LDAP secure port (i.e 636), but works with non-secure LDAP port (i.e 389). The connection failure is returned during the Add Directory Server step in SANtricity System Manager. The E-Series embedded Web Services Proxy logs (web-server-trace-log-%.7z) available in a support bundle and AutoSupport indicates the LDAP secure connection failure was result of certificate validation failure: