Managing Serviceguard 13th Edition, February 2007

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4 171
Table 3-3 on page 87 describes different types of failover behavior and
how to set the parameters that determine each behavior.
Package Configuration File Parameters
Before generating the package configuration file, assemble the following
information and enter it on the worksheet for each package:
PACKAGE_NAME The name of the package. The package name must be
unique in the cluster. It is used to start, stop, modify,
and view the package.
In the package ASCII file, the package name can be
from 1 to 39 characters. It must not contain any of the
following illegal characters: space, slash (/),
backslash(\), and asterisk (*). All other characters are
legal.
FAILOVER_POLICY
The policy used by the package manager to select the
node on which the package should be automatically
started.
Default is CONFIGURED_NODE, which selects the next
available node in the list of node names for the
package. The order of preference is the order of the
node name entries in the package’s configuration file.
The alternate policy is MIN_PACKAGE_NODE, which
creates a list of packages running on each node that
can run this package, and selects the node that is
running the fewest packages.
FAILBACK_POLICY
The policy used to determine what action the package
manager should take if the package is not running on
its primary node and its primary node is capable of
running the package.
Default is MANUAL, which means no attempt will be
made to move the package back to its primary node
when it is running on an alternate node. (This is the
same behavior as in previous versions of Serviceguard.)
The alternate policy is AUTOMATIC, which means that
the package will be halted and restarted on its primary