Managing Serviceguard 12th Edition, March 2006

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 380
NOTE Using the MIN_PACKAGE_NODE policy, when node 2 is repaired and
brought back into the cluster, it will then be running the fewest
packages, and thus will become the new standby node.
If these packages had been set up using the CONFIGURED_NODE failover
policy, they would start initially as in Figure 3-7, but the failure of node 2
would cause the package to start on node 3, as in Figure 3-9:
Figure 3-9 CONFIGURED_NODE Policy Packages after Failover
If you use CONFIGURED_NODE as the value for the failover policy, the
package will start up on the highest priority node in the node list,
assuming that the node is running as a member of the cluster. When a
failover occurs, the package will move to the next highest priority node in
the list that is available.
Failback Policy The use of the FAILBACK_POLICY parameter allows
you to decide whether a package will return to its primary node if the
primary node becomes available and the package is not currently
running on the primary node. The configured primary node is the first
node listed in the package’s node list.
The two possible values for this policy are AUTOMATIC and MANUAL. The
parameter is coded in the package ASCII configuration file:
# Enter the failback policy for this package. This policy will be used
# to determine what action to take during failover when a a package
# is not running on its primary node and its primary node is capable