Managing Serviceguard 14th Edition, June 2007

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5242
• Heartbeat network minimum requirement is met. See the entry for
HEARTBEAT_IP under “Cluster Configuration Parameters” starting on
page 154.
• 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.
Distributing the Binary Configuration File
After specifying all cluster parameters, you 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
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: