That is usually because the LDAP server is not answering. It could also because you have incorrect credentials defined in your LDAP server so it is not answering.
i tried " aaa query server-name admin-DN "
but it gave me authentication failed , and tried show aaa authentication-server ldap test1 status m it gave me adminbound -> no .
can you clarify the credentials for me !!
Most ldap servers require you to define a user to "bind" to the LDAP directory. Have you seen the article here? http://community.arubanetworks.com/t5/Controller-Based-WLANs/How-do-I-configure-LDAP-on-the-Aruba-controller/ta-p/184056
In my opinion, LDAP is the least flexibile but most troublesome authentication method. I would look into doing Radius for your authentication, if possible.
yes i saw it m but its not clear ! any way thank you for your response .
There has to be a service account used to authenticate users. That is the "admin DN" account. You enter that account's password in the password field when you define the LDAP server. If you define that correctly, adminbound will become "Yes".
© Copyright 2024 Hewlett Packard Enterprise Development LPAll Rights Reserved.