Using Serviceguard Extension for RAC, 10th Edition, April 2011

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
To run this script from cron, you would create the following entry in /var/spool/cron/
crontabs/root:
0 8,20 * * * verification.sh
See the cron (1m) manpage for more information.
Limitations
Serviceguard does not check the following conditions:
• Access Control Policies properly configured
• File systems configured to mount automatically on boot (that is, Serviceguard does not check
/etc/fstab)
• Shared volume groups configured to activate on boot
• Volume group major and minor numbers unique
• Redundant storage paths functioning properly
• Kernel parameters and driver configurations consistent across nodes
• Mount point overlaps (such that one file system is obscured when another is mounted)
• Unreachable DNS server
• Consistency of settings in .rhosts and /var/admin/inetd.sec
• Consistency across cluster of major and minor numbers device-file numbers
• Nested mount points
• Staleness of mirror copies
Online Reconfiguration
The online reconfiguration feature provides a method to make configuration changes online to a
Serviceguard Extension for RAC (SGeRAC) cluster. Specifically, this provides the ability to add
and/or delete nodes from a running SGeRAC Cluster, and to reconfigure SLVM Volume Group
(VG) while it is being accessed by only one node.
Online Node Addition and Deletion
Online node addition enables the addition or deletion of nodes in a SGeRAC cluster to or from
another running cluster. Node(s) can be added and/or deleted by changing the cluster
configuration. This is done by editing the cluster specification file and re-applying the configuration
to the already running cluster. For deleting online node(s), the node(s) needs to be halted before
deleting them from the cluster.
128 Maintenance