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

Ensure that you run the cmupgrade tool on all the nodes that are part of the cluster.
Ensure that the Jetty server and Java are installed on the nodes before you run the cmupgrade
tool. Also, ensure that java -version command displays the version greater than or equal
to 1.7.0 in the output.
To perform the rolling upgrade from A.11.20.X to A.12.00.00 using cmupgrade tool:
1. Enable global switching for packages running on node 1.
The cmmodpkg command enables switching of the package.
For example, #cmmodpkg -e pkg1
2. Halt first node.
Halt the node you want to upgrade. This results in the node's packages to start up on an
adoptive node. The Serviceguard daemon on node 1 is halted.
For example, #cmhaltnode -f node1
3. You can upgrade node as follows:
a. Export the SGMGR_ENV environment variable:
SGMGR_ENV=<replicated user password>
where, <replicated user password> is the password that you want to set for
Serviceguard Manager user.
For more information about how to create a replicated user, see “Installing HP
Serviceguard for Linux the traditional way”.
NOTE: Installation of Serviceguard Manager for Linux B.12.00.00 automatically creates
a user called sgmgr and password for this user is taken from the SGMGR_ENV environment
variable.
b. Upgrade node 1:
# cmupgrade [-a <automatic-installation-of-pre-requisites>] {-d
<mount-path-where-DVD-is-mounted>} {-j <jetty location>}
For more information, see cmupgrade (1m) manpage.
c. If you are upgrading to patch:
# cmupgrade {-d extracted_patch_location} {-j jetty-location}
IMPORTANT: Before you upgrade to the patch, ensure that HP Serviceguard for Linux
Base 12.00.00 is installed on your system.
4. Restart cluster on first node.
For example, # cmrunnode -n node1
Check that the node joins the cluster successfully, and if necessary, move packages back to
the node.
5. Repeat steps from 2 to 4 for all the nodes.
Upgrading HP Serviceguard for Linux the traditional way
To perform the rolling upgrade from A.11.20.X to A.12.00.00 the traditional way:
1. Enable global switching for packages running on node 1.
The cmmodpkg command enables switching of the package.
7 Rolling software upgrade 19