Managing HP Serviceguard A.11.20.10 for Linux, December 2012

You can also test the package manager using generic resources. Perform the following procedure
for each package on the cluster:
1. Obtain the generic resource that is configured in a package by entering
cmviewcl -v -p <pkg_name>
2. Set the status of generic resource to DOWN using the following command:
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 211)).
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.
8.1.2 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.
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.
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 the original node:
cmhaltpkg <pkgname>
cmmodpkg -e -n <originalnode>
cmrunpkg <pkgname>
Depending on the specific databases you are running, perform the appropriate database
recovery.
6. Repeat this procedure for all nodes in the cluster one at a time.
8.2 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. For information
about disk monitoring, see “Creating a Disk Monitor Configuration” (page 191). In addition, the
following should be monitored for errors or warnings of all kinds:
• CPUs
• Memory
• NICs
• Power sources
242 Troubleshooting Your Cluster