Debug Size:

8.1 - Manual Failover Testing

To move a service from one node to another, the rsfcli command can be used in two ways:

Using rsfcli move:
romulus# /opt/HAC/RSF-1/bin/rsfcli –i0 move POOLA remus
This causes the following to happen: Or using rsfcli stop:
romulus# /opt/HAC/RSF-1/bin/rsfcli –i0 stop POOLA
This alternate method simply tells romulus to stop the service (running through steps 1-3 above). If remus has switchover mode for POOLA set to automatic, as soon as it sees the service is not running anywhere (and cannot run anywhere else), it will start the service after its RUNTIMEOUT countdown timer has expired.

Once a service has been moved elsewhere and is running successfully, the switchover mode of the previous node should be reset to automatic:
romulus# /opt/HAC/RSF-1/bin/rsfcli –i0 auto POOLA
The above procedures can be used to manually move RSF-1 services around the cluster. Other than for initial testing purposes, these procedures can be used for planned maintenance situations, load redistribution etc.

Automatic Failover Testing

Automatic failover testing is best achieved by faking a system crash of one of the nodes that is running one or more services using one of the following methods:
NOTE - The reboot command is not a recommended method for faking a system crash, as the shut down is not guaranteed to cleanly shut down any VIPs
As soon as communication via all heartbeat channels ceases, the surviving node, assuming switchover modes are set to automatic, will initiate countdown and failover of those services lost by the crash.
Prev Page
Next Page