Managing Serviceguard Fifteenth Edition, reprinted May 2008

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 277
Choosing Package Modules
IMPORTANT Before you start, you need to do the package-planning tasks described
under “Package Configuration Planning” on page 169.
To choose the right package modules, you need to decide the following
things about the package you are creating:
• What type of package it is; see “Types of Package: Failover,
Multi-Node, System Multi-Node” on page 277.
• Which parameters need to be specified for the package (beyond those
included in the base type, which is normally failover, multi-node,
or system-multi-node). See “Package Modules and Parameters” on
page 280.
When you have made these decisions, you are ready to generate the
package configuration file; see “Generating the Package Configuration
File” on page 311.
Types of Package: Failover, Multi-Node, System
Multi-Node
There are three types of packages:
• Failover packages. This is the most common type of package.
Failover packages run on one node at a time. If there is a failure,
Serviceguard (or a user) can halt them, and then start them up on
another node selected from the package’s configuration list; see
node_name on page 288.
To generate a package configuration file that creates a failover
package, include -m sg/failover on the cmmakepkg command line.
See “Generating the Package Configuration File” on page 311.
• Multi-node packages. These packages run simultaneously on more
than one node in the cluster. Failures of package components such as
applications, services, EMS resources, or subnets, will cause the
package to be halted only on the node on which the failure occurred.