Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP XC System Software: Installation Guide > Chapter 3 Configuring and Imaging the System

Task 4: Install Patches or RPM Updates

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

For each supported version of the HP XC System Software, HP releases all Linux security updates and HP XC software patches on the HP IT Resource Center (ITRC) Web site.

You are required to download and install all available patches and updated RPM packages now before the system is configured so that the software updates are propagated to all nodes during the initial image synchronization.

See the following sources to determine if additional software packages (patches) are available for this release:

Proceed to “Task 5: Run the discover Command to Discover System Components” when you are finished installing patches.

Download and Install Patches

Follow this procedure to download and install HP XC patches from the ITRC Web site:

  1. Create a temporary patch download directory on the head node. You can name this temporary directory anything you want; this procedure creates a directory called /home/patches:

    # mkdir /home/patches
    IMPORTANT: Although HP has no restrictions about where you download patches, do not choose a directory that is included in the golden image because you do not want to distribute the actual RPM files to all client nodes. The HP XC System Software Administration Guide provides a list of directories that are included in the golden image; do not save patches in these directories.

    If necessary, you can exclude specific files from the golden image if they are not appropriate for distribution to all client nodes.

    The example uses /home because it is not included in the golden image.

  2. Register as an Americas/Asia Pacific or European customer at the following HP remote server:

    http://www.itrc.hp.com/

    NOTE: Because this is a newly installed system, set up the proxies on the Web browser to access this Web site.

    After supplying information about yourself and your corporation, an ITRC user ID is assigned to you; you supply your own password. Remember this user ID and password because you must use it whenever you download a patch.

  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 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:

    <xc_support@hp.com>

  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.

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
     LD [M]  /usr/local/cmcluster/drivers/deadman.ko
    # make modules_install INSTALL
    /usr/local/cmcluster/drivers/deadman.ko 
  3. Create a new module dependency list, system.map:

    # depmod -a
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2003 Hewlett-Packard Development Company, L.P.