Managing Serviceguard Fifteenth Edition, reprinted May 2008

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5248
Verifying the Cluster Configuration
If you have edited a cluster configuration file using the command line,
use the following command to verify the content of the file:
cmcheckconf -k -v -C /etc/cmcluster/clust1.config
The following items are checked:
• Network addresses and connections.
• Cluster lock connectivity (if you are configuring a lock disk).
• Validity of configuration parameters for the cluster and packages.
• Uniqueness of names.
• Existence and permission of scripts specified in the command line.
• If all nodes specified are in the same heartbeat subnet.
• If you specify the wrong configuration filename.
• If all nodes can be accessed.
• No more than one CLUSTER_NAME, HEARTBEAT_INTERVAL, and
AUTO_START_TIMEOUT are specified.
• The value for package run and halt script timeouts is less than 4294
seconds.
•The value for NODE_TIMEOUT is at least twice the value of
HEARTBEAT_INTERVAL.
•The value for AUTO_START_TIMEOUT variables is >=0.
• Heartbeat network minimum requirement is met. See the entry for
HEARTBEAT_IP under “Cluster Configuration Parameters” starting on
page 156.
• At least one NODE_NAME is specified.
• Each node is connected to each heartbeat network.
• All heartbeat networks are of the same type of LAN.
• The network interface device files specified are valid LAN device
files.
• VOLUME_GROUP entries are not currently marked as cluster-aware.
• (On systems that support CVM 3.5) there is only one heartbeat
subnet configured if you are using CVM 3.5 disk storage.