Managing Serviceguard Eighteenth Edition, September 2010

The package for CVM 4.1 and later 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 the configuration file SG-CFS-pkg.conf. Create and modify
configuration using the cfs administration commands.
1. First, make sure the cluster is running:
cmviewcl
2. If it is not, start it:
cmruncl
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 ” (page 269).
4. 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:
cfscluster status
Node : ftsys9
Cluster Manager : up
CVM state : up (MASTER)
MOUNT POINT TYPE SHARED VOLUME DISK GROUP STATUS
Node : ftsys10
Cluster Manager : up
CVM state : up
MOUNT POINT TYPE SHARED VOLUME DISK GROUP STATUS
262 Building an HA Cluster Configuration