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

• You cannot delete Serviceguard software (via rpm -e) from a node while the
cluster is in the process of rolling upgrade.
• This procedure depends on the upgrade or re-install keeping the same device
naming convention and general system configuration. It is possible for devices to
change names or be changed in the scan order in a way that cannot be corrected.
If this happens, the cluster will need to be re-created rather than to be upgraded.
Preparation
IMPORTANT: Make sure there is a supported upgrade path from your current Linux
and Serviceguard versions to the new versions. See the Serviceguard, SGeRAC, and SMS
Compatibility and Feature Matrix at http://docs.hp.com/hpux/ha.
There is no upgrade path between some Linux OS releases. In such cases you will need
to do a new OS installation (cold install).
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.
See “Package Maintenance Mode” (page 19) for more information about this feature.
Do the following before you start.
1. Record the hostname and its entire network interface IP addresses. Record each
MAC address of each interface and its network assignment (Example: eth1:
HWaddr 00:0B:CD:69:F4:68)
2. Record all network information, such as network mask, gateway address, DNS
server address, its broadcast address, etc. This information can be useful if you
are installing a new OS.
NOTE: Make sure that all your network and storage interfaces are supported by
the new OS.
3. Record the storage configuration, such as all LVM information, and if possible,
collect a list of hardware disks configured, for example sfdisk -l
On SUSE Linux Enterprise Server, you may need to run YAST or YAST2.
52 Serviceguard for Linux Version A.11.19 Release Notes