After you have installed and configured the WebAccess Agent in your Heartbeat cluster, and the WebAccess Application with your Web server, you can use the following methods to test whether the WebAccess Agent fails over as expected:
In the HA Management Client, select a node where the WebAccess Agent is running, then click . The WebAccess Agent should fail over to another node and start running again. This can also be done from the command line using the crm_standby utility.
Using the crm_resource utility, manually migrate a node where the WebAccess Agent is running.
If you receive the error Unmanaged on node, see Step 7 in Testing Your WebAccess Agent Installation on Each Node for troubleshooting assistance.
If you have set up your Heartbeat cluster in a test situation first, you can also use the following methods for testing WebAccess Agent failover:
Power off the node where the WebAccess Agent is running. The WebAccess Agent should fail over to another node and start running again.
Simulate the WebAccess Agent stopping unexpectedly (kill -9 agent_PID). If you have configured the WebAccess Agent for automatic restart, as described in Enabling Automatic GroupWise Agent Restart, the agent should start running again on the same node.
WARNING:These last two tests should not be performed on a production system because they can result in damage to GroupWise databases.