Managing Serviceguard Eighteenth Edition, September 2010

Table 7-1 Verifying Cluster Components (continued)
CommentsTool or Command; More InformationComponent (Context)
Commands check that all IP
addresses configured into the
cluster are in each node's
/etc/hosts.
cmcheckconf (1m), cmapplyconf
(1m)
IP addresses (cluster)
cmcheckconf (1m), cmapplyconf
(1m)
See also “Verifying and Applying the
Package Configuration” (page 317).
Package IP addresses (package)
For LVM only, commands
check that file systems have
been built on the logical
volumes identified by the
fs_name parameter (page 307).
cmcheckconf (1m), cmapplyconf
(1m)
See also “Verifying and Applying the
Package Configuration” (page 317).
File systems (package)
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 317).
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.
Example
The short script that follows runs cluster verification and sends an email to
[e-mail] when verification fails.
#!/bin/sh
cmcheckconf -v >/tmp/cmcheckconf.output
if (( $? != 0 ))
then
mailx -s "Cluster verification failed" [e-mail] 2>&1 </tmp/cmcheckconf.output
fi
340 Cluster and Package Maintenance