Page created: 6 Nov 2019 |
Page updated: 25 Mar 2020
- We stop the ds-east-01.example.com:389 and ds-east-02.example.com:389 server instances and test searches through proxy-east-01.example.com.
Perform several searches against the Directory Proxy Server. Verify activity in each of the servers in the east location, ds-east-01 and
ds-east-02, by looking at the access logs. 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=*)"
Next, stop the Directory Server instance on
ds-east-01.example.com and ds-east-02.example.com using the stop-server command and
immediately retry the above searches. There should be no errors or noticeable
delay in processing the search.
root@proxy-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=*)"
- Check the access log to confirm that requests made to these servers are routed to the central servers, as these servers are the first failover location in the failover list for the ds-east-01 and ds-east-02 servers.
- Restart the Directory Server instance on ds-east-01.example.com and ds-east-02.example.com. Check their access logs to ensure that traffic is redirected back from the failover servers.