Current Entries: 0 Max Entries: 512 Entry Lifetime: 86400
I was wondering if anybody has tweaked this setting to be less than 24h, preferably something like 15min. If yes, was there any unexpected behaviour by the filer or is everything good? FYI, The filer I manage is an AFF8080 with CDOT 8.3.2P5. Thanks in advance for any response.
I work for NetApp doing ONTAP9 architecture and migration planning. The short answer is: Some people adjust the cache values, and it depends on how it will affect your environment based on LDAP server health/load, LDAP structure, NFS load, latency, etc.
Before adjusting it down, I'd say ensure your LDAP infrastructure and latency between the storage controller to LDAP is very good. Read up on LDAP server best practices on pg 40 of the Name Services Best Practices guide: http://www.netapp.com/us/media/tr-4379.pdf
Pgs 53 through 55 detail all the default and recommended cache values, there is also the generic point of contacting support before endeavoring to adjust the TTL.
If this helped out or answered your question, be sure to hit the Kudos / Mark as Answered button 😃
Hello. Apologies for the late response. Yeah, what you explain makes absolute sense and it's what one would expect. I just wanted to see how other fellow sys admins manage this situation when users are added and removed into AD/LDAP groups in a kind of a frequent basis and what their experiences were in case they reduced the LDAP related caches TTL.
The latency between the filer and the AD servers is extremelly low as they all run in a 10Gb LAN. Plus the CPU utilisation is very low (less than 10% average as far as I can see from the current and historical data in our monitoring system).
The two documents you mentioned are awesome. Thanks for sharing 🙂
After a couple of years this needs some updating. For those that do not know, ONTAP 9.3 and later introduce a change with regards to group caching in the form of the new Global Nameservice Caching functionality . The associated command is "name-service cache group-membership". For more information you can look the following KB: