Managing Serviceguard A.11.20, March 2013

Table 14 Verifying Cluster Components (continued)
CommentsTool or Command; More InformationComponent (Context)
as ownership, content, etc., use
cmcompare (1m).
Commands check that each node
has a working physical connection
to the disks.
cmcheckconf (1m), cmapplyconf
(1m)
See also “Verifying and Applying the
Package Configuration” (page 263).
VxVM disk groups (package)
Commands check that the
mount-point directories specified
cmcheckconf (1m), cmapplyconf
(1m)
Mount points (package)
in the package configuration file
See also “Verifying and Applying the
Package Configuration” (page 263).
exist on all nodes that can run the
package.
Commands check that files
specified by service commands
cmcheckconf (1m), cmapplyconf
(1m)
Service commands (package)
exist and are executable. Service
See also “Verifying and Applying the
Package Configuration” (page 263).
commands whose paths are nested
within an unmounted shared file
system are not checked.
Commands check that all IP
addresses configured into the
cmcheckconf (1m), cmapplyconf
(1m)
IP addresses (cluster)
cluster are in each node's /etc/
hosts.
cmcheckconf (1m), cmapplyconf
(1m)
Package IP addresses (package)
See also “Verifying and Applying the
Package Configuration” (page 263).
For LVM only, commands check
that file systems have been built on
cmcheckconf (1m), cmapplyconf
(1m)
File systems (package)
the logical volumes identified by
See also “Verifying and Applying the
Package Configuration” (page 263).
the fs_name parameter
(page 255).
cmcheckconf (1m), cmapplyconf
(1m)
Generic resources (package)
See also “Verifying and Applying the
Package Configuration” (page 263).
Commands check that configured
resources are available on each
node that can run the package.
cmcheckconf (1m), cmapplyconf
(1m)
See also “Verifying and Applying the
Package Configuration” (page 263).
EMS resources (package)
A non-zero return value from any
script will cause the commands to
fail.
cmcheckconf (1m), cmapplyconf
(1m)
External scripts and pre-scripts
(modular package)
Setting up Periodic Cluster Verification
You can use cron (1m) to run cluster verification at a fixed interval. Specify the commands to
run in a crontab file (see crontab (1)).
NOTE: The job must run on one of the nodes in the cluster. Because only the root user can run
cluster verification, and cron (1m) sets the job’s user and group ID’s to those of the user who
submitted the job, you must edit the file /var/spool/cron/crontabs/root as the root user.
280 Cluster and Package Maintenance