----------------------------------------------------------------------------- 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 8.00 (Use Landscape format when printing) ----------------------------------------------------------------------------- 1. What is a ProLiant Support Pack (PSP)? 2. Minimum OS Requirements for the PSP 3. Contents of PSP 8.00 3.1 PSP for SUSE LINUX Enterprise Server 10 (AMD64/EM64T) 4. Support Information 5. Updates in PSP v8.00 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 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, README files, 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 the Chapter, "Deploying ProLiant Support Pack in Linux", of the ProLiant Support Pack User Guide. The latest version of this can be found at the following URL: http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00472061/c00472061.pdf 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. Starting with this release, support for AMD-based servers and 64-bit extensions for the Intel EM64T and AMD Opteron-based servers are supported as well. The Linux Deployment Utility is intelligent enough to determine which RPMs are supported based on the running kernel and only allows supported components to install. Because of this enhancement, support for the additional processors and bit extensions are included in a single PSP Bundle. This allows users to install the PSP without worrying about anything more than the distribution of Linux that is installed on their server. 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 Enterprise Linux 4 (32-bit) 2.6.9-11 (Update 1) through 2.6.9-67.EL (Update 6) (64-bit) 2.6.9-11 (Update 1) through 2.6.9-67.EL (Update 6) Red Hat Enterprise Linux 5 (32-bit) 2.6.18-8.el5 (Base) through 2.6.18-53.el5 (Update 1) (64-bit) 2.6.18-8.el5 (Base) through 2.6.18-53.el5 (Updaet 1) SUSE LINUX Enterprise Server 9 (32-bit) 2.6.5-7.244 (SP3) thru 2.6.5-7.308 (SP4) (64-bit) 2.6.5-7.244 (SP3) thru 2.6.5-7.308 (SP4) SUSE Linux Enterprise Server 10 (32-bit) 2.6.16.21-0.8 (Base) thru 2.6.16.53-0.16 (64-bit) 2.6.16.21-0.8 (Base) thru 2.6.16.53-0.16 * Errata kernels listed include versions of the listed errata kernels for base, smp, enterprise, bigmem and other vendor specific kernels. Not all component deliverables will support all listed errata kernels. Please see Section 4.a for the list of supported kernels for each component. NOTE: Support for Red Hat Professional 7.3, Red Hat Professional 8.0 and SUSE LINUX Enterprise Server 7 is available in the PSP v7.10b. Support for Red Hat Advanced Server 2.1 and Red Hat Enterprise Linux 2.1 is available in PSP v7.30. Support for SUSE LINUX Enterprise Server 8 (SLES8) is available in PSP v7.50. Support for Red Hat Enterprise Linux 3 is available in PSP v7.70. Starting with Linux PSP v8.00, PSPs for 32-bit and 64-bit are delivered separately. Please ensure the correct PSP is being used for the architecture of the Linux distribution being used. 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 as long as it supports the processor architecture and the hardware that a given driver supports is installed in the server. 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. 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 8.00 3.1 PSP for SUSE LINUX Enterprise Server 10 (AMD64/EM64T) File Name Description ================================================ ============================= aacraid-1.1.5.2432-4.sles10.x86_64.rpm.tar.gz HP 6-Port SATA RAID Controller Driver for SUSE Linux Enterprise Server 10 (AMD64/EM64T) bnx2-1.7.1d-1.src.rpm.tar.gz HP NC-Series Multifunction Driver for Linux cpqacuxe-8.0-14.noarch.rpm.tar.gz HP Array Configuration Utility for Linux cpq_cciss-3.6.18-10.sles10.x86_64.rpm.tar.gz HP ProLiant Smart Array Controller (AMD64/EM64T) Driver for SUSE LINUX Enterprise Server 10 (AMD64/EM64T) e1000-7.6.9.1b-1.src.rpm.tar.gz HP NC-Series Intel Driver for Linux fibreutils-2.4-1.linux.x86_64.rpm.tar.gz Fibre Channel Utilities for HP StorageWorks FCA2214/FCA2214DC FC HBA for Linux (AMD64/EM64T) hpacucli-8.0-14.noarch.rpm.tar.gz HP Array Configuration Utility CLI for Linux hpadu-8.0-14.noarch.rpm.tar.gz HP Array Diagnostics Utility for Linux hpasm-8.0.0-173.sles10.x86_64.rpm.tar.gz HP System Health Application and Insight Management Agents for SUSE LINUX Enterprise Server 10 (AMD64/EM64T) hpdiags-8.0.0-210.linux.i586.rpm.tar.gz HP Insight Diagnostics Online Edition for Linux hp-ilo-8.0.0-145.sles10.x86_64.rpm.tar.gz HP ProLiant Channel Interface for SUSE LINUX Enterprise Server 10 (AMD64/EM64T) hp-lpfc-8.1.10.11-1.linux.noarch.rpm.tar.gz HP Linux Driver Kit for Emulex Based Fibre Channel Host Bus Adapters for 2.6.x Kernels hp-lpfc-8.1.6.8-5.sles10.rpm.tar.gz HP Linux Driver Kit for Emulex Based Fibre Channel Host Bus Adapters for 2.6.x Kernels hpmouse-1.1.1-41.noarch.rpm.tar.gz HP iLO2 High-Performance Mouse for Linux hponcfg-1.7.0-2.noarch.rpm.tar.gz HP Lights-Out Online Configuration Utility for Linux hp-OpenIPMI-8.0.0-113.sles10.x86_64.rpm.tar.gz HP OpenIPMI Device Driver for SUSE LINUX Enterprise Server 10 (AMD64/EM64T) hppldu-1.0.19-2.tar.gz The PSP binaries. The install shell will unpack and cleanup these files during the installation. hppldu-librpms-1.0.19-2.tar.gz The PSP binaries. The install shell will unpack and cleanup these files during the installation. hp_qla2x00src-8.01.07.25-2.linux.noarch.rpm.ta HP StorageWorks FCA2214/FCA2214DC FC HBA Driver for 2.6.x Kernels hpsmh-2.1.11-197.x86_64.rpm.tar.gz HP System Management Homepage for Linux (AMD64/EM64T) hpvca-2.1.9-6.linux.rpm.tar.gz HP Version Control Agent for Linux install800.sh The install shell script used to initiate PSP installations mptlinux-4.00.13.01-1.sles10.x86_64.rpm.tar.gz HP U320 SCSI Adapter, SAS HBA with RAID, SCxxXe and SCxxGe series HBA (AMD64/EM64T) Driver for SUSE LINUX Enterprise Server 10 (AMD64/EM64T) nx_lsa-3.4.336-1.src.rpm.tar.gz HP Linux Socket Acceleration nx_nic-3.4.336-1.src.rpm.tar.gz HP NC-Series NetXen Driver for Linux tg3-3.81e-1.src.rpm.tar.gz HP NC-Series Broadcom TG3 Driver for Linux 4. Support Information Supported Errata Kernels for components included with 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. NOTE: 2.6.99-99 means that any 2.6 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. PSP for SUSE LINUX Enterprise Server 10 (AMD64/EM64T) Minimum Maximum File Name Kernel Kernel ======================================= ================== =================== aacraid-1.1.5.2432-4.sles10.x86_64.rpm 2.6.16.21-0.8 2.6.16.46-0.12 bnx2-1.7.1d-1.src.rpm 2.6.16.21-0.8 2.6.99-99 cpqacuxe-8.0-14.noarch.rpm 2.6.16.21-0.8 2.6.99-99 cpq_cciss-3.6.18-10.sles10.x86_64.rpm 2.6.16.21-0.8 2.6.16.46-0.12 e1000-7.6.9.1b-1.src.rpm 2.6.16.21-0.8 2.6.99-99 fibreutils-2.4-1.linux.x86_64.rpm 2.6.16.21-0.8 2.6.99-99 hpacucli-8.0-14.noarch.rpm 2.6.16.21-0.8 2.6.99-99 hpadu-8.0-14.noarch.rpm 2.6.16.21-0.8 2.6.99-99 hpasm-8.0.0-173.sles10.x86_64.rpm 2.6.16.21-0.8 2.6.99-99 hpdiags-8.0.0-210.linux.i586.rpm 2.6.16.21-0.8 2.6.99-99 hp-ilo-8.0.0-145.sles10.x86_64.rpm 2.6.16.21-0.8 2.6.99-99 hp-lpfc-8.1.10.11-1.linux.noarch.rpm 2.6.16.46-0.12 2.6.99-99 hp-lpfc-8.1.6.8-5.sles10.rpm 2.6.16.21-0.8 2.6.16.46-0.11 hpmouse-1.1.1-41.noarch.rpm 2.6.16.21-0.8 2.6.99-99 hponcfg-1.7.0-2.noarch.rpm 2.6.16.21-0.8 2.6.99-99 hp-OpenIPMI-8.0.0-113.sles10.x86_64.rpm 2.6.16.21-0.8 2.6.99-99 hp_qla2x00src-8.01.07.25-2.linux.noarch. 2.6.16.21-0.8 2.6.99-99 hpsmh-2.1.11-197.x86_64.rpm 2.6.16.21-0.8 2.6.99-99 hpvca-2.1.9-6.linux.rpm 2.6.16.21-0.8 2.6.99-99 mptlinux-4.00.13.01-1.sles10.x86_64.rpm 2.6.16.21-0.8 2.6.16.46-0.12 nx_lsa-3.4.336-1.src.rpm 2.6.16.21-0.8 2.6.99-99 nx_nic-3.4.336-1.src.rpm 2.6.16.21-0.8 2.6.99-99 tg3-3.81e-1.src.rpm 2.6.16.21-0.8 2.6.99-99 5. Updates in PSP v8.00 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 v7.91 release of the Linux PSP: ==== N O N E ==== 5.3 Updated drivers/components in this PSP. o Support for the following adapters and utilities has been updated since the v7.91 release of the Linux PSP: ==== N O N E ==== 5.4 Drivers/Components no longer included in the PSP. o The following Drivers/Components have been removed since the v7.91 release of the Linux PSP: ==== N O N E ==== 6. Software Installation 6.1 GUI Deployment Graphical installation uses the ./install800.sh command without the --nui, --silent, or -y parameters. ./install800.sh A Gtk-based GUI enables you to install the components in the PSP. Please refer to the chapter called, "Deploying ProLiant Support Packs in Linux", in the PSP User 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 with the ./install800.sh command: ./install800.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 the 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. 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 with the ./install800.sh command. Installation of the PSP can require up to 10 minutes, especially if compilation of multiple drivers must be performed. With silent installation the installation of all components is attempted. To install silently, you must use the -s or --silent options with the ./install800.sh command: ./install800.sh --silent, or, ./install800.sh -s 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 ./install800.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 This argument enables you to delay a reboot by (in minutes) 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 name.rpm.tar.gz, This argument enables you to view the details name.rpm associated with a given component RPM at the terminal window. The rpmname provided must be in the format of componentname.rpm or, componentname.rpm.tar.gz. -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. ./install800.sh o Using the force option for the Linux PSP ./install800.sh -f o Using the "terminal-window installation" option (No GUI) ./install800.sh --nui o Using the silent option (no command-line or GUI output) ./install800.sh -s o Using the silent option and the force option ./install800.sh -s -f o Installing a single component rpm -Uvh [un-tarred component_name.rpm] o Determining the component details without installation ./install800.sh --view [rpm_name] o Use an input file to setup configuration variables for either a terminal window or GUI installation GUI ./install800.sh --inputfile /var/hp/hppldu.cfg Terminal Window Installation ./install800.sh --inputfile /var/hp/hppldu.cfg --nui o Reboot with message and timeout of 5 minutes after successful installation ./install800.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 One or more component RPM files were missing or corrupt. 7 The selected components are not required on this server. 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 for future use. 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 ./install800.sh command was incorrect and must be fixed for the 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. 24 The component RPM does not support the current processor or data width (32bit vs 64bit). 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 each component and its installation progress are written to the log file at the following location: /var/log/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 Guide, Chapter, "Deploying ProLiant Support Packs in Linux". 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/servers/swdrivers. NOTE: All components that comprise a PSP must be present in the same directory as the Support Pack XML file. 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 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 and Exit buttons might be hidden beneath the user panel. To view the Install 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 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: 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. Q: When installing software via the HP Version Control Agent (VCA), if I update the HP Systems Management Homepage (hpsmh) software, my Version Control Agent will report "The document contains no data" when the Details option is clicked after a successful installation. A: The VCA uses the HP Systems Management Homepage to communicate to the Version Control Repository Manager (VCRM) software. When the HP Systems Management Homepage software is updated, the VCA may lose its connection to the HP Systems Management Homepage. To resolve this issue, simply log back into the Version Control Agent and look at the Details again to see the information from the installation. Q: When installing selected components in the HP ProLiant Support Pack using the HP Linux Version Control Agent (VCA), I notice that some software is removed and not re-installed. A: This is caused by the way that RPM structures its database and dependencies. The Linux PSP Deployment Utility (LDU) will remove all HP value-add software necessary to update a given component. When deployed as a bundle of software the LDU automatically installs the updated versions of the HP value-add software it removes so that the server is updated to the latest versions of HP value-add software. When using the VCA, since it is possible to install a single component, the VCA does not provide the LDU with the necessary files to re-install the previously removed software. To resolve this issue, it is recommended that a Linux ProLiant Support Pack baseline be established when using the Linux VCA and that installations be compared after single component installations with the established baselines. If any software is no longer at the established baseline, it should be installed using HP Systems Insight Manager (HP SIM) or the Linux VCA. ----------------------------------------------------------------------------- Copyright 2003-2008 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 note. 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 vendors standard commercial license.