HP Serviceguard for Linux Enterprise Version 12.00.00 Release Notes, May 2014

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 ensure that 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 for Linux A.12.00.00 manual.
Before you start do the following:
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: Ensure 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.
4. Back up the following files on media that can be easily recovered by the node after its upgrade
or a new OS installation:
• Host files: /root/.rhosts, /etc/hosts, /etc/profile, and the network
information (including the bonding configurations):
◦ Red Hat Enterprise Linux :/etc/sysconfig/network-scripts/ifcfg*
◦ SUSE Linux Enterprise Server: /etc/sysconfig/network/ifcfg*
5. Ensure you have the latest versions of the software listed in the “Software prerequisites for HP
Serviceguard for Linux” section.
• SG files: $SGCONF/*: all current package control and configuration files, including their log
files.
7.4 Rolling upgrade on OS
NOTE: Warning messages might appear during rolling upgrade while a node is determining
the software version that is running. This is a normal occurrence and not a cause for concern.
1. Halt the node you want to upgrade (cmhaltnode). This will cause the node's packages to
start up on an adoptive node.
2. Upgrade the node to the new OS or patch.
3. After completing the OS upgrade or installation for the node, restore all its previously saved
Host files: /root/.rhosts, /etc/hosts, /etc/profile, /etc/profile, /etc/
18