Managing Serviceguard 14th Edition, June 2007

Building an HA Cluster Configuration
Creating the Storage Infrastructure and Filesystems with Veritas Cluster Volume Manager (CVM)
Chapter 5258
Preparing the Cluster for Use with CVM
In order to use the Veritas Cluster Volume Manager (CVM), you need a
cluster that is running with a Serviceguard-supplied CVM system
multi-node package. This means that the cluster must already be
configured and running before you create disk groups.
Configure system multi-node and multi-node packages using the
command line, not Serviceguard Manager. Once configured, these
clusterwide packages’ properties have a special tab under Cluster
Properties.
NOTE Cluster configuration is described in the previous section, “Configuring
the Cluster” on page 234.
Check the heartbeat configuration. The CVM 3.5 heartbeat requirement
is different from version 4.1 and later:
• 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 and later, the cluster must 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 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 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: