Managing HP Serviceguard A.11.20.20 for Linux, March 2014

8 Troubleshooting Your Cluster
This chapter describes how to verify cluster operation, how to review cluster status, how to add
and replace hardware, and how to solve some typical cluster problems. Topics are as follows:
• Testing Cluster Operation
• Monitoring Hardware (page 254)
• Replacing Disks (page 255)
• Replacing LAN Cards (page 256)
• Replacing a Failed Quorum Server System (page 257)
• Troubleshooting Approaches (page 258)
• Solving Problems (page 261)
• “Troubleshooting serviceguard-xdc package” (page 266)
• Troubleshooting Serviceguard Manager (page 267)
8.1 Testing Cluster Operation
Once you have configured your Serviceguard cluster, you should verify that the various components
of the cluster behave correctly in case of a failure. In this section, the following procedures test that
the cluster responds properly in the event of a package failure, a node failure, or a LAN failure.
CAUTION: In testing the cluster in the following procedures, be aware that you are causing
various components of the cluster to fail, so that you can determine that the cluster responds correctly
to failure situations. As a result, the availability of nodes and applications may be disrupted.
8.1.1 Testing the Package Manager
To test that the package manager is operating correctly, perform the following procedure for each
package on the cluster:
1. Obtain the PID number of a service in the package by entering
ps -ef | grep <service_cmd>
where service_cmd is the executable specified in the package configuration file (or legacy
control script) by means of the service_cmd parameter (page 183). The service selected must
have the default service_restart value (none).
2. To kill the service_cmd PID, enter
kill <PID>
3. To view the package status, enter
cmviewcl -v
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.
8.1 Testing Cluster Operation 253