Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Understanding Serviceguard Software Components

How the Package Manager Works

Chapter 3 79

# 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:

Figure 3-10 Automatic Failback Configuration before Failover

Node1 panics, and after the cluster reforms, pkgA starts running on node

Table 3-2 Node Lists in Sample Cluster

Package

Name

NODE_NAME

List

FAILOVER

POLICY

FAILBACK

POLICY

pkgA node1, node4 CONFIGURED_NODE AUTOMATIC

pkgB node2, node4 CONFIGURED_NODE AUTOMATIC

pkgC node3, node4 CONFIGURED_NODE AUTOMATIC