Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4162
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. In the ASCII package
configuration file, this parameter is known as
FAILBACK_POLICY.
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
node as soon as the primary node is capable of running
the package and, if MIN_PACKAGE_NODE has been
selected as the Package Failover Policy, the primary
node is now running fewer packages than the current
node.
Package nodes
The names of primary and alternate nodes for the
package. In the ASCII configuration file, this
parameter is NODE_NAME. Enter a node name for each
node on which the package can run.
The order in which you specify the node names is
important. First list the primary node name, then the
first adoptive node name, then the second adoptive
node name, followed, in order, by additional node
names. in a failover, control of the package will be
transferred to the next adoptive node name listed in
the package configuration file.
If all nodes in the cluster are to be used, and if order is
not important, you can specify: NODE_NAME *
A node name can be up to 31 bytes long.
Package auto run