An IP load balancer, is often used to load balance Directory Servers. (Although far better and feature rich load balancing can be achieved with Sun Java System Directory Proxy Server).
If you choose to use a load balancer such as a BIG-IP F5, then please configure the F5 as follows:
Create an LDAP monitor that will execute a bind against the Directory Server. This is preferable to a standard TCP health check because:
- A simple TCP health check does not perform as complete an LDAP operation as a BIND
- The LDAP server does not know how to handle the simple TCP health check properly and thus in your Sun Directory Server logs you will likely see 4164 or 4166 errors.
- ‘user name’: enter an LDAP user that has no rights to important data in the Directory, ideally an ACI that only gives privileges to the use and nothing else. This ensures that if anyone compromises these credentials they cannot access other data. Sample ACI that only allows the F5 user to modify their own password.
aci: (targetattr = "userPassword") ( version 3.0; acl "allow
userpassword self modification"; allow (write) userdn = "ldap:///self";)
- ‘password’: the password for the user
- ‘Base’: base DN
- ‘Filter;: if your user is in it’s own OU no need to filter anything
- ‘Security’: select yes if you wish to test LDAPS (LDAP over SSL)
Complete the simple F5 configuration web form with relevant details from your Directory Server.