----------------------------------------------------------------------------- H E W L E T T P A C K A R D C O M P A N Y HP ProLiant Support Pack (PSP) for Linux Help Version 7.10b ----------------------------------------------------------------------------- 1. What is a ProLiant Support Pack (PSP) 2. Minimum OS Requirements for the PSP 3. Contents of PSP 7.10b 3.1 PSP for Red Hat Linux 7.3 3.2 PSP for Red Hat Linux 8.0 3.3 PSP for SUSE LINUX Enterprise Server 7 4. Supported Errata Kernels for components included in this PSP 4.1 PSP for Red Hat Linux 7.3 4.2 PSP for Red Hat Linux 8.0 4.3 PSP for SUSE LINUX Enterprise Server 7 5. Updates in PSP v7.10b 5.1 New features or enhancements to the PSP installation utility: 5.2 New drivers/components in this PSP. 5.3 Updated drivers/components in this PSP. 5.4 Drivers/Components no longer included in the PSP. 6. Software Installation 6.1 GUI Deployment 6.2 Terminal Window Deployment 6.3 Silent Deployment 6.4 List of Command-line parameters 6.5 Usage Scenarios 6.6 Return Codes from the PSP 7. Log files 8. FAQ 1. What is a ProLiant Support Pack (PSP) A ProLiant Support Pack (PSP) is a bundle of components. A bundle is a group of components that have been tested individually and together to provide the latest available drivers, agents, and utilities for HP ProLiant servers. Each bundle consists of a bundle XML file that describes the PSP contents, installation tools, readmes, and components. Each component consists of an RPM package, a component XML file, and an optional README file with a filename that matches the name of the RPM except for the extension. See Section 3 of this document for the contents of the bundles for each supported distribution of Linux. See Section 6 for information regarding installation scenarios and Usage Scenarios. More information about the Linux PSP can be found in Chapter 4 of the ProLiant Support Pack User's Guide. The latest version of this can be found at the following URL: http://h18000.www1.hp.com/products/servers/linux/value-add-software.html#psp Each RPM included in the PSP has passed HP's rigorous software testing prior to release. To install individual RPMs, you can use the RPM command. Please refer to the man page for the RPM command for specifics on installing or upgrading components. The purpose of a PSP is to provide customers with the latest software, utilities, and drivers for HP Proliant servers. 2. Minimum OS Requirements for the PSP The PSP currently is shipped as individual bundles for each supported distribution of Linux. While not all components support all errata kernels, the PSP has been tested on the following distributions and errata kernels for this release. Distribution *Erratas ================================ ================================== Red Hat Linux 7.3 Base 2.4.18-3 thru 2.4.20-28.7 Red Hat Linux 8.0 Base 2.4.18-14 thru 2.4.20-28.8 SUSE Enterprise Server 7 Base 2.4.7-19 thru 2.4.18-290 * Errata kernels listed include versions of the listed errata kernels for base, smp, enterprise, bigmem and other vendor specific kernels. The PSP allows installation of components on kernels other than the ones listed above. If a component is known not to work on a given errata kernel, the PSP will not allow the component to be installed unless the force option is used. In the force case, the PSP will allow the component to attempt to install. In some instances, the installation of a component on a kernel that it does not support will result in a hung server on reboot. It is strongly recommended that if the user elects to use the force option, that it be tested on non-production servers first. The PSP is intended to be used after OS installation to update drivers and install HP-specific utilities (such as Array Configuration Utility, Health, etc), agents (NIC and Storage), and drivers (storage and NIC). HP recommends that the PSP be re-installed after any errata kernel has been applied to a server to ensure that all drivers and utilities are at the latest versions and are rebuilt with the latest kernel source if applicable. The server should be rebooted after installing the errata kernel in order to activate the errata kernel prior to the re-installation of the PSP. 3. Contents of PSP 7.10b 3.1 PSP for Red Hat Linux 7.3 File Name Description ========================================== ============================================= aic7xxx-6.3.2-rh73.i686.rpm HP ProLiant 64-Bit/66-Mhz Dual Channel Wide Ultra3 SCSI Controller Driver for Red Hat Linux 7.3 bcm5700-7.1.9e-1.src.rpm HP ProLiant NC10xx/NC67xx/NC77xx Gigabit Ethernet NIC Driver for Linux. bonding-1.0.4h-1.src.rpm HP Tested and Approved Linux Bonding Driver. cmanic-7.1.0-5.linux.i686.rpm NIC Agents for Servers - Linux. cmastor-7.1.0-12.linux.i386.rpm HP Storage Agents for Linux. cpqacuxe-7.15-19.linux.i386.rpm HP Array Configuration Utility for Linux. cpq_cciss-2.4.50-18.rh73.i686.rpm ProLiant Linux driver for Smart Array 5x and 6x Controllers for Red Hat Linux 7.3. e1000-5.2.16b-1.src.rpm HP ProLiant NC61xx/NC71xx Gigabit Ethernet NIC Driver for Linux. e100-2.3.27b-1.src.rpm HP ProLiant NC31xx Fast Ethernet NIC Driver for Linux. hpasm-7.1.0-145.rh73.i386.rpm HP Server Management Drivers and Agents for Red Hat Linux 7.3. hpasm-jlk-7.1.0-8.linux.i386.rpm Server Management Agent for Linux - Japanese Language Kit. hppldu-1.0.3-6.tar.gz The PSP binaries. The install shell will unpack and cleanup these files during the installation. hprsm-7.1.0-155.rh73.i386.rpm HP Lights-Out Drivers and Agents for Red Hat Linux 7.3. install710.sh The install shell script used to initiate PSP installations. lsi-megaide-drvr-2.26e-1.i386.rpm HP ProLiant Integrated Ultra ATA-100 Dual Channel Driver for Red Hat Linux 7.3 and SUSE Linux Enterprise Server 7 ucd-snmp-cmaX-4.2.5-116.rh73.i386.rpm A Collection of SNMP Protocol Tools from UC-Davis for Red Hat Linux 7.3. ucd-snmp-cmaX-devel-4.2.5-116.rh73.i386.rpm A Collection of SNMP Protocol Tools from UC-Davis for Red Hat Linux 7.3. ucd-snmp-cmaX-utils-4.2.5-116.rh73.i386.rpm A Collection of SNMP Protocol Tools from UC-Davis for Red Hat Linux 7.3. vlan-1.8.0-14.src.rpm HP Tested and Approved Linux 802.1q VLAN Driver. 3.2 PSP for Red Hat Linux 8.0 File Name Description ========================================== ============================================= aic7xxx-6.3.2-rh80.i686.rpm HP ProLiant 64-Bit/66-Mhz Dual Channel Wide Ultra3 SCSI Controller Driver for Red Hat Linux 8.0 bcm5700-7.1.9e-1.src.rpm HP ProLiant NC10xx/NC67xx/NC77xx Gigabit Ethernet NIC Driver for Linux. bonding-1.0.4h-1.src.rpm HP Tested and Approved Linux Bonding Driver. cmanic-7.1.0-5.linux.i686.rpm NIC Agents for Servers - Linux. cmastor-7.1.0-12.linux.i386.rpm HP Storage Agents for Linux. cpqacuxe-7.15-19.linux.i386.rpm HP Array Configuration Utility for Linux. cpq_cciss-2.4.50-18.rh80.i686.rpm ProLiant Linux driver for Smart Array 53xx and 5i controllers for Red Hat Linux 8.0. e1000-5.2.16b-1.src.rpm HP ProLiant NC61xx/NC71xx Gigabit Ethernet NIC Driver for Linux. e100-2.3.27b-1.src.rpm HP ProLiant NC31xx Fast Ethernet NIC Driver for Linux. hpasm-7.1.0-145.rh80.i386.rpm HP Server Management Drivers and Agents for Red Hat Linux 8.0. hpasm-jlk-7.1.0-8.linux.i386.rpm Server Management Agent for Linux - Japanese Language Kit. hppldu-1.0.3-6.tar.gz The PSP binaries. The install shell will unpack and cleanup these files during the installation. hprsm-7.1.0-155.rh80.i386.rpm HP Lights-Out Drivers and Agents for Red Hat Linux 8.0. install710.sh The install shell script used to initiate PSP installations. lsi-megaide-drvr-rh80-2.26e-1.i386.rpm HP Megaide ATA RAID Driver for Red Hat Linux 8.0. net-snmp-cmaX-5.1-74.rh80.i386.rpm A Collection of SNMP Protocol Tools from Net-SNMP for Red Hat Linux 8.0. net-snmp-cmaX-devel-5.1-74.rh80.i386.rpm A Collection of SNMP Protocol Tools from Net-SNMP for Red Hat Linux 8.0. net-snmp-cmaX-perl-5.1-74.rh80.i386.rpm A Collection of SNMP Protocol Tools from Net-SNMP for Red Hat Linux 8.0. net-snmp-cmaX-utils-5.1-74.rh80.i386.rpm A Collection of SNMP Protocol Tools from Net-SNMP for Red Hat Linux 8.0. vlan-1.8.0-14.src.rpm HP Tested and Approved Linux 802.1q VLAN Driver. 3.3 PSP for SUSE LINUX Enterprise Server 7 File Name Description ========================================== ============================================= aic7xxx-6.3.4-sles7.i686.rpm HP ProLiant 64-Bit/66-Mhz Dual Channel Wide Ultra3 SCSI Controller Driver for SLES 7. bcm5700-7.1.9e-1.src.rpm HP ProLiant NC10xx/NC67xx/NC77xx Gigabit Ethernet NIC Driver for Linux. bonding-1.0.4h-1.src.rpm HP Tested and Approved Linux Bonding Driver. cmanic-7.1.0-5.linux.i686.rpm NIC Agents for Servers - Linux. cmastor-7.1.0-12.linux.i386.rpm HP Storage Agents for Linux. cpqacuxe-7.15-19.linux.i386.rpm HP Array Configuration Utility for Linux. cpq_cciss-2.4.50-18.sles7.i586.rpm ProLiant Linux driver for Smart Array 53xx and 5i controllers for SUSE-SLES7. e1000-5.2.16b-1.src.rpm HP ProLiant NC61xx/NC71xx Gigabit Ethernet NIC Driver for Linux. e100-2.3.27b-1.src.rpm HP ProLiant NC31xx Fast Ethernet NIC Driver for Linux. hpasm-7.1.0-145.sles7.i386.rpm HP Server Management Drivers and Agents for SUSE Linux Enterprise Server 7. hpasm-jlk-7.1.0-8.linux.i386.rpm Server Management Agent for Linux - Japanese Language Kit. hppldu-1.0.3-6.tar.gz The PSP binaries. The install shell will unpack and cleanup these files during the installation. hprsm-7.1.0-155.sles7.i386.rpm HP Lights-Out Drivers and Agents for SUSE Linux Enterprise Server 7. install710.sh The install shell script used to initiate PSP installations. lsi-megaide-drvr-2.26e-1.i386.rpm HP ProLiant Integrated Ultra ATA-100 Dual Channel Driver for Red Hat Linux 7.3 and SUSE Linux Enterprise Server 7 ucdsnmp-cmaX-4.2.6-74.sles7.i386.rpm A Collection of SNMP Protocol Tools from UC-Davis for SUSE Linux Enterprise Server 7. vlan-1.8.0-14.src.rpm HP Tested and Approved Linux 802.1q VLAN Driver. 4. Supported Errata Kernels for components included in this PSP NOTE: 2.4.99-99 means that any 2.4 errata kernel later than the minimum supported kernel should work. Please refer to Section 2 for information on what errata kernels were actually tested for each supported distribution of Linux. 4.1 PSP for Red Hat Linux 7.3 File Name Minimum Supported Kernel Maximum Supported Kernel ======================================= ======================== ======================== cpq_cciss-2.4.50-18.rh73.i686.rpm 2.4.20-20.7 2.4.20-28.7 lsi-megaide-drvr-2.26e-1.i386.rpm 2.4.18-3 2.4.18-4 aic7xxx-6.3.2-rh73.i686.rpm 2.4.18-3 2.4.20-20.7 e100-2.3.27b-1.src.rpm 2.4.18-3 2.4.99-99 e1000-5.2.16b-1.src.rpm 2.4.18-3 2.4.99-99 bcm5700-7.1.9e-1.src.rpm 2.4.18-3 2.4.99-99 bonding-1.0.4h-1.src.rpm 2.4.18-3 2.4.99-99 vlan-1.8.0-14.src.rpm 2.4.18-3 2.4.99-99 ucd-snmp-cmaX-4.2.5-116.rh73.i386.rpm 2.4.18-3 2.4.99-99 ucd-snmp-cmaX-devel-4.2.5-116.rh73.i386. 2.4.18-3 2.4.99-99 ucd-snmp-cmaX-utils-4.2.5-116.rh73.i386. 2.4.18-3 2.4.99-99 hpasm-7.1.0-145.rh73.i386.rpm 2.4.18-3 2.4.99-99 hprsm-7.1.0-155.rh73.i386.rpm 2.4.18-3 2.4.99-99 cmanic-7.1.0-5.linux.i686.rpm 2.4.18-3 2.4.99-99 cmastor-7.1.0-12.linux.i386.rpm 2.4.18-3 2.4.99-99 cpqacuxe-7.15-19.linux.i386.rpm 2.4.18-3 2.4.99-99 hpasm-jlk-7.1.0-8.linux.i386.rpm 2.4.18-3 2.4.99-99 4.2 PSP for Red Hat Linux 8.0 File Name Minimum Supported Kernel Maximum Supported Kernel ======================================= ======================== ======================== cpq_cciss-2.4.50-18.rh80.i686.rpm 2.4.20-20.8 2.4.20-28.8 lsi-megaide-drvr-rh80-2.26e-1.i386.rpm 2.4.18-14 2.4.18-14 aic7xxx-6.3.2-rh80.i686.rpm 2.4.18-14 2.4.20-20.8 e100-2.3.27b-1.src.rpm 2.4.18-14 2.4.99-99 e1000-5.2.16b-1.src.rpm 2.4.18-14 2.4.99-99 bcm5700-7.1.9e-1.src.rpm 2.4.18-14 2.4.99-99 bonding-1.0.4h-1.src.rpm 2.4.18-14 2.4.99-99 net-snmp-cmaX-5.1-74.rh80.i386.rpm 2.4.18-14 2.4.99-99 net-snmp-cmaX-devel-5.1-74.rh80.i386.rpm 2.4.18-14 2.4.99-99 net-snmp-cmaX-perl-5.1-74.rh80.i386.rpm 2.4.18-14 2.4.99-99 net-snmp-cmaX-utils-5.1-74.rh80.i386.rpm 2.4.18-14 2.4.99-99 vlan-1.8.0-14.src.rpm 2.4.18-14 2.4.99-99 hpasm-7.1.0-145.rh80.i386.rpm 2.4.18-14 2.4.99-99 hprsm-7.1.0-155.rh80.i386.rpm 2.4.18-14 2.4.99-99 cmanic-7.1.0-5.linux.i686.rpm 2.4.18-14 2.4.99-99 cmastor-7.1.0-12.linux.i386.rpm 2.4.18-14 2.4.99-99 cpqacuxe-7.15-19.linux.i386.rpm 2.4.18-14 2.4.99-99 hpasm-jlk-7.1.0-8.linux.i386.rpm 2.4.18-14 2.4.99-99 4.3 PSP for SUSE LINUX Enterprise Server 7 File Name Minimum Supported Kernel Maximum Supported Kernel ======================================= ======================== ======================== cpq_cciss-2.4.50-18.sles7.i586.rpm 2.4.18-280 2.4.18-290 lsi-megaide-drvr-2.26e-1.i386.rpm 2.4.7-17 2.4.18-19 aic7xxx-6.3.4-sles7.i686.rpm 2.4.7-17 2.4.18-281 e100-2.3.27b-1.src.rpm 2.4.7-17 2.4.99-99 e1000-5.2.16b-1.src.rpm 2.4.7-17 2.4.99-99 bcm5700-7.1.9e-1.src.rpm 2.4.7-17 2.4.99-99 bonding-1.0.4h-1.src.rpm 2.4.7-17 2.4.99-99 ucdsnmp-cmaX-4.2.6-74.sles7.i386.rpm 2.4.7-17 2.4.99-99 vlan-1.8.0-14.src.rpm 2.4.18-131 2.4.99-99 hpasm-7.1.0-145.sles7.i386.rpm 2.4.7-17 2.4.99-99 hprsm-7.1.0-155.sles7.i386.rpm 2.4.7-17 2.4.99-99 cmanic-7.1.0-5.linux.i686.rpm 2.4.7-17 2.4.99-99 cmastor-7.1.0-12.linux.i386.rpm 2.4.7-17 2.4.99-99 cpqacuxe-7.15-19.linux.i386.rpm 2.4.7-17 2.4.99-99 hpasm-jlk-7.1.0-8.linux.i386.rpm 2.4.7-17 2.4.99-99 5. Updates in PSP v7.10b 5.1 New features or enhancements to the PSP installation utility: ==== N O N E ==== 5.2 New drivers/components in this PSP. o Support for the following adapters and utilities has been added since the last release of the Linux PSP: > net-snmp-cmaX-5.1-74.rh80.i386.rpm A Collection of SNMP Protocol Tools from Net-SNMP. > net-snmp-cmaX-devel-5.1-74.rh80.i386.rpm A Collection of SNMP Protocol Tools from Net-SNMP. > net-snmp-cmaX-perl-5.1-74.rh80.i386.rpm A Collection of SNMP Protocol Tools from Net-SNMP. > net-snmp-cmaX-utils-5.1-74.rh80.i386.rpm A Collection of SNMP Protocol Tools from Net-SNMP. > ucd-snmp-cmaX-4.2.5-116.rh73.i386.rpm A Collection of SNMP Protocol Tools from UC-Davis. > ucdsnmp-cmaX-4.2.6-74.sles7.i386.rpm A Collection of SNMP Protocol Tools from UC-Davis. > ucd-snmp-cmaX-devel-4.2.5-116.rh73.i386.rpm A Collection of SNMP Protocol Tools from UC-Davis. > ucd-snmp-cmaX-utils-4.2.5-116.rh73.i386.rpm A Collection of SNMP Protocol Tools from UC-Davis. 5.3 Updated drivers/components in this PSP. o Support for the following adapters and utilities has been updated since the last release of the Linux PSP: > "HP ProLiant 64-Bit/66-Mhz Dual Channel Wide Ultra3 SCSI Controller Driver". from "6.2.35-1" aic7xxx-6.2.35-rh73.i686.rpm to "6.3.2-1" aic7xxx-6.3.2-rh73.i686.rpm > "HP ProLiant 64-Bit/66-Mhz Dual Channel Wide Ultra3 SCSI Controller Driver". from "6.2.35" aic7xxx-6.2.35-rh80.i686.rpm to "6.3.2-1" aic7xxx-6.3.2-rh80.i686.rpm > "HP ProLiant 64-Bit/66-Mhz Dual Channel Wide Ultra3 SCSI Controller Driver". from "6.2.35" aic7xxx-6.2.35-sles7.i686.rpm to "6.3.4-1" aic7xxx-6.3.4-sles7.i686.rpm > "HP ProLiant NC10xx/NC67xx/NC77xx Gigabit Ethernet NIC Driver". from "6.2.17a-1" bcm5700-6.2.17a-1.src.rpm to "7.1.9e-1" bcm5700-7.1.9e-1.src.rpm > "HP Tested and Approved Linux Bonding Driver". from "1.0.4d-1" bonding-1.0.4d-1.src.rpm to "1.0.4h-1" bonding-1.0.4h-1.src.rpm > "NIC Agents". from "7.0.0-4" cmanic-7.0.0-4.linux.i686.rpm to "7.1.0-5" cmanic-7.1.0-5.linux.i686.rpm > "HP Storage Agents". from "7.0.0-16" cmastor-7.0.0-16.linux.i386.rpm to "7.1.0-12" cmastor-7.1.0-12.linux.i386.rpm > "HP Array Configuration Utility". from "7.0-1" cpqacuxe-7.0-1.linux.i386.rpm to "7.15-19" cpqacuxe-7.15-19.linux.i386.rpm > "ProLiant Linux driver for Smart Array 53xx and 5i controllers". from "2.4.48-6" cpq_cciss-2.4.48-6.sles7.i586.rpm to "2.4.50-18" cpq_cciss-2.4.50-18.sles7.i586.rpm > "ProLiant Linux driver for Smart Array 5x and 6x Controllers". from "2.4.48-8" cpq_cciss-2.4.48-8.rh73.i686.rpm to "2.4.50-18" cpq_cciss-2.4.50-18.rh73.i686.rpm > "ProLiant Linux driver for Smart Array 53xx and 5i controllers". from "2.4.48-8" cpq_cciss-2.4.48-8.rh80.i686.rpm to "2.4.50-18" cpq_cciss-2.4.50-18.rh80.i686.rpm > "HP ProLiant NC61xx/NC71xx Gigabit Ethernet NIC Driver". from "5.0.43c-1" e1000-5.0.43c-1.src.rpm to "5.2.16b-1" e1000-5.2.16b-1.src.rpm > "HP ProLiant NC31xx Fast Ethernet NIC Driver". from "2.2.21c-1" e100-2.2.21c-1.src.rpm to "2.3.27b-1" e100-2.3.27b-1.src.rpm > "HP Server Management Drivers and Agents". from "7.0.0-21" hpasm-7.0.0-21..i386.rpm to "7.1.0-145" hpasm-7.1.0-145..i386.rpm > "HP Lights-Out Drivers and Agents". from "7.0.0-19" hprsm-7.0.0-19..i386.rpm to "7.1.0-155" hprsm-7.1.0-155..i386.rpm > "HP Tested and Approved Linux 802.1q VLAN Driver". from "1.8.0-12" vlan-1.8.0-12.src.rpm to "1.8.0-14" vlan-1.8.0-14.src.rpm 5.4 Drivers/Components no longer included in the PSP. o Support for the following adapters and utilities has been removed since the last release of the Linux PSP: ==== N O N E ==== 6. Software Installation 6.1 GUI Deployment Graphical installation uses the ./install710.sh command without the --nui, --silent, or -y parameters. ./install710.sh A Gtk-based GUI enables you to install the components in the PSP. Please refer to Chapter 4 of the PSP User's Guide for detailed instructions and descriptions of GUI deployment using the Linux PSP. 6.2 Terminal Window Deployment During a "no user interface" installation, the installation proceeds at the terminal window. When the LDU is in this mode, user input and program output are provided at the terminal window. Program output is also saved to the default log file, /var/log/hppldu.log. To install with no user interface, you must use the --nui option on the ./install710.sh command: ./install710.sh --nui At the start of the --nui installation, the appropriate PSP for the installed version of Linux is determined. The PSP contains the components that support that version of Linux. These component contents are parsed to determine their installation requirements. If any components require configuration, you are prompted for the configuration information during the installation of those components. If a password is required, you are prompted to verify the original password. After the configuration data has been confirmed as valid, the --nui installation continues installation of the components in the PSP. During installation, information about each component to be installed is displayed. The name, version, and description of the component being installed are shown on the console. Any data generated by the installation, including output from RPM scripts, is shown on the terminal window. This continues until installation of all components has been attempted. While the installation is in progress, the LDU might determine that a component requires files that are not located on the current server. If this occurs, you are given the option to provide remote source location information about how to obtain the source. The LDU can obtain source from other remote servers using Network File System (NFS) or Samba. If you choose to provide this information, follow the prompts to provide the required information. Refer to the "Remote Source Location" section of the PSP User's Guide for more information about how to use the Remote Source Location option in the LDU. NOTE: Components that require files located on a remote server can take up to 20 minutes to install. Installation time varies depending on the speed and the number of processors of the servers involved, as well as network loading. After the installation is complete, the final status is returned by the LDU. If the reboot option has been selected and the installation was successful, the server reboots. If the reboot option has not been selected, you are returned to the terminal window prompt. 6.3 Silent Deployment During a silent installation, the LDU does not prompt for user input. Any components that would normally require user input will fail unless the necessary information has been provided in the input file using the --inputfile filename option on the ./install710.sh command. Installation of the PSP can require up to 30 minutes, especially if remote source code is required to compile drivers and multiple drivers must be built. With silent installation, the installation of all components is attempted. To install silently, you must use the -s or --silent options on the ./install710.sh command: ./install710.sh --silent All output that would normally be written to the terminal window during installation is saved in the default log file, /var/log/hppldu.log. 6.4 List of Command-line parameters ./install710.sh [-h | -? | --help] [--nui] [-s | --silent] [-r | --reboot ] [-f | --force] [--inputfile filename] [-t reboot_timeout_in_minutes] [ -m "reboot_message" ] [-v | --verbose] [--view rpmname] [ -y ] Command Line Argument Description ==================== =============================================== -h, -?, --help This argument displays a list of command line parameters. --nui This argument suppresses the user interface. However, during installation, output is shown at the terminal window unless the silent (--silent) option is also used. -s, --silent This argument enables a silent installation. All messages are logged to the /var/log/hppldu.log file unless overridden. No console output or GUI is shown. -r, --reboot This argument reboots the system if any components being installed require it and no failures occurred during the installation. -f, --force This argument attempts to force the installation of all components. This option will bypass the following install checks: · Minimum kernel version check · Maximum kernel version check · PCI device presence check · Installed library file requirements · Installed software version check The force option will not force a component to install if prerequisites such as required modules, files, source code, and build environment are not available, and if the PCI device for a device driver is not installed on the server. --inputfile filename This argument enables you to pass input parameters in to the LDU to enable scripted deployments of the PSPs. The name used for the filename can be any valid Linux text file name. -t reboot_timeout_in_minutes This argument enables you to delay a reboot by the specified number of minutes to enable users to save their data and log out from the server. If the --reboot parameter is not included, this parameter is ignored. -m "reboot_message" This argument enables you to send a message to all currently logged on users before rebooting the server. The message must be in double quotes to be sent properly. If the --reboot parameter is not included, this parameter is ignored. -v, --verbose This argument enables you to see more information during an installation than is normally displayed. --view rpmname This argument enables you to view the details associated with a given component RPM at the terminal window. The rpmname provided must be unique enough to enable the LDU to recognize the full RPM name. -y This argument enables you to step through a terminal window installation of a PSP. For each component, you will be prompted to decide whether it should be installed, or to exit out of the LDU. The -y switch will force the --nui switch option. 6.5 Usage Scenarios o Normal program execution to deploy a bundle of components for any supported distribution of Linux. The deployment utility will expect the bundle file and all bundles to be in the directory which it was called from. ./install710.sh o Using the force option for the Linux PSP ./install710.sh -f o Using the "terminal-window installation" option (No GUI) ./install710.sh --nui o Using the silent option (no command-line or GUI output) ./install710.sh -s o Using the silent option and the force option ./install710.sh -s -f o Installing a single component rpm -Uvh [component_name] o Determining a components details without installation ./install710.sh --view [rpm_name] o Use an input file to setup configuration variables for either a terminal window or GUI installation GUI ./install710.sh --inputfile /var/hp/hppldu.cfg Terminal Window Installation ./install710.sh --inputfile /var/hp/hppldu.cfg --nui o Reboot with message and timeout of 5 minutes after successful installation ./install710.sh --reboot -t 5 -m "The server will reboot in 5 minutes" 6.6 Return Codes from the PSP Value Meaning ========= ===================================================== 0 Installation was successful. Reboot is not required. 1 Component XML files are missing or corrupt. 2 No components to be installed were found in the bundle XML file. 3 Bundle XML file is missing, or no bundle XML was found that supports the installed version of Linux. 4 Component RPM files are missing or corrupt. 5 A condition was not met for one or more components. 6 Reserved 7 Reserved 8 More than one supported bundle XML file was found in the current directory. 9 User did not install any components prior to exiting the LDU. 10 Installation of one or more components failed. 11 User did not configure a component requiring configuration. 12 Preconfiguration of one or more components failed. 14 Postconfiguration of one or more components failed. 15 Reserved 16 Component installation was successful. Reboot is required to complete the installation of one or more components. 17 Installation of the selected components was not attempted because the software version is the same as the previously installed version. 18 Installation of the selected components was not attempted because a newer version of the software is already installed. 19 Installation of the selected components was not attempted because the hardware supported by the component was not found in the server. 20 One or more command line parameters on the ./install710.sh command was incorrect and must be fixed for installation to occur. 21 The user canceled installation of the Linux PSP before completion using CTRL+C. 22 Another instance of the LDU was found running on this server. Only one instance of the LDU can run at a time. 23 User aborted the installation during installation of components by clicking the Abort button. 7. Log files During PSP installation an installation log file is generated that contains more detailed information about the installation than is displayed by the GUI or terminal-window installation screens. The log file is useful in determining why a particular component failed to install properly. During installation, details about the each component and its installation progress are written to the log file at the following location: /var/hp/hppldu.log The installation log file can be displayed using any text editor. The default location of the log file can be altered by using the LOGFILENAME="" parameter in an inputfile. For more information about this parameter, please refer to the PSP User's Guide, Chapter 4. 8. FAQ The following issues might be encountered when attempting to install Linux PSPs. The issues are in bold and their resolutions follow: Q: I used the -r flag to reboot the server, and one of the components installed required a reboot, but the server did not reboot. What is happening? A: If any of the components chosen for installation fails the installation, a reboot does not occur. This enables the administrator to examine a server to determine and resolve a software installation failure before activating any changes. Q: When I try to install the PSP, I get the following error message: No supported Bundle XML files were found. The BP00xxxx.xml file is missing for the operating system that you have installed or the version of Linux you installed is not supported by any current Linux PSP. A: If the BP00xxxx.xml file is missing, download the complete Linux PSP again from http://www.hp.com/support/files. NOTE: All components that comprise a PSP must be present in the same directory as the Support Pack XML file. Q: When I try to install the PSP, I get the following error message: "Only one instance of the HP ProLiant Linux Support Utility may run at a time." A: This error indicates one of two conditions exist: 1. The utility is currently running, 'ps -e' should show this. Multiple instances of HPPLDU may not co-exist. 2. A lock file did not get removed from a previous instance. Look for a directory, /var/lock/hppldu. If it exists, remove it. Then rerun this utility. Q: When I install the storage components and restart the server, there are one or more new entries in the Linux Loader (LILO) or Grand Unified Bootloader (GRUB) tables for kernels to boot from. Is this normal? A: Yes, this is normal. Each of the storage drivers will relink its driver to the base kernel and add a new entry in the LILO or GRUB tables that are displayed at boot. To be sure that you get the kernel with the latest drivers, select the last entry in the table. Q: When I try to install the PSP for Linux remotely through ssh, I receive a message similar to the following: The libraries necessary to use the GUI are not available. Would you like to install the ProLiant Support Pack for Linux without user interaction? [Y/N] A: This is displayed for one of two reasons: - The required Gtk libraries are not installed on the local computer. You must install the required graphics libraries from the appropriate operating system installation CD or continue with the installation as a terminal window installation. - The appropriate DISPLAY environment variable has not been set on the remote server. To set the variable, use one of the following methods: NOTE: You must know either the DNS name or IP address of the target server. Method A: a. Be sure the ForwardX11 parameter is set to "yes" in the /etc/ssh/ssh_config file on the local server. b. Be sure the X11Forwarding parameter is set to "yes" in the /etc/ssh/sshd_config file on the remote system. c. Restart the sshd daemon on the remote system. Method B: a. On the local system, issue the command xhost + [IPAddress | DNS name of Remote Server] b. On the remote system, issue the command export DISPLAY=<[IP Address | DNS name] of Local system>:0 NOTE: Method B is not recommended because it can open your server to unauthorized access. Q: When I start the LDU, I cannot see the Install, Remote Source Location, and Exit buttons at the bottom of the screen in 800 x 600 screen resolution. A: On some 800 x 600 display resolutions, the Install, Remote Source Location, and Exit buttons might be hidden beneath the user panel. To view the Install, Remote Source Location, and Exit buttons, hide the user panel or collapse it to one side of the screen. HP recommends running the LDU in 1024 x 768 or higher resolution. Q: I attempt to connect to my NFS/Samba server, but I receive a message similar to the following: A directory, /usr/src/linux-2.4... necessary to complete installation of the xxx package is not present. A: Here are a few pointers to help make NFS/Samba connectivity easier to debug. - Attempt to mount the remote source outside of the LDU to ensure access rights are correct. - Verify that the firewall settings are correct. Issuing ‘iptables’ commands to enable port access for NFS or Samba might be necessary to correctly configure firewall access. Although not recommended, the firewall can be temporarily suspended during LDU installation by using the following command: /etc/init.d/iptables stop [use start to restart the firewall] - Be sure that the actual source directories are located at the remote source and not just the RPMs or source RPM for the kernel. To properly use remote source location, you must install the source on a server and then copy the entire /usr/src tree to the remote source server for use during future LDU installations. - Verify that the exported directory at the server is not exported at a higher directory layer. It is invalid to export a directory at multiple points in its directory tree. - Verify that no_root_squash has been set on any exported NFS directory. - Verify that write permissions have been given to the directories where the remote kernel source is located. During compilation of driver source, the make dep command will write a .depend file in each directory in the kernel source tree. Without write access, this command will fail. Q: I attempt to install a component that compiles from source code, but the installation fails on the make command. A: The cause of this problem is that the build tools necessary to complete the build from kernel source are not located on the server where the LDU is deploying. To build from source RPMs, the following RPMs must be installed on the server that the LDU is deploying software to: - gcc-2.96-108.1 or later - cpp-2.96-108.1 or later - binutil-2.11.90.0.8 or later - glibc-devel-2.2.4-26 or later Q: When I run the LDU and attempt to install NIC drivers using remote source code from an NFS server, I receive a return code 512, 1, or 2 from the make -C command or the command. A: The most common causes of this issue are: - Root_squash has been set on the NFS export on the NFS server. - Write permissions have not been granted to the directory tree from which the files are exported. - The NFS server exports multiple directories in the same directory tree (for example, /tmp/share and /tmp/share/files are in the same directory tree) that have different permissions. The solutions to these causes are: - Use the no_root_squash option when exporting a directory on the NFS server. Be sure to reset the exports as well, using exportfs -a after the change has been made. - Enable write permissions on the share at the NFS server (use "rw" instead of "ro" when exporting the file system). - Export only one directory in any given directory tree. Q: When I install the bcm5700 and e100 drivers, the modules.conf file does not get updated. Why not? A: The LDU installs these drivers but does not configure them because the LDU cannot determine all the information needed to properly configure the NIC drivers during installation. To configure these drivers, use the operating system-specific tools provided in the supported Linux distributions. Q: Why do some drivers report that they do not support the errata kernel that I have installed? A: Some RPM components provided by the LDU contain prebuilt binaries for the specific errata kernels that they support. If a new prebuilt binary is not available for an errata kernel, the LDU prevents the installation of the component. Upgraded RPM components that support newer errata kernels are included in the Linux PSPs as soon as possible after they are made available. If support for an errata kernel is not available, then you must choose either to use an errata kernel that allows the RPM component to install or to use alternate hardware that does provide support for the errata kernel you want to use. ----------------------------------------------------------------------------- Copyright 2003-2004 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.