HP Serviceguard A.11.20- Managing Serviceguard Twentieth Edition, August 2011

Figure 13 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 ” (page 227).
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 302) 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 227), for instructions for creating modular packages.
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.
Failover Packages’ Switching Behavior
The auto_run parameter (known in earlier versions of Serviceguard as the
PKG_SWITCHING_ENABLED parameter) defines the default global switching attribute for a failover
package at cluster startup: that is, whether Serviceguard can automatically start the package when
the cluster is started, and whether Serviceguard should automatically restart the package on a new
node in response to a failure. Once the cluster is running, the package switching attribute of each
package can be temporarily set with the cmmodpkg command; at reboot, the configured value
will be restored.
The auto_run parameter is set in the package configuration file.
How the Package Manager Works 51