Good afternoon everyone,
Has anyone had any delay problems using LDAP with NetApp? We're trying to implement it for user mapping purposes. It seems to be working in general; however, I am having a strange problem. Whenever I first do a query to test the connection (getXXbyYY getpwbyname_r <username>), it comes back immediately with the response. When I try it again another time or two, it still works fine. But after the 3rd or 4th attempt, there is about a 35 second delay before the response appears, and this delay happens for every query thereafter. The same delay occurs when trying wcc -u (or -s) <username>. Even trying to map a drive encounters the delay (which is the main reason we can't use LDAP until this is resolved -- users won't sit for 35 seconds waiting for every drive to map).
I have worked with the team that manages our LDAP environment, and the logs on their side show our netapp server doing the query and exiting within 2 seconds. (So what is it waiting on??) I've enabled cifs.trace_login, but it's showing no errors once the information finally appears.
We're running ontap 7.0.6 (which means netapp is using SASL -- no SSL feature).
nswitch.conf on the netapp looks like:
hosts: files dns nis passwd: files ldap netgroup: files nis group: files ldap shadow: files ldap
As far as ldap options, I have ldap.servers set to the server, and ldap.ADdomain is left blank.
Any time I disable and re-enable LDAP on the NetApp server, the delay goes away until I run a couple queries...then it always starts up again.
I'd greatly appreciate any ideas
-Brian Beaird