Managing Serviceguard 13th Edition, February 2007

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4168
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 SG-CFS-MP-id# =UP on the
SAME_NODE.
2. The mount point packages should not run unless the disk group
packages are running.
Create the mount point packages using the cfsmntadm and cfsmount
commands. Serviceguard names the mount point packages
SG-CFS-MP-id#, automatically incrementing their ID numbers. In
their configuration file, Serviceguard specifies the dependency on the
disk group packages.
3. The disk group packages should not run unless the CFS system
multi-node package (SG-CFS-pkg) is running to manage the volumes.
Create the disk group packages with the cfsdgadm. command.
Serviceguard names them SG-CFS-DG-id#, automatically
incrementing their ID number. IN their configuration file,
Serviceguard specifies the dependency on the CFS system
multi-node package (SG-CFS-pkg).
CAUTION Once you create the disk group and mount point packages, it is
critical that you administer the cluster with the cfs commands,
including cfsdgadm, cfsmntadm, cfsmount, and cfsumount. If you
use the general commands such as mount and umount, it could cause
serious problems such as writing to the local file system instead of
the cluster file system.
Any form of the mount command (for example, mount -o cluster,
dbed_chkptmount, or sfrac_chkptmount) other than cfsmount or
cfsumount in a HP Serviceguard Storage Management Suite
environment with CFS should be done with caution. These non-cfs
commands could cause conflicts with subsequent command
operations on the file system or Serviceguard packages. Use of these
other forms of mount will not create an appropriate multi-node
package which means that the cluster packages are not aware of the
file system changes.