HP Serviceguard Version A.11.19 Release Notes, October 2009

CAUTION: No package can be in maintenance mode, whether it is running or not,
when you perform an upgrade from Serviceguard A.11.19 to any later version, including
an upgrade from the initial release of A.11.19 to the July or later 2009 patch.
This means that:
• You must make sure no packages are in maintenance mode when you start the
upgrade.
• You must not put any package in maintenance mode until all the nodes have been
upgraded.
Breaking this rule will leave the cluster in an inconsistent state. To recover, you will
need to halt the cluster and then upgrade all the nodes.
When a package is in maintenance mode, you have two options:
• You can perform maintenance on the running package.
This is chiefly useful for making networking and EMS changes.
• You can halt the package and start it again in partial start-up maintenance mode,
in which you start up some modules, not others, and perform maintenance on the
modules you have not started.
This is useful for performing maintenance on package services, file systems, and
volume groups.
For more information, rules, and instructions see “Maintaining a Package” in Chapter
7 of the latest version of Managing Serviceguard, which you can find at the address given
under “Documents for This Version ” (page 50).
Other Package Changes
NOTE: For information about legacy and modular packages, see Chapter 6 of Managing
Serviceguard.
Serviceguard A.11.19 adds the following package features not discussed elsewhere in
these Release Notes:
• A new multi_node_all module includes all the parameters that can be
configured for multi-node packages.
• A new package_description parameter allows you to indicate what application the
package runs.
See “Package Modules and Parameters” in Chapter 6 of Managing Serviceguard for more
information.
What’s in this Release 31