Page created: 26 Jul 2021 |
Page updated: 7 Dec 2022
After you have tested connectivity, run a simulated failure of a load-balanced external server to verify that the Directory Proxy Server redirects LDAP requests appropriately.
In this procedure, stop the
ds-east-01.example.com:389 server instance
and test searches through
Perform several searches against the Directory Proxy Server.
Verify activity in each of the servers in the east location,
ds-east-02, by looking at the access logs.
Because you used the default load balancing algorithm of fewest operations, it's likely that all of the searches go to only one of the proxies.
The following simple search can be repeated as needed.
root@proxy-east-01: bin/ldapsearch \ --bindDN "cn=Directory Manager" \ --bindPassword password --baseDN "dc=example,dc=com" \ --searchScope base --useStartTLS "(objectclass=*)"
Stop the Directory Server instance on
ds-east-01.example.comusing the stop-server command and immediately retry the searches in step 1.Note:
There should be no errors or noticeable delay in processing the search.
root@ds-east-01: bin/stop-server root@proxy-east-01: bin/ldapsearch \ --bindDN "cn=Directory Manager" \ --bindPassword password --baseDN "dc=example,dc=com" \ --searchScope base --useStartTLS "(objectclass=*)"
Restart the Directory Proxy Server instance on
Check the access log to confirm that the Directory Proxy Server
started to include the
ds-east-01server in load-balancing within 30 seconds.
The default time is 30 seconds, but you can change this default.