Managing Serviceguard A.11.20, March 2013

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”
(page 233).
• 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” (page 234).
When you have made these decisions, you are ready to generate the package configuration file;
see “Generating the Package Configuration File” (page 258).
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”
(page 239).
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” (page 258).
• Multi-node packages. These packages run simultaneously on more than one node in the cluster.
Failures of package components such as applications, services, generic resources, EMS
resources, or subnets, will cause the package to be halted only on the node on which the
failure occurred.
The Veritas Cluster File System (CFS) system multi-node packages are examples of multi-node
packages; but support for multi-node packages is no longer restricted to CVM/CFS; you can
create a multi-node package for any purpose.
IMPORTANT: If the package uses volume groups, they must be activated in shared mode:
vgchange -a s.
NOTE: On systems that support CFS, you configure the legacy CFS multi-node packages by
means of the cfsdgadm and cfsmntadm commands, not by editing a package configuration
file. For modular CFS packages, you cannot edit using the cfs commands, but must edit the
parameters in the package configuration files; see “Creating a Storage Infrastructure with
Veritas Cluster File System (CFS)” (page 204).
Note that relocatable IP addresses cannot be assigned to multi-node packages. See also
“Differences between Failover and Multi-Node Packages” (page 234).
To generate a package configuration file that creates a multi-node package, include-m
sg/multi_node on the cmmakepkg command line. See “Generating the Package
Configuration File” (page 258).
• System multi-node packages. These packages run simultaneously on every node in the cluster.
They cannot be started and halted on individual nodes.
Both node_fail_fast_enabled (page 239) and auto_run (page 239) must be set to yes
for this type of package. All services must have service_fail_fast_enabled (page 248)
set to yes.
System multi-node packages are supported only for applications supplied by HP, for example
Veritas Cluster File System (CFS).
Choosing Package Modules 233