Managing Serviceguard 13th Edition, February 2007

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 380
# This policy will select nodes in priority order from the list
of
# NODE_NAME entries specified below.
# The alternative policy is MIN_PACKAGE_NODE. This policy will
select
# the node, from the list of NODE_NAME entries below, which is
# running the least number of packages at the time of failover.
#FAILOVER_POLICY CONFIGURED_NODE
If you use CONFIGURED_NODE as the value for the failover policy, the
package will start up on the highest priority node available in the node
list. When a failover occurs, the package will move to the next highest
priority node in the list that is available.
If you use MIN_PACKAGE_NODE as the value for the failover policy, the
package will start up on the node that is currently running the fewest
other packages. (Note that this does not mean the lightest load; the only
thing that is checked is the number of packages currently running on the
node.)
Automatic Rotating Standby Using the MIN_PACKAGE_NODE failover
policy, it is possible to configure a cluster that lets you use one node as an
automatic rotating standby node for the cluster. Consider the
following package configuration for a four node cluster. Note that all
packages can run on all nodes and have the same NODE_NAME lists.
Although the example shows the node names in a different order for each
package, this is not required.
When the cluster starts, each package starts as shown in Figure 3-7.
Table 3-1 Package Configuration Data
Package Name NODE_NAME List FAILOVER_POLICY
pkgA node1, node2,
node3, node4
MIN_PACKAGE_NODE
pkgB node2, node3,
node4, node1
MIN_PACKAGE_NODE
pkgC node3, node4,
node1, node2
MIN_PACKAGE_NODE