| Section | |||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
To verify the functionality of the high availability setup on your SONARPLEX devices, follow these steps:
On SONARPLEX HA Slave
- Open User Webinterface > Monitoring > Services
- See the just created HA service check to report "OK" with a note on syncronized files, for example:
| Code Block |
|---|
Failover behavior: automatic, HA mode 0: Monitor process is up, last complete syncronization: 2014-08-20 08:13:28 (302 files) |
On SONARPLEX HA master
- If the syncronization is complete, shut down the SONARPLEX HA master device to test HA functionality.
...
The SONARPLEX HA slave is about to reboot with all configurations, log files and graphs from the last complete syncronization.
How to trigger a failover manually
There are three ways to trigger a manual failover in case of a functionality test or a scheduled maintenance. These all result in the slave SONARPLEX becoming the master SONARPLEX.
Shutdown the HA master SONARPLEX
The first method is to shutdown the HA master SONARPLEX completely. To do this, follow these steps:
> Status > SummaryInsert excerpt _OpenAdminWeb _OpenAdminWeb nopanel true - Click on "Click here to shut your appliance down"
- Wait for the HA slave SONARPLEX to take over
Stop the HA master SONARPLEX monitoring process
The next way to trigger a manual failover is to stop the monitoring process on the HA master SONARPLEX:
> Status > MonitorInsert excerpt _OpenAdminWeb _OpenAdminWeb nopanel true - Click on "Stop the monitor process"
- Wait for the HA slave SONARPLEX to take over
Disconnect from the network (not recommended)
The last way is to just disconnect the HA master SONARPLEX from the network so the HA slave SONARPLEX won't recognize it anymore. This is not recommended as the monitoring procss on the former HA master SONARPLEX is still running and you can end up with inconsistent graphs and logs, once the connection has been re-established.
- Disconnect the ethernet connection from the HA master SONARPLEX
- Wait for the HA slave SONARPLEX to take over
How to switch back after failover
If a failover has taken place and all problems have been solved, many wish to switch back to the original state of the setup (former slave being slave and former master being master again). This can be done simply by starting both SONARPLEX appliances and having them connected to your network in a way that they can communicate with each other. The former HA slave SONARPLEX will notice the HA master SONARPLEX to be back online and automatically synchronizes the collected graphs and log files. After completion, it will recover its former configuration with the only check being the HA master check.
| Info |
|---|
Only log files and graphs are synchronized back to the HA master SONARPLEX! Changes in configuration done on the HA slave SONARPLEX while running as HA master are not getting transferred back and will be lost! If you made changes to the config, create a backup and save it prior to the switchback. |
How to proceed in case of hardware failures/RMA
If one of your HA members suffers a hardware failure and needs to be replaced, contact support@azeti.net for assistance in creating an RMA. The following article describes the procedure after receiving your RMA replacement device.
TODO