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

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.
4. 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 ensure the node with new OS sees all its previously configured LVM disks.
5. Install the new Serviceguard release from the DVD in the same order as described in the
“Packaging information”.
6. For Red Hat Enterprise Linux:
Ensure that the sg_pidentd rpm is not installed, if present erase the rpm rpm -e --nodeps
sg_pidentd-3.0.19-2
7. For Red Hat Enterprise Linux:
Ensure that the authd rpm is installed. If not, install authd rpm from distro. For example,
#rpm -i <authd rpm>
Follow the instructions in the README file in the directory of each driver. If you have installed
a new OS version, you must run a convert program. This will convert the binary file
(cmclconfig) to its new release format. To run the program on the upgraded node,
enter:$SGGSBIN/convert
a. Reboot the node.
b. After the node has rebooted, verify the cluster status using cmviewcl, and also verify all
file systems with fsck.
c. Restart Serviceguard on this node using cmrunnode. Check that the node joins the cluster
successfully, and if necessary, move packages back onto the node.
d. Edit the following file to include the line:AUTOSTART_CMCLD = 1
For Red Hat Enterprise Linux: /usr/local/cmcluster/conf/cmcluster.rc
For SUSE Linux Enterprise Server: /opt/cmcluster/conf/cmcluster.rc
e. Check if sgmgr service is running on the node:
# service jetty-sgmgr status
f. Repeat this process for each node in the cluster.
NOTE: Be sure to plan sufficient system capacity to allow moving the packages from
node to node during the process without an unacceptable loss of performance. If the
cluster fails before the rolling upgrade is complete (because of a catastrophic power
failure, for example), you can restart it by entering the cmruncl command from a node
which has been upgraded to the latest revision of the software.
NOTE: If you change kernel parameters as a part of doing a rolling upgrade, ensure to make
the same changes on all nodes that can run the same packages.
7.5 Supported rolling upgrade paths
Table 5 describes the supported upgrade paths for HP Serviceguard for Linux:
7 Rolling software upgrade 19