Managing Serviceguard A.11.20, March 2013

Any package using a CVM disk group must declare a dependency (see the entries for
dependency_name and related parameters starting on (page 242)) on the CVM system multi-node
package. See “Preparing the Cluster for Use with CVM ” (page 225).
vxvm_dg
Specifies a VxVM disk group (one per vxvm_dg, each on a new line) on which a file system needs
to be mounted. See the comments in the package configuration file, and “Creating the Storage
Infrastructure and file systems with LVM, VxVM and CVM” (page 181), for more information.
vxvm_dg_retry
Specifies whether to retry the import of a VxVM disk group, using vxdisk scandisks to check
for any missing disks that might have caused the import to fail. Equivalent to VXVM_DG_RETRY in
the legacy package control script.
Legal values are yes and no. yes means vxdisk scandisks will be run in the event of an
import failure. The default is no.
HP recommends setting this parameter to yes in Metrocluster installations using EMC SRDF.
IMPORTANT: vxdisk scandisks can take a long time in the case of a large IO subsystem.
deactivation_retry_count
Specifies how many times the package shutdown script will repeat an attempt to deactivate a
volume group (LVM) or disk group (VxVM, CVM) before failing.
Legal value is zero or any greater number. As of A.11.18, the default is 2.
kill_processes_accessing_raw_devices
Specifies whether or not to kill processes that are using raw devices (for example, database
applications) when the package shuts down. Default is no. See the comments in the package
configuration file for more information.
File system parameters
A package can activate one or more storage groups on startup, and mount logical volumes to file
systems. At halt time, the package script unmounts the file systems and deactivates each storage
group. All storage groups must be accessible on each target node. (CVM disk groups must be
accessible on all nodes in the cluster).
For each local file system you specify in the package configuration file (fs_name (page 255)), you
must identify a logical volume, the mount point, the mount, umount, and fsck options and type
of the file system; for example:
fs_name /dev/vg01/lvol1
fs_directory /pkg01aa
fs_mount_opt "-o rw"
fs_umount_opt "-s"
fs_fsck_opt "-s"
fs_type "vxfs"
A logical volume can be created in an LVM volume group, a Veritas VxVM disk group, or a Veritas
CVM disk group. Logical volumes can be entered in any order, regardless of the type of storage
group. The parameter explanations that follow provide more detail.
For an NFS-imported file system, see the discussion under fs_name (page 255) and fs_server
(page 255).
Choosing Package Modules 253