Managing HP Serviceguard for Linux, Eighth Edition, March 2008

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 3 57
Figure 3-10 CONFIGURED_NODE Policy Packages after Failover
If you use configured_node as 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 set in the package configuration file:
As an example, consider the following four-node configuration, in which
failover_policy is set to configured_node and failback_policy is
automatic: