HP XC System Software Administration Guide Version 3.2

3. From the registration confirmation window, select the option to go directly to the ITRC
home page.
4. From the IT Resource Center home page, select patch/firmware database from the
maintenance and support (hp products) list.
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.
Select the HP XC version that is appropriate for the cluster platform.
If you are installing patches for SVA, select hpsva as the vendor.
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 website, contact the HP XC Support team at
the following email 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.
10.3 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.
10.4 Rebuilding 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.
136 Managing Patches and RPM Updates