Managing Serviceguard Nineteenth Edition, Reprinted June 2011

After rebooting, node 1 rejoins the cluster. At that point, pkgA will be automatically stopped on
node 4 and restarted on node 1.
Figure 21 Automatic Failback Configuration After Restart of Node 1
CAUTION: Setting the failback_policy to automatic can result in a package failback and
application outage during a critical production period. If you are using automatic failback, you
may want to wait to add the package’s primary node back into the cluster until you can allow the
package to be taken out of service temporarily while it switches back to the primary node.
Serviceguard automatically chooses a primary node for a package when the NODE_NAME is set
to '*'. When you set the NODE_NAME to '*' and the failback_policy is automatic, if you
add, delete, or rename a node in the cluster, the primary node for the package might change
resulting in the automatic failover of that package.
Using Older Package Configuration Files
If you are using package configuration files that were generated using a previous version of
Serviceguard, HP recommends you use the cmmakepkg command to open a new template, and
then copy the parameter values into it. In the new template, read the descriptions and defaults of
the choices that did not exist when the original configuration was made. For example, the default
for failover_policy is now configured_node and the default for failback_policy is
now manual.
For full details of the current parameters and their default values, see Chapter 6: “Configuring
Packages and Their Services ” (page 216), and the package configuration file template itself.
Using the Event Monitoring Service
Basic package resources include cluster nodes, LAN interfaces, and services, which are the
individual processes within an application. All of these are monitored by Serviceguard directly. In
addition, you can use the Event Monitoring Service registry through which add-on monitors can
be configured. This registry allows other software components to supply monitoring of their resources
for Serviceguard. Monitors currently supplied with other software products include EMS (Event
Monitoring Service) High Availability Monitors, and an ATM monitor.
How the Package Manager Works 55