Managing Serviceguard 12th Edition, March 2006

Building an HA Cluster Configuration
Creating a Storage Infrastructure with VERITAS Cluster File System (CFS)
Chapter 5 241
3. If you have not initialized your disk groups, or if you have an old
install that needs to be re-initialized, use the vxinstall command
to initialize VxVM/CVM disk groups. See “Initializing the VERITAS
Volume Manager” on page 252.
4. 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 4.1, which is required
for the Cluster File System, Serviceguard supplies the SG-CFS-pkg
template. (In CVM 3.5, Serviceguard supplies the VxVM-CVM-pkg
template)
The CVM 4.1 package has the following responsibilities:
• Maintain VERITAS configuration files /etc/llttab,
/etc/llthosts, /etc/gabtab
• Launch required services: cmvxd, cmvxpingd, vxfsckd
• Start/halt VERITAS processes in the proper order: llt, gab,
vxfen, odm, cvm, cfs
NOTE Do not edit system multi-node package configuration files, such as
VxVM-CVM-pkg.conf and SG-CFS-pkg.conf. Create and modify
configuration using the cfs admin commands listed in Appendix A.
Activate the SG-CFS-pkg and start up CVM with the cfscluster
command; this creates SG-CFS-pkg, and also starts it.
This example, for the cluster file system, uses a timeout of 900
seconds; if your CFS cluster has many disk groups and/or disk LUNs
visible to the cluster nodes, you may need to a longer timeout value.
Use the -s option to start the CVM package in shared mode:
# cfscluster config -t 900 -s
5. Verify the system multi-node package is running and CVM is up,
using the cmviewcl or cfscluster command. Following is an
example of using the cfscluster command. In the last line, you can
see that CVM is up, and that the mount point is not yet configured: