Proliant Linux Manual PSP Installation Using HPSUM

This page is for PSP versions that use hpsum to install the packages (PSP's starting with 8.40) . For PSP's lower than 8.40, see the page PHow to configure the PSP to load only the necessary PSP packages, configure SNMP, and install from the command line with no human interaction.

Here's how to configure the PSP to load only the necessary PSP packages, configure SNMP, and install from the command line with no human interaction. It is written for RHEL 4 and 5.

This example uses PSP 8.50 but it's valid for any of the PSP versions starting with 8.40. If you are using HPSUM v4.0.0 (from PSP 8.40), make sure to read HP Support Document ID c02257218: Advisory: (Revision) ProLiant Support Pack for Linux 8.40/8.41 - Unable to Configure RPMs Using the Input File Functionality in HP Smart Update Manager (HP SUM)

  • Modify the contents section at the end of the PSP description file, bp000518.xml, to allow the installation of only the packages that are necessary. The PSP description file name will change with each PSP revision.
    • Put the modified file in the directory where all of the PSP files reside.
    • Before modifiying the file, make a copy of it but do not put the copy in the same directory as the modified file.
    • All of the entries are originally marked as yes for installation. If you don't need/want to install a package, change the yes to no.
    • In this example, we're not going to install any drivers or the fibreutils package. These are the packages I select when I want only the packages required for Insight Remote Support (IRS):

    <package install="no">hp_qla2x00src-8.02.23-2.noarch.rpm</package>
    <package install="no">hp_qla2x00src-mezz-8.02.23-2.noarch.rpm</package>
    <package install="no">hp-lpfc-</package>
    <package install="no">cpq_cciss-3.6.24-4.rhel5.i686.rpm</package>
    <package install="no">mptlinux-</package>
    <package install="no">hpahcisr-1.2.4-14.rhel5.i686.rpm</package>
    <package install="no">hp-e1000-8.0.19-1.src.rpm</package>
    <package install="no">hp-e1000e-1.1.17-5.src.rpm</package>
    <package install="no">hp-tg3-3.99p-9.src.rpm</package>
    <package install="no">hp-netxtreme2-5.2.53-3.src.rpm</package>
    <package install="no">hp-nx_nic-4.0.526-2.src.rpm</package>
    <package install="no">hp-qla4xxx-</package>
    <package install="no">hp-igb-2.2.9-2.src.rpm</package>
    <package install="no">hp-be2net-</package>
    <package install="no">hp-be2iscsi-</package>
    <package install="no">hp-mlnx-en-1.5.1-3.src.rpm</package>
    <package install="yes">hp-OpenIPMI-8.5.0-1.rhel5.i386.rpm</package>
    <package install="yes">hp-ilo-8.5.0-1.rhel5.i386.rpm</package>
    <package install="yes">hp-health-</package>
    <package install="yes">hp-snmp-agents-</package>
    <package install="yes">hpmouse-1.2.0-96.noarch.rpm</package>
    <package install="yes">hpsmh-6.1.0-103.i386.rpm</package>
    <package install="yes">hp-smh-templates-</package>
    <package install="yes">hpvca-6.1.0-7.linux.rpm</package>
    <package install="yes">cpqacuxe-8.50-5.0.noarch.rpm</package>
    <package install="yes">hpacucli-8.50-6.0.noarch.rpm</package>
    <package install="yes">hpdiags-8.5.0-11.linux.i586.rpm</package>
    <package install="yes">hp-fc-enablement-1.1-16.noarch.rpm</package>
    <package install="no">fibreutils-2.5-4.i386.rpm</package>
    <package install="yes">hponcfg-3.1.0-0.noarch.rpm</package>

  • Create a configuration file (let's call it rhel_psp_input_file.cfg), like the one below, with snmpd.conf parameters (and a few others).
    • These are documented in the PSP Users Guide.
    • You can add any other parameters that you require.
    • The parameter BUNDLESLIST must be the name of the PSP description file that was modified in the prior section.

        BUNDLESLIST = bp000794.xml
        CMADEFTRAPCOMMSTR = public
        CMASYSLOCATION = Palo Alto Lab

For your site:

  • Change to the IP address of where you want the SNMP traps to be sent (e.g. your SIM server, NNM server. etc)
  • Change "public" to your Read-Only community name
  • Change "private" to your Read-Write community name (or delete the entries if you don't want to enter a Read-Write community name)
  • Change the contact and location information to whatever you like.

You can now install the PSP using the command line by changing to the directory where the PSP files reside and executing:

    ./hpsum /s /inputfile rhel_psp_input_file.cfg

To do a test installation (i.e. sumulate the installation but do not actually install anything), use the /dryrun option

     ./hpsum /s /dryrun /inputfile rhel_psp_input_file.cfg

Installing the PSP with Kickstart

You can't install many of the PSP packages, in particular the packages built from source, directly from a kickstart file. This is because the build needs to know which kernel you're running and the kickstart kernel won't work. If you're not building any of the packages from source, you can run the install command above.

If you are building from source, one way to do it is to install the PSP after the kickstart installation completes and the system has booted onto the runtime kernel. The %post section of the kickstart file would look something like this:

    chkconfig portmap on
    chkconfig nfs on
    mkdir /nwinstall
    cat > /etc/rc5.d/S99PSP_install << EOF
    mount /nwinstall
    cd /nwinstall
    ./hpsum /s /inputfile rhel_psp_input_file.cfg
    /bin/rm -f /etc/rc5.d/S99PSP_install
    /bin/chmod 755 /etc/rc5.d/S99PSP_install
    /bin/cp -f /etc/rc5.d/S99PSP_install /var/tmp # A copy to see whats going on
    exit 0

The assumption is that you're doing the PSP install using an NFS mount. If not, you'll need to modify the script section for http, ftp, etc.

  • You'll also need to modify the script for your own IP's and paths
  • The chkconfig lines make sure that the network services are running when the system is booted.
  • The mkdir line creates the NFS mount point
  • The next eight lines creates a script in the run level 5 boot directory. The script:
    • NFS mounts the PSP directory
    • Changes into the PSP directory
    • Executes the PSP installation script
    • Deletes itself so it doesn't execute again
    • You can have the system reboot after the PSP installation script completes by un-commenting the#/sbin/reboot line.
  • The chmod line makes sure the script is executable
  • The cp line makes a copy of the script in /var/tmp for debug purposes. You can remove this line once you're satisfied that the script is OK
  • The scenario is that:
    • The system is installed using kickstart
    • The %post section will create the PSP installation script
    • The system will reboot
    • The PSP installation script will install the PSP. Note that I put the S99PSP_install script in the run level directory, rc5.d. If your system comes up in run level 3, you'll need to modify the script to put it in the rc3.d directory.
    • The script runs as the last boot script, 99. If you change that, make sure it runs after the network and network services come up.
    • Retrieved from "