HP Serviceguard A.11.20.20 for Linux Release Notes, March 2014

configuration—during rolling upgrade. This means that you must upgrade all nodes to the
new release before you can modify the configuration file and copy it to all nodes.
• 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. The Serviceguard binary configuration file
(cmclconfig) must be in the correct directory or the cluster will not behave properly.
• Within a Serviceguard cluster, no more than two versions of Serviceguard can be running
while the rolling upgrade is in progress.
• 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.
6.10 Preparation
IMPORTANT: Make sure there is a supported upgrade path from your current Linux and
Serviceguard versions to the new versions. For more information, see the latest version of HP
Serviceguard for Linux Certification Matrix at http://www.hp.com/go/linux-serviceguard-docs
There is no upgrade path between some Linux OS releases. In such cases you must install a new
OS (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 are upgraded.
Breaking this rule will leave the cluster in an inconsistent state. To recover, you must halt the cluster
and then upgrade all the nodes.
For more information, see “Maintaining a Package: Maintenance Mode” section in the Managing
HP Serviceguard manual.
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, and so on. 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.
6 Compatibility and installation requirements 21