Managing HP Serviceguard for Linux Ninth Edition, April 2009

The package should be running on the specified adoptive node.
4. Halt the package, then move it back to the primary node using the cmhaltpkg,
cmmodpkg, and cmrunpkg commands:
cmhaltpkg <PackageName>
cmmodpkg -e <PrimaryNode> <PackageName>
cmrunpkg -v <PackageName>
Depending on the specific databases you are running, perform the appropriate
database recovery.
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.
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
272 Troubleshooting Your Cluster