Managing Serviceguard Nineteenth Edition, Reprinted June 2011

Figure 46 Running Cluster After Upgrades
Guidelines for Non-Rolling Upgrade
Do a non-rolling upgrade if:
• Your cluster does not meet the requirements for rolling upgrade as specified in the Release
Notes for the target version of Serviceguard; or
• The limitations imposed by rolling upgrades make it impractical for you to do a rolling upgrade
(see “Limitations of Rolling Upgrades ” (page 346)); or
• For some other reason you need or prefer to bring the cluster down before performing the
upgrade.
Migrating Cluster Lock PV Device File Names
If you use cluster lock volumes, and you have decided to migrate the device file names used by
the cluster nodes to the HP-UX 11i v3 agile addressing scheme or to cDSFs (see “About Device
File Names (Device Special Files)” (page 77) and “About Cluster-wide Device Special Files (cDSFs)”
(page 99)), use the procedures under “Updating the Cluster Lock Configuration” (page 281).
Other Considerations
See also “Keeping Kernels Consistent” and “Migrating cmclnodelist entries from A.11.15 or
earlier” (page 347).
Performing a Non-Rolling Upgrade
Limitations of Non-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 343).
The following limitations apply to non-rolling upgrades:
• Binary configuration files may be incompatible between releases of Serviceguard. Do not
manually copy configuration files between nodes.
• You must halt the entire cluster before performing a non-rolling upgrade.
Steps for Non-Rolling Upgrades
Use the following steps for a non-rolling software upgrade:
352 Software Upgrades