Managing HP Serviceguard for Linux, Tenth Edition, September 2012

• The value for AUTO_START_TIMEOUT variables is greater than zero.
• Heartbeat network minimum requirement. See HEARTBEAT_IP under “Cluster
Configuration Parameters ” (page 103).
• 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.
• Other configuration parameters for the cluster and packages are valid.
If the cluster is online the cmcheckconf command 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 cluster configuration 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.
Cluster Lock Configuration Messages
The cmquerycl, cmcheckconf and cmapplyconf commands will return errors if the
cluster lock is not correctly configured. If there is no cluster lock in a cluster with two
nodes, the following message is displayed in the cluster configuration file:
# Warning: Neither a quorum server nor a lock lun was specificed.
# A Quorum Server or a lock lun is required for clusters of only two nodes.
If you attempt to configure both a quorum server and a lock LUN, the following message
appears on standard output when issuing the cmcheckconf or cmapplyconf command:
Duplicate cluster lock, line 55. Quorum Server already specified.
Distributing the Binary Configuration File
After specifying all cluster parameters, use the cmapplyconf command to 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 (described
in the next chapter). In this way, you can verify the quorum server, 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 “Configuring Root-Level Access” (page 158).
The following command distributes the binary configuration file:
cmapplyconf -k -v -C $SGCONF/clust1.conf
Configuring the Cluster 193