HP Serviceguard for Linux Version A.11.19 Release Notes, October 2009

In addition, you cannot use cmquerycl -q to configure IPv6 addresses (or hostnames
that resolve only to IPv6 addresses) for QS_HOST and QS_ADDR. You must generate
a cluster template file, edit it to set the appropriate (IPv6) values for QS_HOST and
QS_ADDR and set HOSTNAME_ADDRESS_FAMILY to ANY, and then use
cmapplyconf to apply the configuration. See the latest version of the HP Serviceguard
Quorum Server Version A.04.00 Release Notes on docs.hp.com —> High
Availability —> Quorum Server for more information.
IMPORTANT: Quorum Server Version A.04.00 is required if you are configuring a
second Quorum Server address (QS_ADDR). This is true whether QS_ADDR is an IPv4
or an IPv6 address.
Package Maintenance Mode
NOTE: For information about legacy and modular packages, see Chapter 6 of Managing
Serviceguard.
With the patches listed under “July 2009 Patches” (page 9) Serviceguard A.11.19
allows you to perform maintenance on a modular, failover package while the package
is running. This is called maintenance mode. The package must have package switching
disabled before you can place it in, or take it out, of maintenance mode.
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 2009 or later 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 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.
What’s in this Release 19