Managing HP Serviceguard A.11.20.20 for Linux, May 2013

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 176)) 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 169).
For legacy packages (packages created by the method used on versions of Serviceguard earlier
than A.11.18), you must also create a package control script for each package, to manage the
execution of the package’s services. See “Configuring a Legacy Package” (page 233) for detailed
information.
Customized package control scripts are not needed for modular packages (packages created by
the method introduced in Serviceguard A.11.18). These packages are managed by a master
control script that is installed with Serviceguard; see Chapter 6: “Configuring Packages and Their
Services ” (page 169), 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.
44 Understanding Serviceguard Software Components