Managing Serviceguard 12th Edition, March 2006

Building an HA Cluster Configuration
Creating the Storage Infrastructure and Filesystems with VERITAS Cluster Volume Manager (CVM)
Chapter 5 253
on the map and tree, like failover packages. These clusterwide packages’
properties have a special tab in the cluster properties, and their admin
menu is available when you select their cluster.
NOTE Cluster configuration is described in the previous section, “Configuring
the Cluster” on page 224.
Check the heartbeat configuration. The CVM 3.5 heartbeat requirement
is different from version 4.1:
• With CVM 3.5, prepare the cluster for CVM disk group configuration
you can configure only one heartbeat subnet in the cluster.
• With CVM 4.1, the cluster can have multiple heartbeats.
Neither version can use Auto Port Aggregation, Infiniband, or VLAN
interfaces as a heartbeat subnet.
The VERITAS cluster volumes are managed by a Serviceguard-supplied
system multi-node package which runs on all nodes at once, and
cannot failover. In CVM 3.5, Serviceguard creates the VxVM-CVM-pkg. In
CVM 4.1, 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:
• VERITAS CVM 3.5:
# cmapplyconf -P /etc/cmcluster/cvm/VxVM-CVM-pkg.conf
• VERITAS CVM 4.1: 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