Hi David,
Have you tried searching on AskF5.com for LDAP monitor with the Product filter set to BIG-IP LTM and the version set to your LTM version?
BEST PRACTICE: SOL9311 - Best Practices for LDAP Monitoring
BIG-IP LDAP Monitor configuration settings The BIG-IP LDAP monitor template allows you to configure the following settings: UserName / ... ... this behavior, refer to SOL9734: Search scope cannot be configured for LDAP monitors . Note: For more information about the monitor's individual fields, refer to the BIG-IP Configuration Guide or the Help
Feb 19, 2009
KNOWN ISSUE: SOL9735 - Referral chasing cannot be configured for LDAP monitors
Referral chasing cannot be configured for LDAP monitors SOL9735 116377 LDAP , monitor , pinger, health check, referral, reference, chase, follow, 9735, sol9735, ... By default, the LDAP application health monitor follows referrals and references when they are returned in response to a ...
Apr 27, 2009
KNOWN ISSUE: SOL9734 - Search scope cannot be defined for the LDAP monitor
Search scope cannot be defined for the LDAP monitor SOL9734 101283 LDAP , monitor , pinger, health check, scope, subtree, limit, restrict, level, 9734, ... By default, the LDAP application health monitor performs a single level scope search, but when the Mandatory Attributes ...
Apr 27, 2009
SOL3494 - The LDAP or LDAPS monitor may mark all nodes as down
The LDAP or LDAPS monitor may mark all nodes as down SOL3494 CR41589 3494, LDAP , LDAPS, SOL3494, down, monitor SOL3494 SOL3494 When defining LDAP or ... ... to configure the BIG-IP LTM system's /etc/hosts file in order for the LDAP or LDAPS monitor to work properly.
Sep 02, 2008
You could also check the LTM config guide for your version for details. If you run into problems after you've tried configuring something, can you post details of the monitor configuration and output from /var/log/ltm?
Thanks,
Aaron