Managing Serviceguard Sixteenth Edition, March 2009

NOTE: Cluster configuration is described in the previous section, “Configuring the
Cluster ” (page 216).
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:
cmapplyconf -P /etc/cmcluster/cfs/SG-CFS-pkg.conf
Begin package verification ...
Modify the package configuration ([y]/n)? Y
Completed the cluster update
(If you are using CFS, you will set up CVM as part of the CFS components.)
The following cmviewcl output shows result of the CVM 3.5 command above.
CLUSTER STATUS
example up
NODE STATUS STATE
ftsys9 up running
ftsys10 up running
MULTI_NODE_PACKAGES:
Configuring the Cluster 243