Managing Serviceguard 13th Edition, February 2007

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 382
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
# of running the package. Default is MANUAL which means no attempt
# will be made to move the package back to it primary node when it is
# running on an alternate node. The alternate policy is AUTOMATIC which
# means the package will be moved back to its primary node whenever the
# primary node is capable of running the package.
#FAILBACK_POLICY MANUAL
As an example, consider the following four-node configuration, in which
FAILOVER_POLICY is set to CONFIGURED_NODE and FAILBACK_POLICY is
AUTOMATIC: