Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Planning and Documenting an HA Cluster
Package Configuration Planning
Chapter 4110
The policy used by the package manager to select the
node on which the package should be automatically
started.
Default is CONFIGURED_NODE, which means the next
available node in the list of node names for the
package. The order of node name entries dictates the
order of preference when selecting the node. The
alternate policy is MIN_PACKAGE_NODE, which means
the node from the list that is running the fewest other
packages at the time this package is to be started.
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. 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.
NODE_NAME The names of primary and alternate nodes for the
package. 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.
The node name can contain up to 31 bytes.
AUTO_RUN This parameter determines how a package may start
up. If AUTO_RUN is set to YES, the package will start up
automatically on an eligible node if one is available,