HP Serviceguard A.11.20.10 for Linux Release Notes, December 2012

a. Run the # lsmod | grep deadman command and verify whether deadman is already
loaded.
b. If deadman is already loaded, you must remove it. Run # rmmod deadman command
to remove the deadman.
c. To build and install deadman module, run the following commands in the $SGROOT/
drivers directory:
1) To make the module run the # make modules command.
2) To install the module run the # make modules_install command.
3) To insert the module run the # insmod deadman.ko command.
d. Run the # lsmod | grep deadman command to verify whether deadman is loaded.
NOTE: sg_pidentd or pidentd is not required to be reinstalled on Red Hat Enterprise
Linux 5, SUSE Linux Enterprise Server 10, or SUSE Linux Enterprise Server 11). Do this after
the errata is installed and the system has been rebooted.
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. 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.
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.
26