Managing HP Serviceguard A.11.20.20 for Linux, May 2013

NOTE:

• You can consider setting up a cron (1m) job to run the cmcheckconf command regularly.

For more information, see “Setting up Periodic Cluster Verification” (page 210).

• These new checks are not done for legacy packages. For information about legacy and

modular packages, see Chapter 6: Configuring Packages and Their Services (page 169).

• The cmapplyconf command performs the same verification as the cmcheckconf command.

• The extent of logging can be controlled using the verbosity and log levels. Higher the level of

verbosity, higher is the extent of logging. For example, to verify the cluster configuration and

package files using the -v (verbosity) options use:

◦ cmcheckconf -v OR cmcheckconf –v 1 — This command displays error and

warning messages (if any) for the type of checks being performed, such as storage,

network, and so on. It also displays the status of each check as OK or FAIL.

◦ cmcheckconf -v 2 — This command display errors and warning messages along

with informational and success message.

For more information, see the cmcheckconf (1m) manpage.

7.1.12.1 Verifying Cluster and Package Components

Table 12 describes how to verify each cluster and package component, the command or tool to

use and its description.

Table 12 Verifying Cluster and Package Components

DescriptionTool or Command; More InformationComponent (Context)

Verifies for the following:

• existence

• availability across all the nodes

where the package is

configured to run.

• same physical volumes across

all the nodes where the

package is configured to run.

• same volume group across all

the nodes where the package

is configured to run.

NOTE: The volume group

verifications are ignored in

serviceguard-xdc and Metrocluster

environment.

cmcheckconf (1m), cmapplyconf

(1m)