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

The deadman driver sources and associated files are located at $SGROOT/drivers.
The pidentd (sg_pidentd for Red Hat 5) driver is located at:
/usr/src/pidentd-<version>/driver
where version represents the version number for the pidentd that was last
installed.
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
7. Reboot the node.
8. After the node has rebooted, verify the cluster status using cmviewcl, and also
verify all file systems with fsck.
9. Restart Serviceguard on this node using cmrunnode.
Check that the node joins the cluster successfully, and if necessary, move packages
back onto the node.
10. Edit the /usr/local/cmcluster/conf/cmcluster.rc file (on SUSE /opt/
cmcluster/conf/cmcluster.rc) to include the following line:
AUTOSTART_CMCLD = 1
11. 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.
Keeping Kernels Consistent
If you change kernel parameters as a part of doing a rolling upgrade, be sure to make
the same changes on all nodes that can run the same packages.
Example
The following example shows a simple rolling upgrade on two nodes running one
package each.
Compatibility Information and Installation Requirements 55