Designing Disaster Tolerant High Availability Clusters, 10th Edition, March 2003 (B7660-90013)

Building a Continental Cluster
Building the ContinentalClusters Configuration
Chapter 5 237
The following sequence could provide meaningful notifications, since a
change of state is possible between notification intervals:
MONITOR_PACKAGE_NAME ccmonpkg
MONITOR_INTERVAL 1 MINUTE
...
CLUSTER_EVENT LACluster/UNREACHABLE
CLUSTER_ALERT 3 MINUTES
NOTIFICATION CONSOLE
"3 Minute Alert: LACluster Unreachable"
CLUSTER_ALERT 5 MINUTES
NOTIFICATION CONSOLE
"5 Minute Alert: LACluster Still Unreachable"
CLUSTER_ALARM 10 MINUTES
NOTIFICATION CONSOLE
"ALARM: LACluster Unreachable after 10 Minutes: Recovery
Enabled"
A rule of thumb is that the notification intervals should be multiples of
the monitor interval.
Checking and Applying the ContinentalClusters
Configuration
After editing the configuration file on the primary cluster, halt any
monitor packages that are running, then use the following steps to apply
the configuration to all nodes in the continental cluster.
1. Use the following command to verify the content of the file:
# cmcheckconcl -v -C cmconcl.config
This command will verify that all parameters are within range, all
fields are filled out, and the entries (such as NODE_NAME) are valid.
2. Use the following command to distribute the ContinentalClusters
configuration information to all nodes in the continental cluster:
# cmapplyconcl -v -C cmconcl.config
Configuration data is copied to all nodes and in both clusters. This
data includes a set of managed object files that are copied to the
/etc/cmconcl/instances directory on every node in both clusters.
All nodes must be booted when the command is issued, although the
MC/ServiceGuard cluster may or may not be running.