Managing Serviceguard A.11.20, March 2013

IMPORTANT: Do not proceed without reading and understanding the following points:
• The above are general guidelines. The requirements for any particular Serviceguard release
may be more restrictive. Rolling upgrade is supported only for the HP-UX/Serviceguard
combinations listed in the Release Notes for the target version of Serviceguard. Make sure
your cluster meets all specific requirements and limitations in those Release Notes, and all the
general requirements and limitations in this Appendix, before you attempt a rolling upgrade.
• A rolling upgrade cannot include a cold install of HP-UX on any node. A cold install will
remove configuration information; for example, device file names (DSFs) are not guaranteed
to remain the same after a cold install.
• Until the upgrade is complete on all nodes, you cannot change the cluster configuration files,
and you will not be able to use any of the features of the new Serviceguard release.
Read this entire section, including the “Example of a Rolling Upgrade ” (page 369), before you
begin your upgrade.
You can perform a non-rolling upgrade (that is, an upgrade performed while the cluster is down)
from any Serviceguard release to the latest Serviceguard release.
Performing a Rolling Upgrade
Limitations of Rolling Upgrades
The following limitations apply to rolling upgrades:
CAUTION: Stricter limitations apply to an upgrade to A.11.19; do not proceed with an upgrade
to A.11.19 until you have read and understood the Special Considerations for Upgrade to
Serviceguard A.11.19 (page 363).
• During a rolling upgrade to a release other than A.11.19, you can issue Serviceguard
commands, but should execute commands other than cmrunnode and cmhaltnode only
on a node containing the latest revision of the software. Performing tasks on a node containing
an earlier revision of the software will not work or will cause inconsistent results.
• You cannot modify the hardware configuration—including the cluster’s network
configuration—during rolling upgrade.
• You cannot modify the cluster or package configuration until the upgrade is complete.
If you need to modify the configuration (for example, to take advantage of new features),
upgrade all nodes to the new release, then modify the configuration file and copy it to all the
nodes.
NOTE: This means that you cannot migrate to the HP-UX 11i v3 agile addressing scheme
for device files during a rolling upgrade if cluster lock disks are used as a tie-breaker, because
that involves changing the cluster configuration. See “Updating the Cluster Lock Configuration”
(page 300) for instructions in this case. See “About Device File Names (Device Special Files)”
(page 81) for more information about agile addressing.
• None of the features of the newer release of Serviceguard are allowed until all nodes have
been upgraded.
• Binary configuration files may be incompatible between releases of Serviceguard. Do not
manually copy configuration files between nodes.
• No more than two versions of Serviceguard can be running in the cluster while the rolling
upgrade is in progress.
• Rolling upgrades are not intended as a means of using mixed releases of Serviceguard or
HP-UX within the cluster. HP strongly recommends that you upgrade all cluster nodes as quickly
as possible to the new release level.
• You cannot delete Serviceguard software (via swremove) from a node while a rolling upgrade
is in progress.
366 Software Upgrades