Managing Serviceguard 13th Edition, February 2007

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5228
• 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,
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.
• VOLUME_GROUP entries are not currently marked as cluster-aware.
• (On systems that support CVM) there is only one heartbeat subnet
configured if you are using CVM 3.5 disk storage.
If the cluster is online, the check also verifies that all the conditions for
the specific change in configuration have been met.
NOTE Using the -k option means that cmcheckconf only checks disk
connectivity to the LVM disks that are identified in the ASCII file.
Omitting the -k option (the default behavior) means that cmcheckconf
tests the connectivity of all LVM disks on all nodes. Using -k can result
in significantly faster operation of the command.