Managing Serviceguard 12th Edition, March 2006

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4170
Table 3-3 on page 85 describes different types of failover behavior and
how to set the parameters that determine each behavior.
Package Configuration File Parameters
Prior to generation of the package configuration file, assemble the
following package configuration data. The parameter names given below
are the names that appear in Serviceguard Manager. The names coded
in the ASCII cluster configuration file appear at the end of each entry.
The following parameters must be identified and entered 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 ASCII package
configuration file, this parameter is PACKAGE_NAME.
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.
In Serviceguard Manager, more non-alphanumeric
characters are not allowed. See the online help topic
“Configuring Packages.”
Failover policy The policy used by the package manager to select the
node on which the package should be automatically
started. In the ASCII package configuration file, this
parameter is known as FAILOVER_POLICY.
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