Managing Serviceguard Fifteenth Edition, reprinted May 2008

Understanding Serviceguard Software Components
How the Package Manager Works
Chapter 3 75
Failover Packages
A failover package starts up on an appropriate node (see node_name on
page 288) when the cluster starts. A package failover takes place when
the package coordinator initiates the start of a package on a new node. A
package failover involves both halting the existing package (in the case
of a service, network, or resource failure), and starting the new instance
of the package.
Failover is shown in the following figure:
Figure 3-4 Package Moving During Failover
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; see Chapter 6, “Configuring Packages
and Their Services,” on page 275.
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” on page 377 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,” on page 275, for instructions for creating modular
packages.