Managing Serviceguard A.11.20, March 2013

Package Types
Three different types of packages can run in the cluster; the most common is the failover package.
There are also special-purpose packages that run on more than one node at a time, and so do not
failover. They are typically used to manage resources of certain failover packages.
Non-failover Packages
There are two types of special-purpose packages that do not fail over and that can run on more
than one node at the same time: the system multi-node package, which runs on all nodes in the
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, such
as Veritas Cluster Volume Manager (CVM) and Cluster File System (CFS).
The rest of this section describes failover packages.
Failover Packages
A failover package starts up on an appropriate node (see node_name on (page 239)) 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 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 232).
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 307) 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
How the Package Manager Works 51