HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009

• All nodes must be running the same releases of Linux and Serviceguard before
the upgrade.
• Rolling upgrades are not intended as a means of using mixed releases of
Serviceguard or Linux within the cluster. It is highly recommended that you
upgrade all cluster nodes as quickly as possible to the new release level.
• 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).
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.
68 Serviceguard for Linux Version A.11.18 Release Notes