HP ProLiant Support Pack for Windows and Linux Version 8.70 User Guide

Abstract

This guide is intended for individuals who are familiar with the configuration and operation of Microsoft Windows, Windows Server 2003, Windows Server 2008, Linux, smart components, and deployment of firmware and software to systems and options.
Part Number: 376482-404 April 2011 Edition: 13
Copyright 2000, 2011 Hewlett-Packard Development Company, L.P. 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. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Microsoft, Windows, Windows Server, and Windows Vista are U.S. registered trademarks of Microsoft Corporation. Intel is a trademark of Intel Corporation in the U.S. and other countries. AMD is a trademark of Advanced Micro Devices, Inc.

Contents

Introduction..... 4
PSP overview..... 4 Benefits of PSP..... 4 Components in the PSP.... 5 New features..... 7 Obtaining the PSP..... 7 Obtaining PSP from HP SmartStart CD.... 7 HP website..... 8 Updating a PSP..... 8 Subscriber's Choice.... 8 Version control..... 8 Creating a centralized, network-based software repository.... 8

Deploying PSPs.... 10

PSP deployment scenarios.... 10 Deployment for Microsoft Windows.... 10 Minimum requirements for Microsoft Windows PSP... 10 Installing the PSP for Windows.... 11 Server virtualization detection and support... 13 Deploying PSPs for Linux.... 13 Minimum requirements for Linux PSP.... 13 Installing the PSP for Linux.... 17 Command-line installation.... 19 Command-line syntax.... 19 Command-line arguments.... 20 Input files..... 24 Command-line usage of input file.... 24 Input file format and rules.... 25 File encoding..... 25 Error reporting.... 25 Input file parameters..... 26

Advanced topics.... 19

Troubleshooting.... 35
Troubleshooting installation of PSP for Microsoft Windows... 35 Troubleshooting installation of PSP for Linux... 37

Technical support.... 39

Reference documentation.... 39 Operating system information.... 39 HP contact information..... 40
Acronyms and abbreviations.... 41 Index..... 43

Introduction

PSP overview
HP PSPs are operating system-specific bundles of drivers, utilities, and management agents optimized for HP ProLiant systems. Each PSP is a predefined and tested bundle that includes setup and software maintenance tools designed to help efficiently install, upgrade, and manage system software. The PSPs include tools for Microsoft Windows and Linux server environments that enable deployment of software updates from a central software repository to local or remote server systems. HP SUM enables users to deploy either Windows or Linux components locally on a server and remotely to multiple servers simultaneously. HP SUM can only deploy to target servers running the same operating system (Windows or Linux), however, you do not have to match the operating system version or kernel on the local and remote target servers. This means that Red Hat Enterprise Linux 6.0 can deploy to Red Hat Enterprise Linux 5.6 or Windows Vista clients can deploy updates to Windows 2003 or 2008 servers running those operating systems. NOTE: When deploying source RPMs, the Linux operating system, including the kernel on the system running HP SUM, must be the same as the system that the resulting RPM will be deployed to. A separate PSP is provided for each major operating system release and for each architecture (such as x86 and x86_64 versions). For more information about PSPs and to download the latest PSPs, see the PSP website (http://www.hp.com/servers/psp). NOTE: Information about deployment of previous PSPs can be found in HP ProLiant Support Pack User Guides located on the PSP website (http://www.hp.com/servers/psp).

Windows: WBEM

Linux: ACU

Linux: VCA

Linux: Health/Agents/Platform SW

Linux: Diagnostics

Diagnostics includes a web browser interface in addition to the command-line interface in an online mode. This feature enables remote control of the utility and facilitates easy transfer of configuration information from remote machines to a service provider.
SMH is a web-based interface that consolidates and simplifies single system management for HP servers running the HP-UX, Linux, and Windows operating systems. HP SMH aggregates and displays data from Web Agents and other HP Web-enabled System Management Software that includes:
HP Insight Diagnostics Array Configuration Utility HP Software Version Control Agents

New features

Support for the following operating systems:

o o o o

Red Hat Enterprise Linux 5.6 Red Hat Enterprise Linux 6.0 Windows Small Business Server 2011 Windows Small Business Server 2011 Essentials HP NC-Series QLogic P3P Multifunction Driver for Windows Server 2008 x32, x64, and R2 Editions HP StorageWorks Fibre Channel Over Ethernet Adapter Kit for the x32 and x64 QLogic Storport Driver HP NC-Series QLogic nx3 Multifunction Driver for Windows Server 2008 x32, x64, and R2 NOTE: The AMD and Intel Chipset components are now contained in the Combined Chipset component.
Support for the following components:
The following component is no longer supported:

Obtaining the PSP

The PSP can be obtained from the HP website or HP SmartStart CD media.
Obtaining PSP from HP SmartStart CD
PSPs and individual components can be obtained from the HP SmartStart CD. For information about the HP SmartStart CD, see the SmartStart download page (http://www.hp.com/servers/smartstart).

HP website

The latest PSPs and individual components for supported Windows and Linux operating systems are available at the PSP website (http://www.hp.com/servers/psp).

Updating a PSP

You can obtain the latest released drivers and utilities from the HP FTP site (ftp://ftp.hp.com). For more information, see the HP Smart Update Manager User Guide (http://www.hp.com/support/HP_Smart_Update_Manager_UG_en).

Subscriber's Choice

HP Subscriber's Choice and HP version control tools help to ensure that you have the most up-to-date PSPs and individual components. Keep actively informed of new releases of SmartStart and other Foundation Pack software with e-mail alerts from Subscribers Choice. Subscriber's Choice uses a secure website to proactively communicate product changes and Customer Advisories through e-mail to registered customers based on a customer-provided profile. Register for this free service at the HP Subscriber's Choice website (http://www.hp.com/go/subscriberschoice).

Version control

The HP Version Control Repository Manager (VCRM) and the HP Version Control Agent (VCA) are web-enabled Insight Management Agents. HP Systems Insight Manager uses these Insight Management Agents to facilitate software update tasks.

The VCRM provides a graphical view of the Windows and Linux PSPs that are stored in a repository and can be configured to automatically update the repository with the latest software from HP. The VCA can be configured to point to a repository being managed by the VCRM, enabling easy version comparison and software updates.
For more information about version control tools, see the HP Systems Insight Manager Help Guide and the Version Control User Guide on the HP Systems Insight Manager website (http://www.hp.com/go/hpsim).
Creating a centralized, network-based software repository
Deploying PSPs and individual components from a centralized, network-based software repository saves time and standardizes software maintenance and deployment procedures on Windows- and Linux-based systems.
For maximum flexibility across operating system platforms, locate the software repository on a Windows shared network drive. The repository can be updated from any of the following sources.

Deploying PSPs

Beginning with version 8.40, both Windows and Linux PSPs are deployed using HP SUM. In the PSP for Linux, HP SUM enables support for native RPM files. Users can now deploy firmware and software components simultaneously. PSPs can be deployed using graphical or command-line utilities specific to each operating system as listed below. For more information about PSP deployment with HP SUM, see the HP Smart Update Manager User Guide (http://www.hp.com/support/HP_Smart_Update_Manager_UG_en).

PSP deployment scenarios

Operating system environment

Microsoft Windows

Scenario
Graphical deployment on a single-host system using HP SUM Graphical deployment remotely on a multiple-host system using the HP SUM GUI Command-line deployment on a single-host system using the HP SUM command-line interface Command-line deployment on a multiple-host system using the HP SUM command-line interface Command-line deployment on a multiple-host system managed by HP Systems Insight Manager Graphical deployment on a single-host system using HP SUM Graphical deployment remotely on a multiple-host system using the HP SUM GUI Command-line deployment on a single-host system using the HP SUM command-line interface Command-line deployment on a multiple-host system using the HP SUM command-line interface
NOTE: If you install a PSP and then install an operating system Service Pack, a Support Pack, or other operating system updates, HP recommends reinstalling the PSP.
Deployment for Microsoft Windows
This section discusses deploying PSPs on Windows operating systems. The PSPs support 32-bit and x86-64-based installations on both AMD- and Intel-based servers. NOTE: For a current list of supported operating systems, refer to the PSP website (http://www.hp.com/servers/psp).
Minimum requirements for Microsoft Windows PSP

Deploying PSPs 10

IMPORTANT: Before deploying software updates on a host server, be sure that a recent backup of the host server is available in case the deployment procedure fails. For successful component deployments on Microsoft Windows hosts, the following minimum requirements must be met:
A local administrative system with 512 MB of memory and running a supported Windows operating system must be used. One or more remote host servers that run a supported Windows operating system and need a software upgrade must be available. If the local administrative system (local host) is the only server that requires an upgrade, then remote host servers are not necessary. Sufficient hard-drive space, which is generally at least twice the file size of the components you want to deploy, must be available. WMI must be enabled. NOTE: When attempting to use the remote deployment functionality of HP Smart Update Manager on any edition of Windows Server 2008, you must ensure that the File and Print Services feature is enabled and that the File and Print Services exception has been enabled in the Windows firewall. Failure to do so prevents HP Smart Update Manager from deploying remote Windows target servers.
All remote host servers must be connected to the same network and use TCP/IP to enable the systems to be accessed by the administrative system. Each host server must have an account with administrator privileges. HP recommends that the user name and password for the administrator account on each host server be the same as those on the local administrative system. If administrator privileges are not set up in this manner, then you must have the user name and password for each remote server available. Alternatively, you can use a domain account on the local administrative system that has administrator privileges on the host servers. The beginning and ending IP addresses for the range of hosts must both be on the same subnet. CAUTION: Microsoft recommends that all software be removed from the system before upgrading from Windows Server 2003 to Windows Server 2008. If software applications are left on the system during the upgrade process, Microsoft cannot guarantee the stability of the operating system or the software after the upgrade is complete.
Installing the PSP for Windows
HP SUM utility enables the deployment of PSP software components from a single, easy-to-use interface that is supported in Windows environments. This utility enables legacy support of existing software components, while simplifying the overall deployment process. You do not have to run the SETUP executable files (SETUPC.EXE, SETUPEX.EXE, and SETUP.EXE). HP SUM utility provides this functionality. The utility also provides installation logic and version control that automatically check for dependencies, installing only the correct updates for optimal configuration. With HP SUM version 3.2.0 and later, the storage location for the persistent data (Hosts and Groups) has changed. Persistent data entered with earlier versions of HP SUM is automatically moved to a new location the first time you run HP SUM version 3.2.0 and later. The data is not available for use with earlier versions of HP SUM. This process occurs only once. If an earlier version of HP SUM is run after the persistent data is

glibc 2.2.4-26 or later gawk 3.1.0-3 or later sed 3.02-10 or later pciutils-2.1.8-25.i386.rpm or later
The following RPMs are also required:

On Red Hat servers:

rpm 4.0.4 or later rpm-build 4.0.4 or later rpm-devel 4.0.4 or later
On SUSE Linux servers: rpm 3.0.6 or later
To successfully deploy HP SUM on remote target systems based on a Linux operating system, the following must be available:
tcl-8.x package expect-5.x package
In addition, components that are compiled from source code (such as NIC drivers) require the presence of the following build tools:
gcc-2.96-108.1 or later cpp-2.96-108.1 or later binutils-2.11.90.0.8 or later glibc-devel-2.2.4-26 or later kernel-headers-<version> (The version number depends on which kernel is used.) gtk+ -1.2.10-11 or later gtk- engines -0.11-3 or later
To install using the GUI option, you must have the following RPMs:
Starting with Linux HP ProLiant Support Pack 8.40 and later, and to support many HP value-add software deliverables included in the Linux PSP, you must install the following platform-specific compatibility libraries:
For Red Hat Enterprise Linux 5 x86 servers:

o o o o o

compat-libstdc++-296-2.96-132.7.2.i386 or later lm_sensors-2.8.7-2.i386 or later net-snmp-5.3.1-14.el5.i386 or later perl (required to provide the libperl.so) libnl (required for QLogic and Emulex drivers) compat-libstdc++-296-2.96-132.7.2.i386 or later lm_sensors-2.8.7-2.x86_64 or later net-snmp-5.3.1-14.el5.x86_64 or later perl (required to provide the libperl.so) libnl (required for QLogic and Emulex drivers)
For Red Hat Enterprise Linux 5 AMD64/EM64T servers:
For Red Hat Enterprise Linux 6 servers: NOTE: The following versions listed are needed as a minimum. Later versions of these can also be used.
NOTE: Ensure that each NIC has an IP address assigned. To get the IP address assigned to a NIC, issue the dhclient command in the console, which enables the NIC interfaces and retrieves an IP address. If a NIC does not have an IP address, HP SUM appears to hang on start up.
RHEL6 Console Mode: NOTE: You cannot use an X console in either the x86 or x86_64 version. You must install the base server with defaults and the following RPMs listed to run HP SUM in silent mode.
lm_sensors-libs-3.1.1-10.el6.<arch>.rpm net-snmp-libs-5.5-27.el6.<arch>.rpm net-snmp-5.5.27.el6.<arch>.rpm kernel-headers-2.6.32-71.el6.<arch>.rpm redhat-rpm-config-9.0.3-25.el6.noarch.rpm kernel-devel-2.6.32-71.el6.<arch>.rpm rpm-build-4.8.0-12.el6.<arch>.rpm gcc-4.4.4-13.el6.<arch>.rpm

RHEL6 Graphical Mode: NOTE: If you elect to install the XWindows support, then RHEL6 Graphical Mode applies to both x86 and x86_64. NOTE: The following items must be the 32-bit version even under x86_64 architecture as HP SUM and several of the RPMs require 32-bit libraries installed.
libuuid-2.17.2-6.el6.i686.rpm freetype-2.3.11-5.el6.i686.rpm libSM-1.1.0-7.1.el6.i686.rpm libICE-1.0.6-1.el6.i686.rpm libXi-1.3-3.el6.i686.rpm libX11-1.3-2.el6.i686.rpm libXext-1.1-3.el6.i686.rpm libxcb-1.5-1.el6.i686.rpm libXau-1.0.5-1.el6.i686.rpm libXrender-0.9.5-1.el6.i686.rpm libXrandr-1.3.0-4.el6.i686.rpm libXfixes-4.0.4-1.el6.i686.rpm libXcursor-1.1.10-2.el6.i686.rpm fontconfig-2.8.0-3.el6.i686.rpm expat-2.0.1-9.1.el6.i686.rpm expect-5.44.1.15-2.el6.<arch>.rpm zlib-1.2.3-25.el6.i686.rpm
libstdc++-4.4.4-13.el6.i686.rpm net-snmp-5.5-27.el6.<arch>.rpm
In addition, the build directory for RPMs built from source has changed depending on the name of the user building them. Up through RHEL5, the directory had been /usr/src/redhat/RPMS/<architecture>. Under RHEL6, the directory is /root/rpmbuild/RPMS/<architecture> if the user is logged in as root and /$USER/home/rpmbuild/RPMS/<architecture> for users other than root. For SLES 10 x86 servers:
compat-2006.1.25-11.2.i586 or later compat-libstdc++-5.0.7-22.2.i586 or later perl (required to provide the libperl.so) libnl (required for QLogic and Emulex drivers) compat-2006.1.25-11.2.x86_64 or later compat-32bit-2006.1.25-11.2.x86_64 or later compat-libstdc++-5.0.7-22.2. x86_64 or later perl (required to provide the libperl.so) libnl (required for QLogic and Emulex drivers) e2fsprogs-32bit perl (required to provide the libperl.so) compat-libstdc++-296-2.96-132.7.2.i386 or later libstdc++33-3.3.3-11.9.i586 or later perl-SNMP-5.4.2.1-6.3.i586 or later net-snmp-5.4.2.1-6.3.i586 or later libnl (required for QLogic and Emulex drivers) glib-1.2.10-15.i386 or later compat-libstdc++-296-2.96-132.7.2.i386 or later libstdc++33-32bit-3.3.3-11.9 or later perl-SNMP-5.4.2.1-6.3.x86_64 or later net-snmp-5.4.2.1-6.3.x86_64 or later libnl (required for QLogic and Emulex drivers)
For SLES 10 AMD64/EM64T servers:

o o o o o o

For SLES 11 x86 servers:
For SLES 11 AMD64/EM64T servers:

The components are installed in the order provided unless dependencies between components require installation in a different order. If so, the utility changes the installation order based on the component dependencies to ensure the successful installation of as many components as possible. Multiple components and bundles can be specified on the same command line. When mixing components and bundles on the command line, the filter switches control what components and bundles are installed. /s[ilent] This argument causes the installation to run silently with no GUI or console output. All data writes to the log file. Any generated prompts use the default option and continue the installation without user input. If a component requires input before installation (such as configuration information), then the component installation fails, and an error message writes to the log file.
Command-line argument Description
Failed dependencies are not reported to the user when using the /s[ilent] argument. To verify failed dependencies, remove the /s[ilent] argument, reissue the command line, and then the HP SUM GUI appears. /allow_update_to_bun This argument is a filter switch and enables the user to install newer versions of dle components defined in a PSP or firmware bundle. This argument enables these components to replace the older versions of the same component that might have shipped with the bundles. /allow_non_bundle_co This argument is a filter switch and enables the user to install components that are mponents not included in the bundle but reside in the directory with the components in the bundle. /b[undle] <bundlename> This argument specifies the bundles to install. Bundles to install can be specified with or without the /b[undle] argument. or <bundle1_to_install> <bundle2_to_install> If using the /b[undle] argument, then only one bundle can be specified with the argument. However, multiple /b arguments and bundles can be specified on the same line. If the /b[undle] argument is not used, then multiple bundles can be specified at the same time, but the bundles need to be separated by a blank and listed after all the arguments on the command line. Multiple components and bundles can be specified on the same command line. When mixing components and bundles on the command line, the filter switches control what components and bundles are installed. /express_install This argument starts express install (for local host only). HP SUM performs discovery, install, or exit without user interaction. The user can cancel or terminate HP SUM. This argument specifies that components, which use SNMP protocol, are available to be selected for installation. These components are available for selection by default. When the /use_snmp argument is used, and the /use_wmi argument is not, the WMI components are optional.

/use_snmp

/use_location file_share
This argument specifies a directory or file share that contains the PSP and components for use with HP SUM. The file_share format must be a mapped file share and not in UNC format. If you do not specify this argument, the directory containing hpsum.exe or HP SUM is used by default. The logged-in account must have access to this location. The /user and /passwd arguments do not have any effect when attempting to access the file share. You can use those arguments only when connecting to a target system. This argument specifies that the check-box for Check ftp.hp.com on the Source Selection screen is to be selected. This enables components to be retrieved from hp.com and to be used in the list of possible updates. This argument enables the inclusion of a proxy server (and port number) to access the HP FTP site (ftp://ftp.hp.com). This argument must be used with /use_web. For example, /use_web /use_proxy <1.22.33.44:80> This argument enables the inclusion of a proxy script to access the HP FTP site (ftp://ftp.hp.com). This argument must be used with /use_web. For example, /use_web /proxy_script <autoproxy.com>

Command-line usage of input file
The form for the HP SUM command line using an input file is hpsum -inputfile <filename>. The input file itself can contain the same flags on the command line. The usual command line flags can still be used with
the -inputfile flag, and takes precedence over any given input file. The <filename> field can be enclosed in double quotes to enable paths with spaces.
Input file format and rules
The input file is divided into two sections:
Configuration The configuration section starts from the beginning of the file and proceeds until the first target section is encountered. This section consists of a number of settings parameters and their values. Each configuration setting must appear on a fresh line in the file along with its value. Comments start with a # character at the beginning of the line. Only one # is allowed on any line.
Target You can provide remote host targets to HP Smart Update Manager. This section can repeat any number of times in the input file, providing a way to organize targets in related sets. The section starts with a special header "TARGETS" enclosed in a pair of square brackets: Targets section ends with the special string "END" enclosed in a pair of brackets: The keyword TARGETS can be suffixed with an optional arbitrary string. This enables you to tag the purpose of the TARGETS section. Other than the visible difference in the header, the contents of such a section are not treated any differently. For example, [TARGETS_WIN2003].

[TARGETS] [END]

Credentials: The TARGETS section allows the targets to be grouped according to the credentials needed for logging in remotely. Each TARGETS section must have a set of login credentials, which applies to all targets in that section. If you want to use the current host's login credentials to log into one or more remote targets, you can do so by setting the variable USECURRENTCREDENTIAL to YES. Login credentials for one or more hosts can be supplied using the variables UID and PWD. If given at the beginning of a TARGETS section, both variables must be used. If given in the middle of a TARGETS section, one or the other can be used to override the selected variable and continue using the active value for the remaining variable. Remote Target: A remote target can be specified using the variable HOST. Possible values are a DNS Name or an IP address.

File encoding

To allow for the inclusion of double-byte characters, the input file is in UTF-8 format.

Error reporting

If errors are encountered in the input file, HP Smart Update Manager exits with a return value of -2 (bad parameter). The details of the location and nature of the error are recorded in hpsum_execution_log_<date>_<time>.raw.

Input file parameters

Parameter

SILENT

Description
This parameter causes the installation to run silently without GUI or console output. All data is written to the log file. Any generated prompts use the default option and continue the installation without user input. If a component requires input before installation (such as configuration information), then the component installation fails (unless the IGNOREERRORS = "FailedDependencies" parameter is supplied), and an error message is written to the log file. This parameter forces both firmware and software components. This parameter forces updates to firmware components. This parameter forces updates to software components. This parameter enables you to override or downgrade an existing installation of components in the selected bundle. This parameter enables you to downgrade to an earlier version of firmware for multi-target devices such as hard drives and array controllers. (Applies to firmware only.) This parameter enables you to rewrite the same version of firmware only for multi-target devices such as hard drives and array controllers. (Applies to firmware only.) This parameter enables you to reboot, if required.

Possible values

YES, NO
FORCEALL FORCEROM FORCESOFTWARE FORCEBUNDLE DOWNGRADE
YES, NO YES, NO YES, NO YES, NO

REWRITE

REBOOTALLOWED REBOOTMESSAGE REBOOTDELAY COMPONENTSLIST
This parameter enables you to create a message to Any string (not exceeding be displayed prior to rebooting. 256 characters) This parameter enables you to delay before rebooting. This parameter enables you to limit the list of components to be updated. This parameter enables you to limit the list of bundle xml files to be filtered. This parameter is a filter switch and enables you to install newer versions of components defined in a PSP, ISP, or bundle. This parameter enables these components to replace the older versions of the same component that might have shipped with the bundles. This parameter defines the behavior when a remote target has an existing HP SUM session in progress. This parameter enables you to skip the host if an existing HP SUM session already exists. A NO overrides the session in progress and reinitializes the installation framework on the remote host. This parameter causes the installation to continue Time in seconds Component names with file extensions (.exe,.rpm, or.scexe) Bundle file names YES, NO

List of IP address ranges separated by semicolons (for example, 10.1.1.1-10.1.1.10;10.2. 2.2-10.2.2.10)
YES (default to include anonymous access) NO
This parameter is used by the HP Systems Anonymous (default) Management Homepage to determine the type of Administrator access granted to local users. (Applies to Linux PSP CAUTION: Selecting local only.) access with administrator privileges as the login provides full access to any user with access to the local console, without prompting for a user name or password. This parameter is used by the HP Systems Management Homepage to set up the trust relationship mode. (Applies to Linux PSP only.)

TRUSTMODE

TrustByCertIf this value is used, the CERTLIST parameter must be defined to enable access to the server. TrustByNameIf this value is used, the XENAMELIST parameter must be defined. TrustByAllHP does not recommend using this value because of possible negative security consequences.
CAUTION: The accepted values are case-sensitive and must be capitalized as shown. Failure to do so prevents the trust relationship from being set up properly during
installation and might affect access to the web server.

CERTLIST

XENAMELIST

HPQLA2X00FO

This parameter enables a user to provide a list of certificate files or servers where certificates can be obtained for trust relationships for the HP Systems Management Homepage. (Applies to Linux PSP only.) This parameter enables a user to provide a list of servers, separated by semicolons, for trust relationships for the HP Systems Management Homepage. (Applies to Linux PSP only.) This parameter is only valid if the TRUSTMODE parameter is set to TrustByName. (Applies to Linux PSP only.) This parameter is used by the hp_qla2x00 QLogic Fibre Channel Driver to determine the failover mode to use. (Applies to Linux PSP only.) This parameter is used by the hp_qla2x00 QLogic Fibre Channel Driver to determine whether to skip detection of third-party storage. (Applies to Linux PSP only.) This parameter provides the username credentials for OA associated with VC. You must define a value of these variables before HOST variable in [TARGETS] section. This parameter only applies for VC firmware. This parameter provides the password credentials for OA associated with VC. You must define a value of these variables before HOST variable in [TARGETS] section. This parameter only applies for VC firmware.
Certificate file name or Server DNS name

Server DNS name

SinglePath SecurePath QLogicFailure
(No default value) HPQLA2X00FORCE "Y", "N" (default)
User can define OAUID variable multiple times before each HOST variable. User can define OAPWD variable multiple times before each HOST variable.
Examples of the HP SUM input file include: REBOOTALLOWED = YES REBOOTREQUIRED = NO REBOOTMESSAGE = "Server is going down for a reboot" REBOOTDELAY = 15 COMPONENTSLIST = cp001234.exe, cp001235.exe BUNDLESLIST = bp001234.xml ALLOWUPDATEBUNDLE = YES SKIPTARGET = NO IGNOREERRORS = ServerNotFound, FailedDependencies SOURCEPATH = c:\pkgsource1 USELATEST = YES SILENT = YES

How do I use HP SUM over a firewall? Which ports will I need to open? Are they configurable? The ports that HP SUM uses cannot be configured. When HP SUM port initiates communications to remote targets, it uses several well-known ports depending on the operating system. For Linux, HP SUM uses port 22 (SSH) to start communications with the remote target. HP SUM uses defined ports to communicate between the remote target and the workstation where HP SUM is executing. When you run HP SUM, it uses the administrator/root privileges to dynamically register the port with the default Linux firewalls for the length of the application execution, and then closes and deregisters the port. All communications are over a SOAP server using SSL with additional functionality to prevent man-in-the-middle, packet spoofing, packet replay, and other attacks. The randomness of the port helps prevent port scanning software from denying service to the application. The SOAP server is deployed on the remote target using the initial ports (138, 445, and 22) and then allocates another independent port for its communications back to the workstation where HP SUM s running. During shutdown of HP SUM, the SOAP server is shutdown and removed from the target server, leaving the log files. To deploy software to remote targets on their secure networks using HP SUM, the following ports are used.
Port 22 Ports 60000-60007
This port establishes a connection to the remote Linux server using SSH. Random ports are used in this range to pass messages back and forth between the local and remote systems using SSL. These ports are used on the system running HP SUM to send data to the target server. Several internal processes within HP SUM automatically use the port from 60000 when no other application uses it. If a port has a conflict, the manager uses the next available port. HP does not guarantee that the upper limit is 60007 because the limit depends on how many target devices are selected for installation. These ports are used to communicate from the target server to the system running HP SUM. The same mechanism is used by the remote access code as the 60000 ports, with the first trial port as 61000. The upper limit might not be 61007 when a conflict occurs. In the case of IPv4-only and one NIC, the lowest available port is used by HP SUM to pass information between processes on the local workstation where HP SUM is executed, and the next available port is used to receive messages from remote servers. This port is the default for some internal communications. This port is listening on the remote side if a conflict does not exist. If a conflict occurs, the next available port is used. The logs are passed to the target, and the logs are retrieved using an internal secure web server that uses port 80 (if available) or a random port between 63000 and 63005, if port 80 is not available. This support enables updates of the iLO firmware without the need to access the host server and enables servers running VMware or other virtualization platforms to update their iLO without rebooting their server or migrating their virtual machines to other servers.

Port 62286

Technical support

Reference documentation

For more information about PSPs, refer to the PSP website (http://www.hp.com/servers/psp). To download the latest PSPs, refer to the software and drivers download page (http://www.hp.com/servers/swdrivers). For information about HP Subscriber's Choice, refer to the Subscriber's Choice website (http://www.hp.com/go/subscriberschoice). For information about HP SUM, see the HP Smart Update Manager User Guide. (http://www.hp.com/support/HP_Smart_Update_Manager_UG_en) For information on the HP Systems Insight Manager, refer to the following documents on the HP Systems Insight Manager website (http://www.hp.com/go/hpsim):
HP Systems Insight Manager Installation and User Guide HP Systems Insight Manager Help Guide
For information about the SmartStart Scripting Toolkit, refer to the Toolkit website (http://www.hp.com/servers/sstoolkit). To download the SmartStart and other CDs, refer to the SmartStart download website (http://www.hp.com/go/ssdownloads). For information about HP Insight Control Management Software, see the HP website (http://www.hp.com/servers/rdp). For general information on management products, see the Insight Foundation website (http://www.hp.com/servers/proliantessentials). For information about operating systems supported by ProLiant servers, refer to the operating system support matrices (http://www.hp.com/go/supportos). For information about SmartStart support, refer to the SmartStart support matrices (http://www.hp.com/servers/smartstart/supportmatrices).
Operating system information
For information about Microsoft Windows operating systems, see the Microsoft website (http://www.microsoft.com). For information about Linux operating systems, refer to one of the following websites:
Red Hat Linux (http://www.redhat.com) SUSE Linux (http://www.suse.com)

HP contact information

For the name of the nearest HP authorized reseller:
See the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html). In the United States, for contact options see the Contact HP United States webpage (http://welcome.hp.com/country/us/en/contact_us.html). To contact HP by phone:
For HP technical support:
Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website (http://www.hp.com/hps).