HP XC System Software Installation Guide Version 3.1

5. From the patch / firmware database page, select Linux under find individual patches.
6. From the search for patches page, in step 1 of the search utility, select vendor and version, select hpxc
as the vendor and select the HP XC version that is appropriate for the cluster platform.
7. In step 2 of the search utility, How would you like to search?, select Browse Patch List.
8. In step 4 of the search utility, Results per page?, select all.
9. Click the search>>> button to begin the search.
10. Download all patches that are available for the cluster platform into the temporary directory you
created.
If you are unable to retrieve the files from this Web site, contact the HP XC Support organization at
the following e-mail address:
[e-mail]
11. Follow the patch installation instructions in the README file.
12. Proceed to “Rebuild Kernel Dependent Modules” if a new kernel has been supplied in a patch.
3.5.2 Rebuild Kernel Dependent Modules
If a new kernel is supplied in a patch, you must rebuild all kernel dependent modules. It is outside the
scope of this document to list kernel-dependent modules. Therefore, it is your responsibility to read the
information in the patch README files to determine if a new kernel is being installed, and you must know
which modules are kernel dependent.
Be aware that some patches, such as a kernel patch, might require you to reboot the head node.
HP recommends that you rebuild the modules immediately after installing the new kernel and reboot the
head node so that the updated modules are included in the golden image that is created by the
cluster_config utility.
Rebuilding HP Serviceguard Modules
The HP Serviceguard software contains two modules that are built against the kernel. You must use the
following procedure to rebuild the pidentd and deadman modules if a new kernel is delivered in a patch.
NOTE: As an alternative, you can reinstall the Serviceguard RPMs rather than rebuilding the kernel
modules.
The /usr/local/cmcluster/bin directory is the default location of the Serviceguard commands. If
you installed Serviceguard in a location other than the default, look in the /etc/cmcluster.conf file
for the location of the Serviceguard bin directory. The examples in this procedure use the default location;
specify another path if you installed Serviceguard in a different directory.
1. Rebuild the pidentd module:
# cd /usr/src/pidentd-3.0.15sg/drivers
# make modules
CC [M] /usr/src/pidentd-3.0.15sg/drivers/pidentd.o
Building modules, stage 2.
MODPOST
CC /usr/src/pidentd-3.0.15sg/drivers/pidentd.mod.o
LD [M] /usr/src/pidentd-3.0.15sg/drivers/pidentd.ko
# make modules_install INSTALL
/usr/src/pidentd-3.0.15sg/drivers/pidentd.ko
2. Change to the directory where Serviceguard is installed (this example uses the default location), and
rebuild the deadman module:
# cd /usr/local/cmcluster/drivers
# make modules
CC [M] /usr/local/cmcluster/drivers/deadman.o
/usr/local/cmcluster/drivers/deadman.c:159: warning: `MODULE_PARM_' is deprecated
(declared at include/linux/module.h:552) Building modules, stage 2. MODPOST
CC /usr/local/cmcluster/drivers/deadman.mod.o
Rebuilding HP Serviceguard Modules 53