Managing Serviceguard 12th Edition, March 2006

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5236
If you have edited an ASCII 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
Both methods check the following:
• 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. The cluster must have
one heartbeat LAN configured with a standby, two heartbeat LANs,
one heartbeat LAN and an RS232 connection, or one heartbeat
network with no local LAN switch, but with a primary LAN that is
configured as a link aggregate of at least two interfaces.
• 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.
• If a serial (RS-232) heartbeat is configured, there are no more than
two nodes in the cluster, and no more than one serial (RS232) port
connection per node.