Managing Serviceguard A.11.20, March 2013

To create modular CVM disk group and CFS mount point packages, use the cmmakepkg command
and edit the parameters in the package configuration file. You can choose to name the packages.
You can also use the Serviceguard Manager to create the modular CFS packages. See the
Serviceguard Manager online help for more information. Alternatively, you can create CFS legacy
disk group and mount point packages with the cfs family of commands. In this case, do not edit
the package configuration file, but use cfs commands to change the parameters. Serviceguard
names the packages SG-CFS-DG-id# and SG-CFS-MP-id#, respectively, and automatically
increments their ID numbers.
NOTE: It is highly recommend to use the modular style of packaging as they offer flexibility and
can be managed better compared to the legacy style of packaging. For differences between the
two, see “Modular CFS packages v/s Legacy CFS packages” (page 204). For more information on
modular CFS packages, see “Managing Disk Groups and Mount Points Using Modular Packages”
(page 209).
CVM 4.1 and later requires you to configure multiple heartbeat networks, or a single heartbeat
with a standby. The following interfaces are supported as heartbeat networks — APA (CVM 5.0.1
and later) and VLAN (CVM 4.1 and later).
You create a chain of package dependencies for application failover packages and the non-failover
packages:
1. The failover package’s applications should not run on a node unless the mount point packages
are already running.
In the package’s configuration file, you fill out the dependency parameter to specify the
requirement that the disk group is UP on the SAME_NODE.
2. The disk group packages should not run unless the CFS system multi-node package
(SG-CFS-pkg) is running to manage the volumes.
3. The mount point packages should not run unless the disk group packages are running.
If the disk groups and mount points are in separate packages, specify the dependencies on
the disk group packages in the configuration file.
CAUTION: Once you create the modular CVM disk group and CFS mount point packages,
you must administer the cluster with cmcheckconf, cmapplyconf, cmrunpkg, cmmodpkg,
and cmrunpkg commands. If you create the legacy CFS packages, you must administer the
cluster with CFS commands, including cfsdgadm, cfsmntadm, cfsmount, and cfsumount.
You must not use the HP-UX mount or umount command to provide or remove access to a
shared file system in a CFS environment; using these HP-UX commands under these
circumstances is not supported. Use cfsmount and cfsumount instead. If you use the HP-UX
mount and umount commands, serious problems could occur, such as writing to the local
file system instead of the cluster file system. Non-CFS commands could cause conflicts with
subsequent CFS command operations on the file system or the Serviceguard packages, and
will not create an appropriate multi-node package, which means cluster packages will not be
aware of file system changes.
NOTE: The Disk Group (DG) and Mount Point (MP) multi-node packages do not monitor the
health of the disk group and mount point. They check that the application packages that
depend on them have access to the disk groups and mount points. If the dependent application
package loses access and cannot read and write to the disk, it will fail, but that will not cause
the DG or MP multi-node package to fail.
4. You create the CFS package, SG-CFS-pkg, with the cfscluster command. It is a system
multi-node package that regulates the volumes used by CVM 4.1 and later. System multi-node
packages cannot be dependent on any other package.
Package Configuration Planning 133