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

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: /etc/sysconfig/network-scripts/ifcfg*
— SUSE: /etc/sysconfig/network/ifcfg*
5. Make sure you have the latest versions of the software listed under “Pre-Installation
Checklist” (page 45) and (if you are using or intend to use Serviceguard Manager)
“Pre-Installation Checklist for Serviceguard Manager” (page 46).
• SG files:$SGCONF/*: all current package control and configuration files, including
their log files.
Procedure — Performing the Rolling Upgrade
NOTE: Warning messages may appear during rolling upgrade while a node is
determining what version of software 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. Edit the /usr/local/cmcluster/conf/cmcluster.rc file (on SUSE, /opt/
cmcluster/conf/cmcluster.rc) to include the following line:
AUTOSTART_CMCLD = 0
If you need to upgrade only Serviceguard, and not the Linux OS, skip to step 6
below.
3. Upgrade the node to the new OS, or if necessary, do a complete installation with
a new OS.
4. After completing the OS upgrade or installation for the node, restore all its
previously saved Host files: /root/.rhosts, /etc/hosts, /etc/profile,
/etc/sysconfig/network/ifcfg*(or /etc/sysconfig/
network-scripts/ifcfg*) and bonding files.
Verify that the network configurations are the same prior to the upgrade or the
new installation. Check the current interface eth0 has the same corresponding
Mac address before and after.
5. Verify that all disks and their filesystems are the same prior to this OS upgrade or
new installation.
Check and compare with the disk layout collected before the upgrade. Use
command vgscan to make sure the node with new OS sees all its previously
configured LVM disks.
Rolling Software Upgrades 53