HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

cmsetresource -r <res1> –s down
3. To view the package status, enter
cmviewcl -v
The package should be running on the specified adoptive node.
4. Move the package back to the primary node (see “Moving a Failover Package ” (page 286)).
NOTE: If there was a monitoring script configured for this generic resource, then the monitoring
script would also be attempting to set the status of the generic resource.
Testing the Cluster Manager
To test that the cluster manager is operating correctly, perform the following steps for each node
on the cluster:
1. Turn off the power to the node SPU.
2. To observe the cluster reforming, enter the following command on some other configured
node:
cmviewcl -v
You should be able to observe that the powered down node is halted, and that its packages
have been correctly switched to other nodes.
3. Turn on the power to the node SPU.
4. To verify that the node is rejoining the cluster, enter the following command on any configured
node:
cmviewcl -v
The node should be recognized by the cluster, but its packages should not be running.
5. Move the packages back to original node (see “Moving a Failover Package ” (page 286)).
6. Repeat this procedure for all nodes in the cluster one at a time.
Testing the Network Manager
To test that the network manager is operating correctly, for each node on the cluster do the following:
1. To identify primary and standby lan cards on the node, enter
lanscan
and then
cmviewcl -v
2. Disconnect the LAN connection from the Primary card.
3. Verify that a local switch has taken place so that the Standby card is now the Primary card.
In Serviceguard Manager, check the cluster properties. On the command line, use cmviewcl
-v.
4. Reconnect the LAN to the original Primary card, and verify its status. In Serviceguard Manager,
check the cluster properties. On the command line, use cmviewcl -v.
Monitoring Hardware
Good standard practice in handling a high availability system includes careful fault monitoring so
as to prevent failures if possible or at least to react to them swiftly when they occur. The following
should be monitored for errors or warnings of all kinds:
• Disks
• CPUs
• Memory
322 Troubleshooting Your Cluster