Managing Serviceguard Eighteenth Edition, September 2010

• That all nodes specified are in the same heartbeat subnet, except in cross-subnet
configurations(page 41) .
• That the configuration filename is correcy.
• That all nodes are reachable.
• That no more than one CLUSTER_NAME and AUTO_START_TIMEOUT are
specified.
• That the value for package run and halt script timeouts is less than 4294 seconds.
• That the value for AUTO_START_TIMEOUT variables is >=0.
• That the heartbeat network minimum requirement is met. See the entry for
HEARTBEAT_IP under “Cluster Configuration Parameters ” (page 143) .
• That at least one NODE_NAME is specified.
• That each node is connected to each heartbeat network.
• That all heartbeat networks are of the same type of LAN.
• That network interface device files specified are valid LAN device files.
• That VOLUME_GROUP entries are marked as cluster-aware.
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.
For more information, see the manpage for cmcheckconf (1m) and “Checking Cluster
Components” (page 337).
Distributing the Binary Configuration File
After specifying all cluster parameters, apply the configuration. This action distributes
the binary configuration file to all the nodes in the cluster. HP recommends doing this
separately before you configure packages (as described in the next chapter) so you can
verify the cluster lock, heartbeat networks, and other cluster-level operations by using
the cmviewcl command on the running cluster. Before distributing the configuration,
ensure that your security files permit copying among the cluster nodes. See “Preparing
Your Systems” at the beginning of this chapter.
Use the following steps to generate the binary configuration file and distribute the
configuration to all nodes in the cluster:
• Activate the cluster lock volume group so that the lock disk can be initialized:
vgchange -a y /dev/vglock
• Generate the binary configuration file and distribute it:
Configuring the Cluster 259