Managing HP Serviceguard A.12.00.00 for Linux, June 2014

cluster, and the multi-node package, which can be configured to run on all or some of the nodes
in the cluster. System multi-node packages are reserved for use by HP-supplied applications.
The rest of this section describes failover packages.
3.3.1.2 Failover Packages
A failover package starts up on an appropriate node (see node_name (page 186)) when the cluster
starts. In the case of a service, network, or other resource or dependency failure, package failover
takes place. A package failover involves both halting the existing package and starting the new
instance of the package on a new node.
Failover is shown in the following figure:
Figure 10 Package Moving During Failover
3.3.1.2.1 Configuring Failover Packages
You configure each package separately. You create a failover package by generating and editing
a package configuration file template, then adding the package to the cluster configuration
database; details are in Chapter 6: “Configuring Packages and Their Services ” (page 179).
Modular packages are managed by a master control script that is installed with Serviceguard; see
Chapter 6: “Configuring Packages and Their Services ” (page 179), for instructions for creating
modular packages.
3.3.1.2.2 Deciding When and Where to Run and Halt Failover Packages
The package configuration file assigns a name to the package and includes a list of the nodes on
which the package can run.
Failover packages list the nodes in order of priority (i.e., the first node in the list is the highest
priority node). In addition, failover packages’ files contain three parameters that determine failover
behavior. These are the auto_run parameter, the failover_policy parameter, and the
failback_policy parameter.
42 Understanding Serviceguard Software Components