HP Smart Update Manager User Guide Part Number 613175-002 June 2010 (Second Edition)
© Copyright 2010 Hewlett-Packard Development Company, L.P. 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. Confidential computer software.
Contents Introduction .................................................................................................................................. 6 HP Smart Update Manager overview ............................................................................................................. 6 Using this guide ........................................................................................................................................... 7 New features of HP SUM 4.0.x ........................
Component configuration for Windows components only ..................................................................... 70 Command-line examples ................................................................................................................... 70 Return codes .................................................................................................................................... 71 Windows smart component return codes ............................................................
Non-matching systems error reported when building source Linux RPMs or installing Linux RPMs built from source .............................................................................................................................................................. 107 Linux component version discrepancy for source RPMs ................................................................................. 108 HP SUM displays No components found in the selected repository(ies) message ........................
Introduction HP Smart Update Manager overview HP SUM is a technology, which is included in many HP products for installing and updating firmware and software components on HP ProLiant and HP Integrity servers, enclosures, and options. HP SUM provides a GUI and a command-line scriptable interface for: • Deployment of firmware for single or one-to-many HP servers and network-based targets such as iLOs, OAs, and VC Ethernet and Fibre Channel modules.
NOTE: HP SUM does not support third-party controllers. This includes flashing hard drives behind these controllers. Using this guide HP SUM is delivered with many different deliverables. A deliverable is an HP product which contains HP SUM and a set of firmware or software components. Some examples are the ProLiant Support for Windows and the HP Smart Update Firmware DVD.
• The beginning and ending IP addresses entered for the range of hosts (targets) must be on the same subnet. • To install firmware on HP Integrity BL860c/BL870c/BL890c i2 Servers, you must run HP SUM from an x86 or x86 Linux machine. You cannot deploy firmware on a Windows Integrity system from a Windows Integrity system. NOTE: HP Smart Update Manager requires a true Administrator login and not an elevated RUN AS Administrator.
• • • • • • o compat-libstdc++-296-2.96-132.7.2.i386 or later o lm_sensors-2.8.7-2.i386 or later o net-snmp-5.1.2-11.i386 or later o perl (required to provide the libperl.so) o libnl (required for QLogic and Emulex drivers) For Red Hat Enterprise Linux 4 AMD64/EM64T servers: o compat-libstdc++-296-2.96-132.7.2.i386 or later o lm_sensors-2.8.7-2.86_64 or later o net-snmp-5.1-2-11x86_64 or later o perl (required to provide the libperl.
• o libstdc++33-3.3.3-11.9.i586 or later o perl-SNMP-5.4.2.1-6.3.i586 or later o net-snmp-5.4.2.1-6.3.i586 or later o libnl (required for QLogic and Emulex drivers) For SLES 11 AMD64/EM64T servers: o glib-1.2.10-15.i386 or later o compat-libstdc++-296-2.96-132.7.2.i386 or later o libstdc++33-32bit-3.3.3-11.9 or later o perl-SNMP-5.4.2.1-6-3.x86_64 or later o net-snmp-5.4.2.1-6.3.
NOTE: Not all functionality is available in each version of HP SUM. Before using HP SUM that comes with a deliverable, review the Support and limitations ("Obtaining the HP SUM utility" on page 11) of that version of HP SUM to determine if it has the features that you need. Obtaining the HP SUM utility The HP SUM utility is available from the following: • HP ProLiant Support Packs for Windows® 7.90 and later • HP ProLiant Support Packs for Linux 8.
HP SUM version Delivered with Support and limitations Servers firmware 4.0.1 4.0.2 • HP ProLiant Support Pack for Windows 8.50 • HP ProLiant Support Pack for Linux 8.50 • HP Smart Update DVD 9.10 • No support to download the latest components available from ftp.hp.
Scenario Description HP SUM command HP deliverable Scripted deployment on a local host (Run HP SUM from a network share on a local server.
Scenario Description HP SUM command HP deliverable Automatic Deployment to one or more servers in a HP BladeSystem enclosure Use this scenario when you: The HP Smart Update Firmware DVD takes care of this automatically • • • (use the HP Smart Update Firmware DVD with embedded HP SUM to deploy firmware updates to one or more blades) Update an existing enclosure manually For more information, see BladeSystem Matrix compatibility chart at www.hp.com/go/matrix compatibility (http://www.hp.
HP SUM delivered with HP Workstation Support Pack supports the software deployment on Windows for HP ProLiant WS460c G6 Blade. This support is available for the local host only. Deploying software using the Integrity Support Pack (ISP) for Microsoft Windows The HP SUM utility enables you to deploy Windows ISP software components for HP Integrity Servers from a single, easy-to-use interface. This utility enables legacy support of existing software components while simplifying the overall deployment process.
• In online mode, users can leverage the autorun utility to launch HP SUM or browse the DVD to the \hp\swpackages directory and execute it directly. All firmware smart components are placed in the \hp\swpackages directory for use by HP SUM. If additional firmware smart components are required, then the HP Smart Update Firmware DVD can be copied to a USB key, and these additional components added to the \hp\swpackages directory.
Component Supported Mellanox NIC firmware Yes Power Management Controller firmware Yes Smart Array Controller firmware Yes SAS and SATA hard drive firmware behind Smart Array controllers Yes SAS and SATA hard drive firmware behind non-Smart Array controllers No Emulex, QLogic, and Brocade Fibre Channel Host Bus Adapter firmware Yes, offline only Tape blade firmware Yes Virtual Connect firmware* Yes, online only HP StorageWorks 600 Modular Disk System (MDS600)** Yes, offline only HP 3Gb S
Component Supported Onboard Administrator firmware, select the Force downgrade box from the Firmware Information section on the Onboard Administrator GUI screen. Select the firmware file by browsing locally or by locating a URL using the input boxes. For any limitations in using older Onboard Administrator firmware or other downgrade options, see the Onboard Administrator User Guide.
10. If additional components must be added to the USB, copy the components into the /hp/swpackages (Linux) or the \hp\swpackages (Windows® operating system) directory. If the version can support the type of components added, then HP SUM picks them up automatically. 11. Unmount the DVD and the USB key. This must match the initial mount point in step 4. umount /dev/cdrom umount /dev/sda1 12. Remove the USB key and DVD. Using a hard drive 1.
• The user does not temporarily disable BitLocker before flashing the System BIOS when using the Microsoft BitLocker Drive Encryption. • The user has optionally selected to measure iLO, Smart Array, and NIC firmware. If HP Smart Update Manager detects a TPM, a pop-up warning message appears. To enable firmware updates without the need to type in the TPM password on each server, the BitLocker Drive Encryption must be temporarily disabled.
6. Close all the windows, and then start the firmware update. To enable advanced startup options, use the following command: cscript manage-bde.wsf -protectors -disable c: When the firmware update process is completed, the BitLocker Drive Encryption support can be reenabled by following steps 1 through 4 but clicking Enabled in step 5 instead. The following command can be used to re-enable BitLocker Drive Encryption after firmware deployment has completed. cscript manage-bde.
If the TPM is detected and enabled with Option ROM Measuring, the installation is silent; the /tpmbypass switch is not given, and any firmware updated must be applied to the server. No pop-up warning appears. A new log file is generated (%systemdrive%\cpqsystem\log\cpqstub.log). Because the installation is silent, the installation is terminated and cannot continue. If the TPM is detected and enabled, the installation is silent, and the /tpmbypass switch is supplied. The installation occurs.
HP SUM User Interface Deployment scenarios HP SUM deploys firmware and software on a local host or one or more remote hosts. The remote hosts must be online and running the same operating system as the system running HP SUM. For example, when the remote hosts are running Linux, HP SUM must also be running on a Linux operating system. The following table describes when typical HP SUM deployment scenarios are used.
Deployment to multiple remote hosts NOTE: A remote host can be the IP address or DNS name of a remote server, remote iLO NIC port, Virtual Connect Ethernet or Fibre Channel Module for c-Class BladeSystem, or BladeSystem Onboard Administrator. To deploy components to multiple remote hosts using the GUI: 1. Ensure that all minimum requirements are met as described in "Minimum requirements (on page 7)." 2. Ensure that the components to be deployed are accessible to the administrative system.
Local host installations HP Smart Update Manager can deploy smart components on a local host or on one or more remote hosts. You can deploy components on a local host by using the HP Smart Update Manager GUI. To access the HP Smart Update Manager, see Deployment Options. Selecting the location to check for updates The Source Selections screen enables you to select components from a directory and the HP FTP site (ftp://ftp.hp.
When using HP SUM delivered with the Integrity support pack, the following screen appears when selecting the location to check for updates, since HP SUM does not support the ability to download the latest components from ftp.hp.com for these servers.
NOTE: HP Smart Update Manager does not support FTP over HTTP proxy. FTP downloaded from HTTP proxy fails. Components from the HP FTP site is only presented for selection on the Select Items to Install screen if their versions are newer than what is already on the system. If a system has all of the latest versions of firmware and software, no components from HP.com is presented on the Select Items to be Installed screen. NOTE: HP SUM does not support the ability to download the latest components from ftp.hp.
The Download Permission screen lists the available self-discovery components found on the HP FTP site. You can select or clear the updates you are downloading. The Download Permission screen includes the following buttons: • Select All—Selects all available components for download. • Clear All—Clears all components selected for download. • Cancel—Exits the Download Permission screen and returns to the Source Selections screen. • OK—Downloads all selected components.
The following columns are included in the Select Installation Host(s) screen: • Host Name—Displays the host IP address or DNS name. • Type—Categorizes the system as a host or group. • Last Used—Enables you to sort the list by the most recently used hosts. • Description—Displays the user-defined description given to a host. When the Remote Host or Group option on the Select Installation Host(s) screen is selected, you can sort your view of the host list by selecting Only Hosts, Only Groups, or Both.
To continue to system discovery, click Next and the discovery process occurs. If the system discovery process finds one or more predefined bundles, the Select Bundle Filter screen appears. Selecting bundles to filter When the discovery process is complete, the Select Bundle Filter screen appears. The Select Bundle Filter screen displays information about the predefined bundles available on your system and enables you to select which bundles to install.
The following image illustrates the Select Bundle Filter screen. The Set Options for Bundle Filter section allows you to set options for non-bundle product versions. o To view all versions of the products included in the bundle, select ALLOW NON-BUNDLE VERSIONS. This option enables you to include updates that might be newer than those released in the bundle. o To view updates of products not included in the bundle, select ALLOW NON-BUNDLE PRODUCTS.
Selecting components to install When the discovery process is complete and a bundle has been selected, the Select Items to be Installed screen appears. The Select Items to be Installed screen displays information about which components are available for installation on your system and enables you to select or clear components to install. The Select Items to be Installed screen includes the following sections: • Host—Lists the system on which the selected items are installed.
The Select Items to be Installed screen also includes the following buttons: • Select All—Selects all available components for installation. • Deselect All—Clears all components selected for installation. • Default—Restores the selections in the product installation pane to the default view, which is based on the existing configuration of the local system. • Exit—Exits HP SUM. • Install—Installs all selected components.
• Updates to be Installed—The components in this section can be installed on your system. • Optional Updates—The components in this section are not selected for installation by default, even if the product is not already installed or is installed but not up-to-date. To include the component in the installation set, you must select the component.
Icon Text Description Ready All selected components are ready to be installed. Already up-todate No component installation is required. None Selected No components are selected for installation. x Critical Action X components are not ready for installation due to failed dependencies, where x is the number of components. The installation cannot proceed until the dependencies are met or the component is deselected for installation.
NOTE: In Linux, the Reboot Delay time is automatically converted from seconds to minutes. Any value under a full minute, 59 seconds or less, will be rounded to the next minute for Linux. Make any changes, and click OK. NOTE: The reboot options do not apply when deploying firmware for HP Integrity BL860c/BL870c/BL890c i2 Servers. HP SUM reboots the server automatically during the firmware update process when the user has selected Upload and Activate for the firmware.
Icon Text Description Deselected by user The component has not been selected for installation. Excluded by Filtering The components excluded which are not applicable to the target server. Failed dependencies The component has a dependency that has not been met. To determine the nature of the failed dependency, click View Failed Dependencies. Build Failed The component build has failed. To view the Build.log, click the View build log link.
If a component displays as Build Failed, you must resolve the issue before proceeding with the installation. If a failed dependency occurs, then you must resolve it by ensuring the prerequisite libraries or the appropriate software or firmware components are available before proceeding with the installation.
The following figure displays the Failed Dependencies screen.
Installation options You can specify firmware upgrade behavior for installable components by selecting one or more options from the Additional Options field. Depending on the component type, one of the following screens appears. CAUTION: Updating the firmware while a shared device is in use can lead to data loss. Before enabling the Allow Shared Devices option, be sure any other servers sharing the selected devices are offline.
• Select Allow Rewrites to enable HP Smart Update Manager to overwrite the current firmware version with the same version. • Select Allow Shared Devices to upgrade firmware in a shared storage environment. NOTE: HP Smart Update Manager does not support Allow Downgrades or Allow Rewrites for the HP Virtual Connect Ethernet and Fibre Channel Modules for c-Class BladeSystem firmware component.
Viewing the installation results When the installation is complete, the Installation Results screen appears. The Installation Results screen is divided into the following columns: • Product—Specifies the name of the installed component. To view the component version history, click the version number. • Status—Specifies the installation status of the component. The following icons might appear in the Status column. Icon • Text Description Success The component was installed successfully.
Icon Text Description Reboot Needed The server must be rebooted for the component to take effect. NOTE: Some of the Linux RPMs require the target server to be rebooted after the RPM is Reboot Needed message does not appear on the Installation installed. However, the Results screen for Linux RPMs since that information is not available to HP SUM. HP recommends that you reboot the target server after installation of any Linux RPMs.
The following installation logs contain information about the installation activity for each host being updated: • hpsum_log.txt log—Contains a brief summary of the installation activity • hpsum_detail_log.
Virtual Connect Ethernet or Fibre Channel Module for c-Class BladeSystem, or BladeSystem Onboard Administrator. To add hosts, see "Managing hosts." To add groups, see "Managing groups (on page 50)." To continue with the deployment process: 1. Select one or more hosts or groups. 2. To continue, click Next. 3. Enter the credentials for the host. 4. Click OK to proceed, as described in Selecting components to install on multiple hosts. 5.
Managing hosts To add, edit, or delete hosts, click Manage Hosts. The Manage Hosts screen appears. A remote host can be the IP address or DNS name of the following: • Remote server • Remote iLO NIC port • Virtual Connect Ethernet or Fibre Channel Module for c-Class BladeSystem • BladeSystem Onboard Administrator NOTE: Local hosts cannot be included in a list with remote hosts or in a group.
To add a host: HP SUM User Interface 47
1. Click Add Host. The New Host dialog box appears. 2. Select the method to add a host from the following: o Enter the DNS name of the host you want to add. o Enter the IP address of the host you want to add. o Enter the IP address range of the hosts you want to add. The starting and ending IP addresses must both be on the same subnet. When using the IPv6 format, the last field in the ending address is limited to 32 targets.
1. On the Manage Hosts screen, click Edit Host. The Edit Host dialog box appears. 2. Edit the Host Name and Description. 3. Click OK. To delete a host: 1. On the Manage Hosts screen, click Delete Host. 2. When the confirmation screen appears, click Yes.
Managing groups To add, edit, or delete groups, click the Manage Groups button. The Manage Groups screen appears.
1. Click Add Group. The Edit Group dialog box appears. 2. Enter a group name. 3. Enter an optional user-defined description given to the group to be added. 4. Select the hosts to be added to the group from the Available Hosts pane. You can add new hosts from this screen by clicking the New Host button. For more information on adding hosts, see "Managing hosts." 5. Click the Enter button to move the selected hosts to the new group. 6. Click OK.
1. Select the group, and then on the Manage Groups screen, click the Edit Group button. The Edit Group dialog box appears. 2. Edit the group name as needed. 3. Edit the optional user-defined description given to the host as needed. 4. Click the Enter and Remove buttons to add or remove hosts as needed. 5. Click OK. To delete a group: 1. Select the group on the Manage Groups screen, and then click the Delete Group button. 2. When the confirmation screen appears, click Yes.
Entering credentials for hosts When you select a single remote host, the Enter Credentials for Host screen appears. You must enter your username and password as the credentials for the host. To enter the credentials for the host, choose one of the following: • Select Enter Username and Password, and then enter the username and password. • Select Use Current Credentials to use the credentials of the user currently logged in. This option is for Windows operating systems only.
When you select a group or multiple hosts, the Enter Credentials for Group screen appears. The screen separates the remaining hosts that still require credentials from the completed hosts. Each pane is divided into the following columns: • Name—Specifies the name of the host • Status—Specifies the credentials status of the host Icon • Text Description Entered The credentials for the host have been entered. Needs Credentials The credentials for the host have not been entered.
To enter the credentials for the host, perform the following steps: 1. In the left pane, select the host from the list of hosts requiring credentials. If all credentials are the same, to select all the hosts on the list, click Select All. 2. To enter the required credentials and move the selected host to the Completed Hosts pane, click Enter. 3. To continue, click Next.
HP SUM User Interface 56
Selecting bundles to filter on multiple hosts If the system discovery finds one or more predefined bundles, the Select Bundle Filter screen appears. If you specify a bundle on the command line when starting HP SUM, this screen does not appear. For more information about the screen, see "Selecting bundles to filter (on page 30)." To proceed with the installation process, click OK.
Selecting components to install on multiple hosts The Select Items to be Installed screen displays the server hosts and the status information. The Select Items to be Installed screen includes the following buttons: • View Host—Enables you to view additional information about a host after you select it. • Install—Installs all selected components on all remote hosts. The Install button is grayed out when a dependency failure occurs. • Exit—Exits HP SUM.
Icon Text Description Host Skipped Due to Existing HPSUM Session The host is skipped due to an existing HP Smart Update Manager session. Action Required The host is not ready for installation. Click View Host for additional information. Discovery Failed The host is not ready for installation. The detection of installed hardware, software, and firmware has failed. NOTE: The default reboot behavior after updates are installed might also appear in the Status column.
• Upload but Do not Activate—If you select this option, the firmware is activated the next time the server is rebooted.
If the user has not changed the default option or has selected Upload and Activate, a warning message displays, indicating that HP SUM will reboot the server during the firmware update process. To continue the update, press OK. You can deploy the Online System, FPGA, iLO-3 MP and Power Monitor firmware using CLI in silent mode. However, you cannot specify the Upload and Do not Activate mode using CLI. Only the default Update and Activate mode is available and no parameter is required.
Viewing the installation results for multiple hosts When the installation is complete, the Installation Results screen appears. The Installation Results screen is divided into the following columns: • Host—Specifies the IP address or DNS name of the host. • Status—Specifies the overall installation status of the components on the remote host. Icon Text Description Success The host was updated successfully. Nothing to install The host is already up-to-date.
To view single-host installation results, double-click or select the host, and then click View Host. Proceed as described in "Viewing the installation results (on page 42).
Scripted deployment Command-line interface The HP SUM command-line interface enables you to script custom installations.
Command-line arguments HP SUM recognizes the following command-line arguments. These arguments prepopulate the GUI in the Select Items to be Installed screen. If you specify the host or group, then the Select Items to be Installed screen does not appear. You cannot use some arguments, such as /romonly and /softwareonly together. Command-line argument Description Help /h[elp] or /? This argument displays command line Help information.
Command-line argument Description /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 /proxy_script This argument enables the inclusion of a proxy script to access ftp.hp.com. This parameter must be used with /use_web. For example, /use_web /proxy_script /use_d[ownloaded] This argument specifies that the checkbox for Include components previously downloaded from HP.com on the Source Selection screen is selected. This enables those previously downloaded components to be included in the list of possible updates.
Command-line argument Description /on_failed_dependen cy This argument tells HP SUM how to proceed when a component has a failed dependency. The default of OmitHost causes the host to be put in a failure state and no install is attempted on it. OmitComponent deselects the affected component(s) and proceeds with any updates that do not have dependency failures. Force attempts all updates, even if they have dependency failures.
Command-line argument Description /target "netAddress" This argument is the IP address or the DNS name of a remote server, remote iLO NIC port, Virtual Connect Ethernet or Fibre Channel Module for c-Class BladeSystem, or BladeSystem Onboard Administrator. When two Onboard Administrators are in an enclosure, this argument should be the active Onboard Administrator. When specifying the IP address, you can use either the IPv4 or IPv6 format.
Command-line argument Description has been read in. Component configuration for Windows components only To configure components without using the HP Smart Update Manager GUI, issue the command, hpsum_config . This command presents the same configuration screens seen in the HP Smart Update Manager GUI. You must run this command from a CD or other read-only media, or the component cannot be configured. Configuration for a given component only needs to be executed once.
Either of the following command-line inputs can deploy the previous version of the PSP only and force all the components to be installed: • hpsum /f:bundle /softwareonly BP000315.xml • hpsum /b BP000315.xml /f:bundle /softwareonly Results: All software components from the 7.80 PSP, which HP SUM determined are required to be installed, were installed. No firmware was installed.
Return code Value Linux Windows ® Text SUCCESS_NO_REBOOT 0 0 0 The installation was successful. SUCCESS_REBOOT 1 1 1 The installation was successful, but a reboot is required. SUCCESS_NOT_REQUIRED 3 3 3 The component was current or not required. FAILURE_GENERAL -1 255 255 A general failure occurred. For details, see the error log. FAILURE_BAD_PARM -2 254 254 A bad input parameter was encountered. FAILURE_COMPONENT_FAILED -3 253 253 The installation of the component failed.
Error level Meaning 3 The installation was not attempted because of one of the following: • • The version to be installed is older than the version already installed. • • The smart component does not support the environment. The supported hardware is not present, not enabled, or in a state that an installation could not be attempted. There is nothing for the component to accomplish.
Command-line usage of input file The form for the HP SUM command line using an input file is hpsum -inputfile[enc] . The optional -enc ending to the -inputfile flag indicates that the input file is encrypted. 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 field can be enclosed in double quotes to enable paths with spaces.
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__
Parameter Description Possible values 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. SKIPTARGET This parameter defines the behavior when a remote target has an existing HP SUM session in progress. YES, NO This parameter enables you to skip the host if an existing HP SUM session already exists.
Parameter Description Possible values for installation. These components are optional by default and are not installed unless this parameter is used. When the /usewmi parameter is used, and the /usesnmp parameter is not used, the SNMP components are optional. ROMONLY SOFTWAREONLY USECURRENTCREDENTIAL This parameter is a filter switch and allows the user to view only the firmware components required for installation. YES, NO Do not use the /romonly parameter with the /softwareonly parameter.
Parameter Description Possible values enclosure, this parameter is the active Onboard Administrator. When specifying the IP address, you can use either the IPv4 or IPv6 format. This parameter specifies an already defined group name in the HP SUM GUI. UID This parameter enables you to log in to the target hosts with your user ID. PWD This parameter enables you to use the password for the user ID specified in the UID. The password is used to log in to target hosts.
Parameter Description Possible values Linux PSP only.) CMATRAPDESTINATIONIP ORDNS This parameter enables you to specify the IP address or DNS host name of a server as a destination for SNMP traps, such as Systems Insight Manager. (Applies to Linux PSP only.) IP address, DNS name CMASYSCONTACT This parameter enables you to specify a person or phone number for administration of this system. (Applies to Linux PSP only.
Parameter Description Possible values ANONYMOUS-ACCESS This parameter determines whether an anonymous user can access the HP Systems Management Homepage. (Applies to Linux PSP only.) YES, NO (default) IP-BINDING This parameter is used by the HP Systems Management Homepage to determine whether hpsmh can use all available NICs and detect subnets for its web services. (Applies to Linux PSP only.
Parameter Description Possible values name or password. TRUSTMODE This parameter is used by the HP Systems Management Homepage to set up the trust relationship mode. (Applies to Linux PSP only.) • TrustByCert—If this value is used, the CERTLIST parameter must be defined to enable access to the server. • TrustByName—If this value is used, the XENAMELIST parameter must be defined. • TrustByAll—HP does not recommend using this value because of possible negative security consequences.
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 OPTIONS = /f:rom [TARGETS] HOST = schinta1 HOST = schinta2 UID = root PWD = root123 HOST = 234.567.765.432 [END] USAGE: hpsum /inputfile Examples of inputfile.
[TARGETS] HOST = BL685cG6 UID = Bigboss2 PWD = password [END] Example 3 SILENT = YES IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies SKIPTARGET = NO SOURCEPATH = C:\fwcd\firmware-8.70-0\hp\swpackages [GROUPS] HOST=winserver UID=Userid PWD=password [END] Example 4 SILENT = YES IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies SKIPTARGET = NO SOURCEPATH = C:\ fwcd\firmware-8.
Reports HP SUM can generate three types of reports about the specified system or repository. You can only generate the reports using the command-line arguments provided. If no additional arguments are specified on the command line, the local host and default repository locations (the directory where HP SUM was initiated) are used. You can specify a target with appropriate credentials and a repository using other command-line parameters if you want to generate reports for other systems and repositories.
The following figure illustrates the HP SUM report in HTML format.
The following figure illustrates the HP SUM Inventory report in HTML format.
The following figure illustrates the HP SUM Firmware report in HTML format.
Advanced topics Software component configuration Some components might have required or optional configuration settings. Configuration parameters can include information necessary to set up the component correctly or passwords required for software installed by the component. If the optional configuration data of a component is not provided and the component has not been installed previously, then default values for that configuration data are used.
Deploying firmware and software simultaneously This topic applies to ProLiant servers and options supported by the server, but does not apply to Integrity servers. HP SUM utility enables you to deploy firmware and software components simultaneously. The latest firmware and software components must be located in the same directory. To deploy firmware and software components simultaneously, select the location where the firmware and software components are located in the Source Selections screen.
connects to the admin$ share, it copies a small service to the target server for the duration of the installation. After this service starts, HP Smart Update Manager uses this service to communicate between the local and remote target server. During this process, HP Smart Update Manager opens ports in the Windows® firewall to enable HP Smart Update Manager to use SOAP calls over SSL to pass data among local and remote systems.
short-name and full IPv6 notation. You do not need to add the optional interface number when you enter the address. If you cannot connect to the target server or receive a Discovery failed message when executing HP Smart Update Manager in an IPv6 environment, see the troubleshooting section ("Troubleshooting HP Smart Update Manager in IPv6 networks" on page 105). After you connect to the target server, all other HP Smart Update Manager functions work identically.
addresses for both local and remote target servers. Windows Vista®, when used as a client to run HP Smart Update Manager to remote Windows Server® 2008 operating systems or as a target operating system on HP Workstation server blades, provides the infrastructure that supports full IPv6 deployment of software and firmware updates from HP Smart Update Manager. NOTE: Windows® XP clients are not supported in IPv6 networks for HP Smart Update Manager deployment.
If you cannot connect to the target server or receive a Discovery failed message when executing HP Smart Update Manager in an IPv6 environment, see the troubleshooting section ("Troubleshooting HP Smart Update Manager in IPv6 networks" on page 105). After you connect to the target server, all other HP Smart Update Manager functions work identically. Log files for IPv6 hosts are stored with all other HP Smart Update Manager files in the \CPQSYSTEM\hp\log\ directory.
IPv6 addresses can be passed to HP Smart Update Manager in command line arguments or using the HP Smart Update Manager user interface. In the HP Smart Update Manager user interface, you can add a remote host on an IPv6 network by either entering the DNS name of the IPv6 target server or by selecting the IPv6 address button and entering the IPv6 address. HP Smart Update Manager supports both the short-name and full IPv6 notation.
Limitations of IPv6 for Linux The only current limitation of HP Smart Update Manager in a Linux IPv6 environment is that all remote target Linux-based servers must have the iptables-ipv6 rpm file installed. You can find the file on the distribution media for both Red Hat Enterprise Linux and Novell SUSE Linux Enterprise Server operating systems. HP Smart Update Manager uses this file to open a port in the IPv6 firewall to communicate with the Linux system that runs HP Smart Update Manager.
Troubleshooting Recovering from a failed ROM upgrade Recovering from a failed system ROM upgrade Use redundant ROM or ROMPaq to recover from a system ROM upgrade failure. Redundant ROM recovery When you flash the system ROM, ROMPaq writes over the backup ROM and saves the current ROM as a backup, enabling you to switch easily to the alternate ROM version if the new ROM becomes corrupted for any reason.
6. Power up the server. The server generates one long beep and two short beeps to indicate that it is in disaster recovery mode. If the disk is not in the correct drive, then the system continues to beep until a valid ROMPaq disk is inserted. The ROMPaq disk flashes both system ROM images. If successful, a sequence of ascending audible beeps is generated. If unsuccessful, a sequence of descending audible beeps is generated, and you must repeat the disaster recovery process. 7. Power down the server. 8.
Recovering from an installation failure Collecting trace directories HP Smart Update Manager generates a set of debug trace logs located in the %TEMP%\hp_sum directory on Windows systems and \tmp\hp_sum on Linux systems. These files contain internal process and debug information, which can be useful in determining HP Smart Update Manager failures. NOTE: To break out to a Linux console while booted to the HP Smart Update Firmware DVD, press Ctrl Alt d b x. Each key (d, b, x) is hit in succession.
The following is an example of the output trace in the OpMan.trace on how to determine if a component was prevented from being shown on the Select Items to Install screen or being deployed from the silent console mode. In the example, the binary image files 0.bin and 1.bin (which represented iLO firmware files), components cp011301.exe and cp011500.exe, and the HP BladeSystem Firmware Update Bundle for Windows represented by bundle file bp000648.xml were added to the installation set.
• In rare cases, external storage enclosures might cause HP SUM to report a discovery failure or to hang. To resolve this issue, disconnect the external storage until the firmware updates are completed. • For Linux, ensure that the target server can be contacted through SSH and that the scp command is available to securely send files to the target server. • Ensure the firewall ports on any routers in the network as documented in the Enabling ports in HP Smart Update Manager section of this document.
Recovering from a blocked program on Microsoft Windows Configuring Windows firewall settings The Windows® Security Alert appears when a program is blocked from accepting connections from the Internet or a network. To set the rules for the Windows® Firewall and Security Policy, click Unblock, and then set your firewall settings to the following: 1. Click Start>Control Panel>Administrative Tools>Windows Firewall with Advanced Security>Inbound Rules>Remote Administration (NP-IN). 2.
scanning software from denying service to the application. The SOAP server is deployed on the remote target using the initial ports described above (ports 138, 445, and 22) and then allocates another independent port as documented below for its communications back to the workstation where HP Smart Update Manager is running. During shutdown of HP Smart Update Manager, the SOAP server is shutdown and removed from the target server, leaving the log files.
Ports 60000-60007 Random ports are used in this range to pass messages back and forth between the local and remote systems via SSL. These ports are used on the system running HP Smart Update Manager to send data to the target server. Several internal processes within HP Smart Update Manager automatically use the port from 60000 when no other application uses it. If there is a port conflict, the manager uses the next available one.
For a successful reboot, you must click Exit. When the message is entered using CLI, the reboot message looks corrupted since the Japanese character set is not supported in CLI. Recovering from Fatal Error - application will exit message Running in a directory path containing double-byte characters When running in a directory path containing double-byte characters, the HP Smart Update Manager encounters a fatal error while trying to initialize.
Recovering a lost HP Smart Update Manager connection HP Smart Update Firmware DVD mounted using iLO virtual media When either iLO and NIC firmware are updated, the HP SUM connection is lost and cannot install components. Booting the Firmware DVD from iLO virtual media is only supported in Offline Automatic Firmware Update mode. Users attempting to boot in this manner might experience issues from connection timeouts, difficulties updating iLO firmware, and mouse syncing issues.
NOTE: You do not need to use the .ipv6-literal.net suffix when entering IPv6 address into the HP Smart Update Manager user interface or when passing IPv6 address using command line parameters to HP Smart Update Manager. After you validate that you can access the admin$ share on the remote target server, HP Smart Update Manager works unless other network or hardware issues exist.
• Ensure you can ping the IPv6 loopback address: ping6 ::1. • Use the DNS hostname instead of IPv6 address to ensure the address is correct. • Use ipconfig to validate you have IPv6 addresses assigned to your NICs. For more information about troubleshooting your configuration, see the Linux IPv6 How-To (http://www.linux.org/docs/ldp/howto/Linux+IPv6-HOWTO/index.html). • For more information about setting up and troubleshooting IPv6 networks, see Getting Around IPv6 by Carla Schroder (http://www.
Linux component version discrepancy for source RPMs You might observe differences in the RPM component name which might appear to be a version mismatch for the component on the Select Item to be Installed screen and the Installation Results screen. This is caused by the RPM build phase. The resulting component is actually the same version. The RPM build adds information, so it is technically the same component.
To resolve this issue, make sure to select the bundle for the OS distribution on the Select Bundle Filter screen for installation or remove the RPMs from the directory that are not applicable to the Linux distribution you are using. Issues related to bundle filtering on the Select Items to be Installed and Select Bundle Filter screens If you specify a bundle to use for installation when starting HP SUM (for example, hpsum /b bp000690.
If you specify a bundle when starting HP SUM, then the Select Bundle Filter screen is not shown and the Select Items to be Installed screen appears with the specified bundle listed as the filter. This is expected, as a bundle was preselected.
If you then select the Select Bundle Filter link, then the Select Bundle Filter screen appears with no bundles available for selection. This issue occurs because HP SUM only recognizes the specified bundle and no others, even if other bundles are present in the repository. Even though this issue occurs, HP SUM is working as designed. • No bundle being used as a filter on the Select Items to be Installed screen.
If you experience the first issue and then select OK on the Select Bundle Filter screen to return to the Select Items to be Installed screen, the bundle you originally specified is no longer listed as the filter. To use your bundle as the filter, you must exit and restart HP SUM. This error will be fixed in the future release of HP SUM. If this issue occurs, from the GUI run HP SUM.
Technical support Reference documentation • To download the ProLiant Firmware Maintenance CD, Smart Update Firmware DVD, SmartStart, and other CD/DVDs, see the SmartStart download website (http://www.hp.com/go/ssdownloads). • For information about firmware support, see the ProLiant Firmware Maintenance CD/DVD Matrix (http://www.hp.com/servers/smartstart/supportmatrices). • For information about SmartStart support, see the SmartStart support matrices (http://www.hp.
Operating system information For information about Microsoft® Windows® operating systems, refer to 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.novell.com/linux) 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).
Acronyms and abbreviations CLI Command Line Interface FPGA Field Programmable Gate Array GUI graphical user interface HBA host bus adapter HP SUM HP Smart Update Manager I/O input/output iLO Integrated Lights-Out iLO 2 Integrated Lights-Out 2 iLO 3 Integrated Lights-Out 3 ISP Integrity Support Pack NIC network interface controller OA Onboard Administrator Acronyms and abbreviations 115
POST Power-On Self Test PSP HP ProLiant Support Pack RBSU ROM-Based Setup Utility RDP Rapid Deployment Pack RILOE II Remote Insight Lights-Out Edition II SAN storage area network SAS serial attached SCSI SCSI small computer system interface SEP Symantec Endpoint Protection SOAP Simple Object Access Protocol SSH Secure Shell SSL Secure Sockets Layer VC Virtual Connect VCA Version Control Agent Acronyms and abbreviations 116
VCRM Version Control Repository Manager WMI Windows Management Instrumentation Acronyms and abbreviations 117
Index A adding groups 50 advanced topics 88 Allow Downgrades 40 Allow Rewrites 40 Allow Shared Devices 40 authorized reseller 113, 114 B blocked HP Smart Update Manager, recovering from 101 bundle filter options 30, 57 C CLI (Command Line Interface) 109 command line arguments 65 command line arguments, component 65 command line examples 70 command line examples, PSPs in Windows 70 command line interface, using 64 command line syntax 64 command-line usage of input file 74 component configuration 88 compone
HP Integrity servers 22 HP ProLiant Firmware Maintenance DVD, deployment options 19 HP ProLiant Servers 16 HP Smart Update Firmware DVD 15 HP website 114 minimum requirements for Windows servers 7 mounting virtual media 105 multiple hosts, filtering bundles 57 multiple remote hosts, deployment 24 I new features 7 NIC firmware 40 non-matching system error 107 iLO (Integrated Lights-Out) 105 input file parameters 74, 75 input file, command-line age 74 installation host 28 installation issues 98, 108 insta
ROM recovery, redundant 96 ROM redundancy 96 ROM upgrade behavior 40 ROM upgrade, recovering from failed option 97 ROM upgrade, recovering from failed system 96 ROM, array controller 97 ROM, Lights-Out management 97 ROM, storage 97 ROMPaq Disaster Recovery 96 RPM return codes, Linux 73 S scenarios, deployment 23 scenarios, overview 23 scripted deployment 23, 24, 64 Select Bundle Filter screen 109 selecting an installation host 28 selecting bundles to filter for the first time 30 selecting components to ins
