Managing Serviceguard Fifteenth Edition, reprinted May 2008

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4174
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.
NOTE The Disk Group (DG) and Mount Point (MP) multi-node packages
(SG-CFS-DG_ID# and SG-CFS-MP_ID#) 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.
Planning for Expansion
You can add packages to a running cluster. This process is described in
“Cluster and Package Maintenance” on page 329.
When adding packages, be sure not to exceed the value of
max_configured_packages as defined in the cluster configuration file.
(see “Cluster Configuration Parameters” on page 156). You can modify
this parameter while the cluster is running if you need to.
Choosing Switching and Failover Behavior
To determine the failover behavior of a failover package (see “Package
Types” on page 74), you define the policy that governs where
Serviceguard will automatically start up a package that is not running.
In addition, you define a failback policy that determines whether a
package will be automatically returned to its primary node when that is
possible.