Home > Storage > ObjectScale and ECS > Product Documentation > Dell ECS with NGINX (OpenResty) > Validation
Start the S3 Browser to validate the setup. Since the S3 browser is using the DNS entry name, “os.ecstme.org”, no additional modifications are needed. Then, validate the redundant setup by shutting down the primary OpenResty service by issuing a “/usr/local/openresty/bin/openersty –s stop”. Once the secondary server recognizes that the primary is down, the secondary picks up the Virtual IP as exemplified in Figure 65. Access to the objects on ECS should still be available using S3 Browser since the secondary load balancer is handling the requests. Similarly, with the NFS client, the mount point should not be affected when the primary load balancer goes down.
Syslog (/var/log/syslog) can also be viewed on each server. Figure 66 shows a sample log file listing the different states on the primary OpenResty server during a failure and after it came back online. When keepalived started, state was initially MASTER and then when check_slb failed, state transitioned to BACKUP and once it started up again, it re-claimed MASTER state. Similar state transitions can be observed on the secondary syslog file. The syslog file can also provide clues if an error occurred in startup of keepalived.