Managing Serviceguard Nineteenth Edition, Reprinted June 2011

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 190).
Note that relocatable IP addresses cannot be assigned to multi-node packages. See also
“Differences between Failover and Multi-Node Packages” (page 218).
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 241).
• 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 224) and auto_run (page 224) must be set to yes
for this type of package. All services must have service_fail_fast_enabled (page 233)
set to yes.
System multi-node packages are supported only for applications supplied by HP, for example
Veritas Cluster File System (CFS).
NOTE: On systems that support CFS, you configure the legacy CFS system multi-node package
by means of the cfscluster command, 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 190).
NOTE: The following parameters cannot be configured for multi-node or system multi-node
packages:
• failover_policy
• failback_policy
• ip_subnet
• ip_address
Volume groups configured for packages of these types must be activated in shared mode.
For more information about types of packages and how they work, see “How the Package Manager
Works” (page 48). For information on planning a package, see “Package Configuration Planning
” (page 120).
When you have decided on the type of package you want to create, the next step is to decide
what additional package-configuration modules you need to include; see “Package Modules and
Parameters” (page 219).
Differences between Failover and Multi-Node Packages
Note the following important differences in behavior between multi-node and failover packages:
• If a multi-node package has auto_run disabled (set to no in the package configuration file)
it will not start when the cluster is started. You can use cmmodpkg to enable package switching
218 Configuring Packages and Their Services