Managing HP Serviceguard A.11.20.20 for Linux, March 2014

Table 12 Verifying Cluster and Package Components (continued)
DescriptionTool or Command; More InformationComponent (Context)
A non-zero return value from any
script results the commands to fail.
cmcheckconf (1m), cmapplyconf
(1m)
External scripts and pre-scripts
(modular package)
If the package configuration file
contains NFS file system, it
validates the following:
• Connectivity to the NFS server
from all the package nodes.
• Export of share by the NFS
server.
• The status of the NFS daemons
on the NFS server.
NOTE: For the NFS file
system mount to be successful,
the NFS daemon must be
running on the NFS server.
cmcheckconf (1m), cmapplyconf
(1m)
NFS server connectivity (package)
7.1.12.2 Setting up Periodic Cluster Verification
You can use cron (1m) to run cluster verification at a fixed time interval. Specify the commands
to run in a crontab file (For more information, see the crontab (1) manpage).
NOTE: The job must run on one of the nodes in the cluster. The crontab –e command is used
to edit the crontab file. This must be run as the root user, because only the root user can run
cluster verification. The cron (1m) command sets the job’s user and group IDs to those of the
user who submitted the job.
For example, the following script 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
To run this script from cron, use the crontab -e command and create an entry in he crontabs
file. For example, the following entry runs the script at 8 a.m. on 20th of every month:
0 8,20 * * * verification.sh
For more information, see the crontab (1) manpage.
7.1.12.3 Limitations
Serviceguard does not check for the following conditions:
• Proper configuration of Access Control Policies. For more information about Access Control
Policies, see “Controlling Access to the Cluster” (page 158).
• File systems configured to mount automatically on boot (that is, Serviceguard does not check
/etc/fstab)
• Uniqueness of volume group major and minor numbers.
• Proper functioning of redundant storage paths.
• Consistency of Kernel parameters and driver configurations across nodes.
• Mount point overlaps (such that one file system is obscured when another is mounted).
210 Cluster and Package Maintenance