Managing Serviceguard 14th Edition, June 2007

Configuring Packages and Their Services
Editing the Configuration File
Chapter 6 305
vg vg01
vg vg02
• If you are using CVM, use the cvm_dg parameters to specify the
names of the disk groups to be activated, and select the appropriate
cvm_activation_cmd. Enter one disk group per cvm_dg, each on a
new line. You can use the fs_ commands in the FILESYSTEMS portion
of the configuration file to specify options for mounting and
unmounting file systems to these disk groups, but note that you must
specify the disk groups whether the package mounts file systems to
them or not.
Do not use the vxvm_dg or vg parameters for CVM disk groups. See
also “Configuring Veritas System Multi-node Packages” on page 313
and “Configuring Veritas Multi-node Packages” on page 315.
Do not include CFS-based disk groups in the package configuration
file; on systems that support CFS and CVM, they are activated by
the CFS multi-node packages before standard packages are started.
See “Configuring Veritas Multi-node Packages” on page 315.
• If you are using VxVM disk groups without CVM, enter the names of
VxVM disk groups that will be imported using vxvm_dg parameters.
Enter one disk group per vxvm_dg, each on a new line. Do not use the
cvm_dg parameters for VxVM disk groups without CVM, and do not
specify an activation command. See “How Control Scripts Manage
VxVM Disk Groups” on page 311.
• If you are using mirrored VxVM disks, use vxvol_cmd (see page
293) to specify the mirror recovery option to be used by vxvol.
• Specify the filesystem mount retry and unmount count options (see
page 295).
• You can specify a deactivation_retry_count for LVM, CVM, and
VxVM volume groups. See page 294.
• You can specify whether or not to kill processes activating raw
devices on shutdown; see page 294.
• If your package uses a large number of volume groups or disk groups,
or mounts a large number of file systems, consider increasing the
values of the following parameters:
— concurrent_vgchange_operations (see page 292)
— concurrent_fsck_operations (see page 294)