Managing Serviceguard Fifteenth Edition, reprinted May 2008

Building an HA Cluster Configuration
Configuring the Cluster
Chapter 5264
NOTE Cluster configuration is described in the previous section, “Configuring
the Cluster” on page 228.
Check the heartbeat configuration. The CVM 3.5 heartbeat requirement
is different from version 4.1 and later:
• CVM 3.5 requires that you can configure only one heartbeat subnet.
• CVM 4.1 and later versions require that the cluster have either
multiple heartbeats or a single heartbeat with a standby.
Neither version can use Auto Port Aggregation, Infiniband, or VLAN
interfaces as a heartbeat subnet.
The CVM cluster volumes are managed by a Serviceguard-supplied
system multi-node package which runs on all nodes at once, and
cannot fail over. For CVM 3.5, Serviceguard creates the VxVM-CVM-pkg.
For CVM 4.1 and later, Serviceguard creates the SG-CFS-pkg.
The SG-CFS-pkg package has the following responsibilities:
• Maintain Veritas configuration files /etc/llttab, /etc/llthosts,
/etc/gabtab
• Launch required services: cmvxd, cmvxpingd, vxfsckd
• Start/halt Veritas process in the proper order: llt, gab, vxfen, odm,
cvm, cfs
The following commands create the system multi-node package that
communicates cluster information to CVM:
• CVM 3.5:
cmapplyconf -P /etc/cmcluster/cvm/VxVM-CVM-pkg.conf
• CVM 4.1 and later: If you are not using Veritas Cluster File System,
use the cmapplyconf command. (If you are using CFS, you will set
up CVM as part of the CFS components.):
cmapplyconf -P /etc/cmcluster/cfs/SG-CFS-pkg.conf
Begin package verification ...
Modify the package configuration ([y]/n)? Y
Completed the cluster update