Managing Serviceguard Fifteenth Edition, reprinted May 2008

Configuring Packages and Their Services
Choosing Package Modules
Chapter 6 279
NOTE On systems that support CFS, you configure the CFS system
multi-node package by means of the cfscluster command, not by
editing a package configuration file. See “Configuring Veritas System
Multi-node Packages” on page 325.
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” on page 74. For information on
planning a package, see “Package Configuration Planning” on page 169.
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” on page 280.
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 and start
the package for the first time. But if you then halt the multi-node
package via cmhaltpkg, it can be re-started only by means of
cmrunpkg, not cmmodpkg.