HP Smart Update Manager Help

Contents

Introduction
        HP Smart Update Manager Overview
        New features of HP Smart Update Manager 4.0.1
        Minimum requirements
                Minimum requirements for Windows® servers
                Minimum requirements for Linux servers
        Obtaining the HP Smart Update Manager Utility
        Deployment from HP Smart Update Manager
                Executing HP Smart Update Manager
                Deploying PSP for Windows®
                Deploying PSP for Linux
                Deploying Firmware from the HP Smart Update Firmware DVD

HP Smart Update Manager User Interface
        Deployment scenarios
                Graphical deployment on a local host
                Scripted deployment on a local host
                Deployment to multiple remote hosts
        Keyboard support
        Local host installations
                Selecting an installation host
                Selecting bundles to filter
                Selecting components to install
                Viewing the installation results
        Multiple-host installations
                Selecting remote hosts or groups
                Selecting bundles to filter on multiple hosts
                Selecting components to install on multiple hosts
                Viewing the installation results for multiple hosts

Scripted Deployment
        Command line interface
        Return codes
        Input files
                Command line usage of input files
                Input file format and rules
                File Encoding
                Error Reporting
                Input file parameters
        Reports

Advanced Topics
        Component configuration
        Deploying firmware and software simultaneously
        Server virtualization detection and support
        Configuring IPv6 networks with HP Smart Update Manager

Troubleshooting
        Recovering from a failed ROM upgrade
        Recovering from an installation failure
        Recovering from a discovery failure
        Recovering from a loss of Linux remote functionality
        Recovering from a blocked program on Microsoft Windows®
        Troubleshooting HP Smart Update Manager in IPv6 Networks
        Enabling ports in HP Smart Update Manager
        Recovering from operating system limitations when using a Japanese character set
        Recovering from Fatal Error - application will exit message
        Recovering from a missing reboot message when running on SUSE LINUX Enterprise Server 9
        Recovering a lost HP Smart Update Manager connection
        HP SUM 'Found new hardware' message
        Non-matching systems error reported when building Source RPMs or installing RPMs built from source
        Linux component version discrepancy for source RPMs
        HP SUM displays "No components found in the selected repository(ies)" message
        Additional/Optional actions coloums is grayed when HP Smart Update Manager is maximized
        Installation of components failed with 'Update returned an error'
        Issues related to bundle filtering on the Select Items to be Installed and Select Bundle Filter screens

Technical Support

Acronyms and abbreviations
 

Introduction

In this section

HP Smart Update Manager Overview
New features of HP Smart Update Manager 4.0.1
Minimum requirements
        Minimum requirements for Windows® servers
        Minimum requirements for Linux servers
Obtaining the HP Smart Update Manager utility
Deployment from HP Smart Update Manager
Executing HP Smart Update Manager
Deploying PSP in Windows®
Deploying PSP in Linux
Deploying Firmware from the HP Smart Update Firmware DVD
 

HP Smart Update Manager Overview

HP Smart Update Manager provides a GUI and a command-line, scriptable interface for HP Smart Update Manager has an integrated hardware and software discovery engine that discovers the installed hardware, current versions of software and firmware in use on target servers. This capability prevents extraneous network traffic by sending only the required components to a target host. HP SUM installs updates in the correct order and ensures all dependencies are met before deployment of an update. HP SUM prevents version-based dependencies from destroying an installation and ensures updates are handled in a manner that reduces any downtime required for the update process.

HP Smart Update Manager does not require an agent for remote installations as it copies a small, secure SOAP server to the target server for the duration of the installation. After the installation is complete, the SOAP server and all remote files associated with the installation except installation log files are removed. HP Smart Update Manager copies the log files from the remote targets back to the system where HP Smart Update Manager is executed.

Key features of HP SUM include:


 

New features of HP Smart Update Manager 4.0.1


 

Minimum requirements

In this Section:

Minimum requirements for Windows® servers
Minimum requirements for Linux servers

Minimum requirements for Windows servers

To successfully deploy HP Smart Update Manager on target systems based on a Microsoft® Windows® operating system, the following must be available:


 

Minimum requirements for Linux servers

To successfully deploy HP Smart Update Manager on target systems based on a Linux operating system, the following must be available:

To successfully deploy HP Smart Update Manager for deployment on remote target systems based on a Linux operating system, the following must be available:

Starting with Linux ProLiant Support Pack 8.40 and later, ensure the following Platform-specific libraries are also installed.


 

Obtaining the HP Smart Update Manager Utility


 

Deployment from HP Smart Update Manager

In this Section:

Executing HP Smart Update Manager
Deploying PSP for Microsoft Windows®
Deploying PSP for Linux
Deploying Firmware from the HP Smart Update Firmware DVD

Executing HP Smart Update Manager

 IMPORTANT:  Before deploying software updates to a target server, be sure that a recent backup of the target server is available in the event the deployment procedure fails.

 

Deploying ProLiant Support Packs for Microsoft Windows

Beginning with the ProLiant Support Pack for Microsoft® Windows® version 7.90 or later, the HP Smart Update Manager utility enables you to deploy Windows® PSP software and firmware components from a single, easy-to-use interface. This utility enables legacy support of existing software and firmware components while simplifying the overall deployment process. You do not have to run the SETUP executable files SETUPC.EXE, SETUPEX.EXE, and SETUP.EXE), because the HP Smart Update Manager utility now 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.

Beginning with the ProLiant Support Pack for Microsoft® Windows® version 7.90 or later, users can now deploy firmware and software components simultaneously. For more information about this feature, see Deploying firmware and software simultaneously.

For more information, see the HP ProLiant Support Pack for Windows and Linux User Guide on the HP website (http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=345557).
 

Deploying ProLiant Support Packs for Linux

Beginning with the ProLiant Support Pack for Linux 8.40 or later, the HP Smart Update Manager utility enables you to deploy Linux PSP software and firmware components from a single, easy-to-use interface. The same manageability is present with added flexibility and more features for added convenience and enhanced functionality. HP Smart Update Manager provides new GUI and a command-line, scriptable interface for deployment to target servers. HP Smart Update Manager discovers and displays all components that are available for installation on the local system and enables the flexibility to choose which components to install or not install. Additionally, the HP Smart Update Manager utility enables software deployment for multiple HP ProLiant servers from a single GUI.

For more information, see the HP ProLiant Support Pack for Windows and Linux User Guide on the HP website (http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=345557).
 

Deploying Firmware from the HP Smart Update Firmware DVD

The HP Smart Update Firmware DVD provides a collection of firmware bundles containing HP SUM and firmware in an ISO image that can be used either in offline (either an automatic or interactive mode), or online (either a scripted or interactive mode). The HP Smart Update Firmware DVD provides firmware for supported HP servers and options. The Firmware DVD contains all the firmware for the supported HP ProLiant servers including BladeSystem enclosures and Virtual Connect firmware.

  • In offline mode, the HP Smart Update Firmware DVD boots a small Linux kernel and enables firmware updates to occur on a single server using the embedded HP SUM software.
  • 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 needed, the HP Smart Update Firmware DVD can be copied to a USB key, and these additional components added to the \hp\swpackages directory. If HP SUM supports the type of firmware added, it is automatically added the next time HP SUM is executed.

     CAUTION:  The HP Smart Update Firmware DVD and its contents must be used only by individuals who are experienced and knowledgeable with HP Smart Update Manager. Before using HP Smart Update Manager to update firmware, back up the target server, and take all other necessary precautions so that mission-critical systems are not disrupted if a failure occurs.

    HP Smart Update Manager stores host and group information from session to session. However, user names, passwords, and existing credentials are not stored in a session or from session to session.

    Use OA version 2.51 or later to get a list of all major firmware versions deployed in your enclosure, using the Rack Firmware link on the main OA web page. HP supports the current and two previous versions of the Smart Update Firmware DVD.

    NOTE: The Onboard Administrator and Virtual Connect Ethernet and Fibre Channel Modules are supported only in online deployments.

    NOTE: You can add firmware components to the USB drive key in the /hp/swpackages directory.

     IMPORTANT:  Before deploying firmware updates on a target server, be sure that a recent backup of the target server is available in the event the deployment procedure fails.

    For more information, see the HP Smart Update Firmware DVD User Guide on the HP website. (http://h18004.www1.hp.com/products/servers/proliantessentials/foundationpack/index.html or http://h18004.www1.hp.com/products/servers/management/core-management-100.html).
     

    HP Smart Update Manager Supported Firmware

    The HP Smart Update Manager provides support for the following firmware:

    ComponentSupported by HP Smart Update Manager
    System ROMYes
    iLO 2 firmwareYes, local and remote
    iLO 3 firmwareNo
    Broadcom NIC firmwareYes
    Intel NIC firmwareNo
    QLogic NIC firmwareYes
    Mellanox NIC firmwareYes
    Power Management firmwareYes, beginning with Firmware Maintenance CD 8.60
    Smart Array controller firmwareYes
    SAS and SATA hard drive firmware behind Smart Array controllersYes
    SAS and SATA hard drive firmware behind non-Smart Array controllersNo
    Emulex, QLogic, and Brocade Fibre Channel Host Bus Adapter firmwareYes, offline only
    Tape blade firmwareYes
    Virtual Connect firmware*Yes, online only
    HP StorageWorks 600 Modular Disk System (MDS600 )**Yes, offline only
    HP 3Gb SAS BL Switch firmware***No
    Onboard Administrator firmware****Yes, online only
    HP Workstation Blade ROMYes, offline only
    HP ProLiant Blade Server ROMYes
    HP ProLiant 100 Series Server ROMYes

    * Virtual Connect firmware components can also be downloaded from the HP website and they can be added to the HP Smart Update Firmware DVD by creating a USB key using the USB Key Utility. The latest version can be obtained from the HP BladeSystem Firmware Maintenance website (http://www.hp.com/go/bladesystemupdates).

    ** MDS600 firmware update requires HP SUM 3.6.0 or later. All blades in an enclosure with Smart Array P700M controllers, except the blade doing the update, must be turned off before the firmware update process is initiated. MDS600 firmware can only be updated using the HP Smart Update Firmware DVD in offline mode.

    *** The HP 3Gb SAS BL Switch firmware can only be updated by uploading a bin file through the VSM product. This firmware is currently delivered as a binary image file on the HP website and must be downloaded and manually upgraded.

    Because firmware might be able to update only in online or offline mode for some components, you might need to execute the HP Smart Update Firmware DVD both online and offline to update all the firmware in an enclosure.

    Because firmware might be able to update only in online or offline mode for some components, you might need to execute the HP Firmware Maintenance DVD both online and offline to update all the firmware in an enclosure.

    **** Downgrading the Onboard Administrator firmware from a new major release to an older release version (for example, 3.x to 2.x) is not supported in HP SUM. Downgrading to a minor version from within a major version is supported (for example, 2.60 to 2.52). To manually install a previous version of the 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.
     

    HP USB key utility

    The HP USB Key Utility enables you to copy the HP Smart Update Firmware DVD contents to a USB memory key. You can then run the Firmware Update applications from a USB key instead of from the DVD. Insert a USB key containing the Firmware DVD ISO image created by using the HP USB Key Creator for Windows utility into the SUV (Serial-USB-Video) cable attached to the blade if the blade server supports the SUV cable.

    For Windows® operating systems, the HP USB Key Creator for Windows® utility must be downloaded from the HP website (http://www.hp.com) and installed on a workstation. Once installed, the utility places a shortcut in the HP System Tools in the Programs start menu folder.

    To create your drive key bootable and copy the contents of the DVD:


     

    Using a hard drive


     

    Deploying components not on HP Smart Update Firmware DVD


     

    Trusted Platform Module (TPM)

    The Trusted Platform Module, when used with BitLocker, measures a system state and, upon detection of a changed ROM image, restricts access to the Windows® file system if the user cannot provide the recovery key. HP Smart Update Manager detects if a TPM is enabled in your system. If a TPM is detected in your system or with any remote server selected as a target, for some newer models of ProLiant, HP Smart Update Manager utilities for iLO, Smart Array, NIC, and BIOS warn users prior to a flash. If the user does not temporarily disable BitLocker and does not cancel the flash, the BitLocker recovery key is needed to access the user data upon reboot.

    A recovery event is triggered if:

    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. Disabling the BitLocker Drive Encryption keeps the hard drive data encrypted. However, BitLocker uses a plain text decryption key that is stored on the hard drive to read the information. After the firmware updates have been completed, the BitLocker Drive Encryption can be re-enabled. Once the BitLocker Drive Encryption has been re-enabled, the plain text key is removed and BitLocker secures the drive again.

    NOTE: Temporarily disabling BitLocker Drive Encryption can compromise drive security and should only be attempted in a secure environment. If you are unable to provide a secure environment, HP recommends providing the boot password and leaving BitLocker Drive Encryption enabled throughout the firmware update process. This requires the /tpmbypass parameter for HP Smart Update Manager or the firmware update is blocked.

    To temporarily disable BitLocker support to allow firmware updates, perform the following:

    To enable advanced startup options, use the following command:

    When the firmware update process is completed, the BitLocker Drive Encryption support can be re-enabled 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.



      TPM scenarios

    The following table discusses the TPM detection scenarios that you might encounter:

    ScenarioResult
    If the TPM is detected and enabled, the installation is not silent, and a system ROM needs to be updated.A pop-up warning message appears. After OK is selected, you are allowed to continue. The installation is not cancelled due to the detection.
    If the TPM is detected and enabled, the installation is silent, the /tpmbypass switch is not given, and any firmware updated needs to 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 not allowed to continue.
    If the TPM is detected and enabled with Option ROM Measuring, the installation is not silent, and a system ROM needs to be updated.A pop-up warning message appears. After OK is selected, you are allowed to continue. The installation is not cancelled due to the detection.
    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 needs to 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 not allowed to continue.
    If the TPM is detected and enabled, the installation is silent, and the /tpmbypass switch is supplied. The installation is allowed as if TPM were not detected.

    All other scenarios will not hinder the normal installation procedure
     

    HP Smart Update Manager User Interface

    In this Section:

    Deployment scenarios
            Graphical deployment on a local host
            Scripted deployment on a local host
            Deployment to multiple remote hosts
    Keyboard support
    Local host installations
            Selecting an installation host
            Selecting bundles to filter
            Selecting components to install
            Viewing the installation results
    Multiple-host installations
            Selecting remote hosts or groups
            Selecting bundles to filter on multiple hosts
            Selecting components to install on multiple hosts
            Viewing the installation results on multiple hosts

    Deployment scenarios

    HP Smart Update Manager deploys firmware and software smart components and Linux RPMS 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 Smart Update Manager. For example, when the remote hosts are running Linux, the HP Smart Update Manager must also be running on a Linux operating system.

    The following table describes typical HP Smart Update Manager deployment scenarios.

    Scenario Description
    Graphical deployment on a local host Use this scenario when you:
    • Are not familiar with command line tools
    • Are deploying components on a local, single-host
    • Do not require scripting
    Scripted deployment on a local host Use this scenario when you:
    • Are familiar with command line tools
    • Are deploying components on a local, single-host
    • Must perform a customized, scripted deployment
    Graphical deployment to a remote host Use this scenario when you:
    • Are not familiar with command line tools
    • Are deploying components on one or more remote hosts
    • Do not require scripting
    Scripted deployment to a remote host Use this scenario when you:
    • Are familiar with command line tools
    • Are deploying components on one or more hosts
    • Must perform a customized, scripted deployment to one or more host systems

     

    Graphical deployment on a local host

    The easiest way to deploy components to a local, single-host is to use the HP Smart Update Manager graphical interface.

    To deploy components to a local host using the GUI:

    1. Ensure that all minimum requirements are fulfilled as described in "Minimum requirements."
    2. Ensure that the components to be deployed are accessible to the local host.
    3. For more information about performing the deployment using the graphical interface, see "Local host installations" .

     

    Scripted deployment on a local host

    To deploy components to a local host using the command line interface:

    1. Ensure all minimum requirements are fulfilled as described in "Minimum requirements."
    2. Ensure that the components to be deployed are accessible to the local host.
    3. Create a script to customize the deployment. See "Command line interface" for more information.
    4. Execute the script.

     

    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.

    The following figure illustrates the multiple-host deployment process.

    To deploy components to multiple remote hosts using the GUI:


     

    Keyboard support

    The HP Smart Update Manager graphical user interface has accelerator keys that enable you to manage and control common tasks quickly. To ensure proper navigation, the following are a few reminders.
     

    Local host installations

    HP Smart Update Manager can deploy smart components on a local host or on one or more remote hosts. You can easily deploy components on a local host by using the Smart Update Manager GUI.

    Selecting the location to check for updates

    The Source Selections screen enables you to select components from a directory and/or the HP ftp site (ftp.hp.com) as a location for obtaining updates to your systems. You can also select components that have already been downloaded. You can use one or up to all three of these methods simultaneously.

    NOTE: For offline deployments, the Source Selections screen does not appear.

    The Source Selections screen enables you to specify where to get components for updating the targets by using one or more of the following methods:

    To begin the inventory process, click Start Inventory. The Inventory Progress screen appears while the HP Smart Update Manager builds an inventory of available updates.
     

    Download Permission

    Before starting any discovery, HP SUM searches the web digest for self-discovery components that need to be downloaded for the discovery process. Self-discovered components are components including but not limited to NIC firmware and tape firmware that HP Smart Update Manager uses to discover the hardware in the system. If the Check ftp.hp.com checkbox has been selected on the previous screen, the Download Permission screen may appear if there are self discovery components that are available for download.

    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 allowing to download. The Download Permission screen includes the following buttons:

    For more information on selecting the location for updates, see "Selecting the location to check for updates".
     

    Selecting an installation host

    To continue with the deployment process using a local host, select a host from the Select Installation Host(s) screen, and click Next.

    The Select Installation Host(s) screen enables you to choose a host for component installation. By default, the first time you run the HP Smart Update Manager on a particular system, the only host available is local host. However, you can select remote hosts as your target by using the GUI. For more information about using the graphical interface for multiple remote deployments, see "Multiple-host installations"

    The following columns are included in the Select Installation Host(s) screen:

    When the Remote Host or Group option in the Select Installation Host(s) screen is selected, you can sort the host list by selecting to view only the hosts, the groups, or both.

    The Select Installation Host(s) screen also includes the following buttons:

    NOTE: When running on a Linux system and the expect-5.x package is not installed, HP Smart Update Manager displays a pop up error message reporting that the package is missing and you are not able to deploy to remote systems. However, you can still deploy to the local host. To do a remote deployment, exit HP Smart Update Manager, and then install the expect-5.x package from the Linux operating system media. To proceed with remote deployment, start HP SUM..

    To continue the system discovery, click Next. For multiple remote deployments, enter the credentials for the host. When the credentials have been successfully entered, the discovery process occurs. If the system discovery 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. This screen also enables you to set options for non-bundle product versions. If you specify a bundle on the command line when starting HP Smart Update Manager, this screen will not be presented.

    The Select Bundle Filter screen is divided into two sections.

    The upper part of the screen includes the product and status information:

    The following image illustrates the Select Bundle Filter screen

    The Set Options for Bundle Filter section allows you to set options for non-bundle products and versions.

    To proceed with the deployment process, click OK.

    NOTE: If a PSP or bundle that supports the target’s operating system is not present in the repository, HP Smart Update Manager may display a message box indicating that a supported bundle is not present in the repository.

     

    Selecting components to install

    When the discovery process is complete, and the desired 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 deselect components to install.

    The following image illustrates the HP Smart Update Manager Select Items to be Installed screen when installing Linux RPMs.

    The Select Items to be Installed screen includes the following sections:

    When updating installation for some but not all NIC components, select the devices to be updated in the window that appears. If the NIC firmware listed for the device does not have a version, you cannot add that firmware to the device using HP Smart Update Manager.

    When multiple hardware devices such as hard drives or array controllers exist in a single server, HP Smart Update Manager lists each device only once. If the devices have different firmware versions, then the versions are listed from earliest to latest in a range. When multiple instances of the firmware are available for installation, the instances are listed from earliest to latest. If necessary, all hardware device firmware is flashed to the selected version.

    The Select Items to be Installed screen also includes the following buttons:

    The select bundle filter screen can be opened from the Select Items to be Installed screen by clicking on the Select Bundle Filter link under 'Optional Actions' section.

    The component selection pane in the Select Items to be Installed screen is divided into sections, which might vary depending on your system. These sections include the following headings:

    Multi-session installation appears on the Source Selections screen under certain combinations of dependencies between the components selected for installation.

    If all of the previous conditions are true, then HP Smart Update Manager detects it and a notification to reboot appears in order to continue the installation. All installable components appear in the original update list, but only the components shown before the notification is installed. You must reboot to complete the installation and then restart HP Smart Update Manager to continue the installation process.

    Status field

    The Status field of the Select Items to be Installed screen displays information about whether the installation is ready to proceed or not.

    Icon Text Description
    Ready All selected components are ready to be installed.
    Already up-to-date 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.

    Reboot section

    The reboot section of the Select Items to be Installed screen enables you to specify preferred reboot behavior.

    To instruct the system to reboot after updates are installed:

    1. Click Reboot System After Installation.
    2. Click Always or If Needed.

    If Always is selected, then the system will always be rebooted unless there is a component installation failure. If If Needed is selected, then the system will be rebooted if needed by at least one component unless there is a component installation failure.

    To change the delay before reboot or the reboot message, click Reboot Options. The Set Reboot Options screen appears.

    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.

    Component selection pane

    The component selection pane of the Select Items to be Installed screen displays (by component number order, unless a dependency causes the installation order to change) all components available for installation based on your server and hardware options. The HP Smart Update Manager automatically checks each component for dependencies, if the component is already installed on the system, or if it requires a reboot after installation. Items available for installation are selected by default. You can deselect any components you do not want to install.

    The component selection pane is divided into the following columns:

    NOTE: For Linux source RPMs, if the Source packages are not installed, then the source RPMs are not available for selection. To deploy any Linux source RPMs, ensure that the appropriate Source packages are installed before starting HP Smart Update Manager.

    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.

    If a failed dependency occurs, then you must resolve it before proceeding with the installation. Depending on the issue, you must locate software or firmware components in the HP Smart Update Firmware DVD, bundles, HP ProLaint Support Packs, or HP website (http://www.hp.com). The following figure displays the Failed Dependencies screen.

    If a component displays a build failed, you must resolve the issue before proceeding with the installation.

    Installation options

    Installation Options allows you to specify firmware upgrade behaviour for installable components by selecting one or more options from the Additonal Options field. Depending on the component type, one of the following screens appears:

    The following table illustrates how changing the options for firmware upgrade behavior can change the firmware upgrade results. In this example, the array controller is assumed to be an HP Smart Array 6402 controller.

    If the existing array controller has firmware version 3.00 installed, then updating the firmware produces results as described in the following table:

      Default Allow downgrades Allow rewrites
    Firmware upgrade v3.05 3.05 3.05 3.05
    Firmware upgrade v3.10 3.10 3.10 3.10

    If the existing array controller has firmware version 3.10 installed, then updating the firmware produces results as described in the following table:

      Default Allow downgrades Allow rewrites
    Firmware upgrade v3.05 No change 3.05 3.10
    Firmware upgrade v3.10 No change No change 3.10

    NOTE:  When updating installation for NIC components, select the devices to be updated in the window that appears.

    After you have selected all the components that you want to install, click Install to proceed with the installation. omponents, The Installation Progress screen appears.
     

    Viewing the installation results

    When the installation is complete, the Installation Results screen appears.

    The Installation Results screen is divided into the following columns:

    The following icons might appear in the Status column

    Icon Text Description
    Success The component was installed successfully.
    Same/older version successfully installed The existing component was successfully downgraded or reflashed to the same or an older version.
    Update returned an error An update error has occurred. For details, see the HP SUM log file.
    Installation failed The component was not installed. To see additional details, Click View Installation Log

    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 installed. However, the Reboot Needed message is not displayed on the Installation Results screen for Linux RPMs since that information is not available to HP Smart Update Manager. HP recommends that you reboot the target server after installation of any Linux RPMs. To view the list of RPMs which require a reboot, see the download page of the HP ProLiant Support Pack for Linux on the PSP website (http://www.hp.com/servers/psp).

    To view the Installation result details, click View Installation Log.

    The Installation Results screen also includes the following buttons:

    NOTE:  After updating hard drives in external enclosures such as MSA20, you must power cycle the external enclosures. The Reboot button in HP Smart Update Manager only reboots the server but never power cycles an external enclosure.

    The following installation logs contain information about the installation activity for each host being updated:

    The log files can be found in the following locations:

    There is a new file that contains detailed information on the execution of HP Smart Update Manager.

    NOTE:  Using the offline environments provided by the Smart Update Firmware DVD and HP BladeSystem Firmware Deployment Tool results in the log files being written to the Linux location.

    HP SUM also creates trace logs of its installation that can be used to debug problems. These trace files are located in the following places:

    HP SUM creates a separate trace log for each target server. These are captured in subdirectories under the trace log directories. The directories start with Target_0, Target_1, and so forth. These contain the target specific trace information. No passwords or sensitive data is stored in this trace logs.
     

    Multiple-host installations

    The HP Smart Update Manager provides an easy-to-use graphical interface that enables you to deploy and maintain firmware and software components. To access HP Smart Update Manager, see "Deployment options". After you start HP SUM,the Source Selection screen ("Selecting the location to check for updates") appears which allows you to specify where the components that you want to deploy can be found. After selecting where the components can be found, the Inventory Progress screen appears while the HP Smart Update Manager builds an inventory of available updates. When the inventory process is complete, the Select Installation Host(s) screen appears.

    Selecting remote hosts or groups

    The Select Installation Host(s) screen enables you to choose multiple hosts and groups for component installation. 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.

    NOTE: Local hosts cannot be included in a list with remote hosts or in a group. When selecting an iLO or iLO2 as a host, only the iLO firmware can be updated. The server host must also be selected to update all other firmware and software components on the same physical server. The iLO firmware can be updated by either selecting the iLO or the server host.

    To add hosts, see "Managing Hosts." To add groups, see "Managing Groups."

    To continue with the deployment process:

    1. Select one or more hosts or groups.
    2. Click Next to continue.
    3. Enter the credentials for the host ("Entering credentials for hosts").
    4. Click OK to proceed as described in Selecting components to install on multiple hosts or "Selecting components to install on multiple hosts."
    5. When the installation is complete, the Installations results for multiple hosts screen ("Viewing the installation results for multiple hosts") appears.

    Managing hosts

    To add, edit, or delete hosts, click the Manage Hosts button. The Manage Hosts screen appears. A remote host can be the IP address or DNS name of the following:

    NOTE: Local hosts cannot be included in a list with remote hosts or in a group. When selecting an iLO, iLO2, OA or VC as a host, only the firmware component for that hardware can be updated. The server host must be selected to update all other firmware and software components. The iLO firmware can be updated by either selecting the iLO or the server host.

    To add a host:

    1. Click Add Host. The New Host dialog box appears.
    2. Select the method to add a host from the following:
      1. Enter the DNS name of the host you want to add.
      2. Enter the IP address of the host you want to add.
      3. 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.

      NOTE: When adding hosts using either IP address option, you can select from the IP format options: IPv4 or IPv6. The IPv4 format is the default option since it is the current Internet protocol. The IPv6 format is the next generation Internet protocol.

    3. Enter an optional user-defined description given to the host to be added.
    4. Click OK.

    The new host is added to the list on the Select Installation Host(s) screen.

    To edit an existing host:

    1. On the Manage Hosts screen click the Edit Host button on the Manage Hosts screen. The Edit Host dialog box appears.
    2. Edit the Host Name and optional user-defined Description.
    3. Click OK.

    To delete a host:

    1. On the Manage Hosts screen, click the 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.

    To add a group:

    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.

    The new group is added to the list on the Select Installation Host(s) screen.

    To edit an existing group:

    1. Select the desired group and click the Edit Group button on the Manage Groups screen. The Edit Group dialog box appears.
    2. Edit the group name as needed.
    3. Edit the optional user-defined description given to the group as needed.
    4. Click the Enter >> button to add hosts and << Remove button to remove hosts as needed.
    5. Click OK.

    To delete a group:

    1. Select the group on the Manage Groups screen, then click the Delete Group button.
    2. Click Yes when the confirmation screen appears.

    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:

    If an active update process is detected on the remote host, you can select Skip host or Restart update.

    Click OK to continue.

    When a group or multiple hosts are selected, 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:

    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 the credentials are the same, click Select All to select all the hosts on the list.
    2. Click the Enter >> button to enter the required credentials and to move the selected host to the Completed Hosts pane.
    3. To continue, Click Next.
    4. NOTE:  If a TPM is detected and enabled, an HP Smart Update Manager pop-up warning message appears after the Discovery Progress screen. You must read the message and determine how to proceed. For more information, see Trusted Platform Module (TPM).


     

    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 Smart Update Manager, this screen will not be presented.

    For more information about the screen, see "Selecting bundles to filter". To proceed with the installation process, click OK. br> 

    Selecting components to install on multiple hosts

    The Select Items to be Installed screen displays the server hosts and their status information.

    The Select Items to be Installed screen includes the following buttons:

    The server host pane of the Select Items to be Installed screen displays summary information for the server hosts available for installation, and features a drilldown of individual hosts.

    The server host pane is divided into the following columns:

    Icon Text Description
    Ready The host is ready for installation.
    Nothing to Install The host is already up-to-date.
    Host Skipped Due to Existing HP Smart Update Manager 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.

    To zoom in to single host selections, click View Host on the Select Items to be Installed screen. The Selections for Single Host screen appears.

    To set single-host selections, proceed as described in "Selecting Components to Install."

    After setting the single-host selections for all hosts to be updated, click Install on the Select Items to be Installed screen to proceed with the installation. br> 

    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:

    Icon Text Description
    Success The host was updated successfully.
    Nothing to install The host is already up-to-date.
    Installation canceled by user The installation was canceled and cannot continue.
    Installation failed One or more of the components have failed.

    The Installation Results screen also includes the following buttons:

    To view single-host installation results, double-click on the host (or select the host), and then click View Host.

    Proceed as described in Viewing the installation results.
     

    Scripted Deployment

    In this section;

    Command line interface
    Return codes
    Input files
            Command line usage of Input file
            Input file format and rules
            File Encoding
            Error Reporting
            Input file parameters
    Deploying firmware and software simultaneously Reports

     

    Command line interface

    The HP Smart Update Manager command-line interface enables you to script custom installations.

    Command line syntax

    The general command line syntax for the HP Smart Update Manager is:

    hpsum [/h[elp]] [/?] [/f[orce]] [/f[orce]:bundle] [/f[orce]:rom] [/f[orce]:software] [/f[orce]:all ] [/g (/downgrade)] [/e (/rewrite)] [/m[utual])] [/s[ilent]] [/allow_update_to_bundle] [/allow_non_bundle_components] [/b[undle] <bundle_to_install>] [/express_install] [/use_snmp] [/use_location "file_share"] [/use_web] [/use_d[ownloaded]] [/tpmbypass] [/ignore_tpm] [/use_wmi] [/use_latest] [/romonly] [/softwareonly] [/continue_on_error <error>] [/override_existing_connection] [/On_failed_dependency:<Parameter>] [/r[eboot]] [/reboot_message "reboot message"] [/reboot_delay timeout_in_seconds] [/reboot_always] [/dryrun] user <username> or /username <username>] [/passwd <password>] [/current_credential] [/target "netAddress"] [/group "group_name"] [/ [/logdir "path"] [/v[erbose]] [/veryv[erbose]] [/report] [/inventory_report] [/firmware_report] [/inputfile "filename"] [/deleteinputfile "filename"] [/c[omponent] <component_to_install>] [<component1_to_install> <component2_to_install> ...] [<bundle1_to_install> <bundle2_to_install> ...]

    NOTE: All arguments and information enclosed in brackets are optional. The arguments may be prefixed with either a '-' or '/' character. These examples show only the '/'. On Windows® operating systems use a slash (/) before each argument and on Linux operating systems use a hyphen (-) before each argument.

    NOTE: Command line syntax does not support double-byte character sets. Any messages entered through the command line using a double-byte character set will not be displayed correctly.

    The HP Smart Update Manager with Onboard Administrator requires a user ID and password to log in. The user ID must be an Administrator equivalent ID and not an operator or user equivalent level ID.

    If no command-line arguments are executed on the command line, the HP Smart Update Manager GUI appears. br> 

    Command line arguments

    HP Smart Update Manager 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, 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.
    INSTALL OPTIONS
    /f[orce] This argument enables you to override or downgrade an existing component installation. This argument produces the same results as /f:software.
    /f[orce]:bundle This argument enables you to override or downgrade the existing installation of components in the selected bundle.
    /f[orce]:rom This argument enables you to override or downgrade the existing installation of the selected firmware components. (Applies to firmware only.)
    /f[orce]:software This argument enables you to override or downgrade the existing installation of the selected software components.
    /f[orce]:all This argument enables you to override or downgrade the existing installation of the selected software components, firmware components, and bundles.
    /g or /downgrade This argument 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.)
    /e or /rewrite This argument 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.)
    /m[utual] If the device you want to flash is in a shared storage environment, then this argument informs the firmware flash engine to flash the firmware. If the device to be flashed is in a shared storage environment, and the /m option is not passed, then the component installation fails. (Applies to firmware only.)
    /c[omponent]
    <component to install> or <component1_to_install> <component2_to_install>
    This argument specifies the components to install. Components to install can be specified with or without the /c[omponent] argument. If using the /c[omponent] argument, then only one component can be specified with the argument. However, multiple /c arguments and components can be specified on the same line. If the /c[omponent] argument is not used, multiple components can be specified at the same time, but the components must be separated by a blank and listed after all the arguments on the command line. 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. Failed dependencies are not reported to the user when using the /s[ilent]argument. To check for failed dependencies, remove the /s[ilent] argument, reissue the command line, and then the HP Smart Update Manager is presented. Continue_on_error <error> argument is not supported with the /s[ilent] argument for this release of HP Smart Update Manager.
    /allow_update_to_bundle This argument is a filter switch and enables the user to install newer versions of 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_components This argument is a filter switch and enables the user to install components that are not included in the bundle but reside in the directory with the components in the bundle.
    /b[undle]
    <bundlename> or <bundle1_to_install> <bundle2_to_install>
    This argument specifies the bundles to install. Bundles to install can be specified with or without the /b[undle] argument. If using the /b[undle] argument, 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, 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). The HP Smart Update Manager performs discovery, install, or exit without user interaction. The user can cancel or terminate HP Smart Update Manager.
    /use_snmp 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_location "file_share" This argument specifies a directory or file share that contains the PSP and components for use with HP Smart Update Manager. The "file_share" format must be a mapped file share and not in Universal Naming Convention (UNC) format. If you do not specify this argument, the directory containing hpsum.exe or HP Smart Update Manager 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.
    /use_web This argument specifies that the check box for Check ftp.hp.com on the Source Selection screen is to be selected. This allows components to be retrieved from hp.com and to be used in the list of possible updates.
    /use_d[ownloaded] This argument specifies that the check box for Include components previously downloaded from HP.com on the Source Selection screen is to be selected. This allows those previously downloaded components to be included in the list of possible updates.
    /tpmbypass or /ignore_tpm These arguments specifies that if a Trusted Platform Module (TPM) is enabled, the warning message should be ignored and component installation will be allowed to continue.
    /use_wmi This argument specifies that components, which use WMI protocol, are available to be selected for installation. These components are optional by default and will not be installed unless this argument is used. When the /use_wmi argument is used, and the /use_snmp argument is not, the SNMP components are optional.
    /use_latest This argument is a filter switch for use with bundles. The argument enables you to use the latest version of the bundle when multiple versions of bundles are listed on the command line. If there are no bundles specified on the command line, and multiple bundles are in the directory, the /use_latest argument allows HP Smart Update Manager to use the bundle with the latest version for installation.
    /romonly This argument is a filter switch and allows the user to see only the firmware components needed for installation. When using this filter switch, you must exit, and then restart HP Smart Update Manager to return to an unfiltered state. Do not use the /romonly argument with the /softwareonly argument.
    /softwareonly This argument is a filter switch and allows the user to see only the software components needed for installation. When using this filter switch, you must exit, and then restart HP Smart Update Manager to return to an unfiltered state. Do not use the /softwareonly argument with the /romonly argument.
    OVERRIDING ERRORS
    /continue_on_error <error> This argument causes the installation to continue and ignore errors. Valid values are <error>=ServerNotFound and <error>=BadPassword. The ServerNotFound option can be used to bypass inactive or unavailable remote hosts when deploying firmware or software to multiple remote hosts at the same time.
    /override_existing_connection This argument defines the behavior when a remote target has an existing HP Smart Update Manager session in progress. This argument overrides the session in progress and reinitializes the installation framework on the remote host.
    /On_failed_dependency:<parameter> This argument tells HP Smart Update Manager how to proceed when a component has a failed dependency. The supported parameters for this argument are Omit_Host (default), Omit_Component and Force. Omit_Host causes the host to be put into a failure state and no installation is attempted. Omit_Component 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.
    REBOOT OPTIONS
    /r[eboot] If the following conditions are met, then this argument causes the server (or host server in a remote installation) to reboot:
    • The /reboot option is selected or given as a command line argument.
    • All components selected for installation are successfully installed.
    • At least one of the installed components requires a reboot to complete its installation.
    /reboot_message "reboot message" This argument displays the specified reboot message on remote consoles connected to the server you want to reboot. You must use this argument with the /reboot option, or the argument is ignored.
    /reboot_delay timeout_in_seconds This argument delays the reboot of the server for the length of time specified by the timeout_in_seconds variable. You must use this argument with the /reboot option, or the argument is ignored. Acceptable values are between 15 and 3600. The default timeout value is 15 seconds for Microsoft® Windows® and 60 seconds for Linux. In Linux, the Reboot Delay time is converted from seconds to minutes. For Linux, any value under a full minute, 59 seconds or less, rounds to the next minute.
    /reboot_always If the following conditions are met, then this argument forces the server to reboot:
    • The /reboot_always option is selected or given as a command line argument.
    • All components selected for installation are successfully installed.
    SIMULATING HP SUM
    /dryrun This argument simulates the installation for a test run. Nothing is installed.
    HOST TARGETS
    /user <username> or /username <username> This argument enables you to log in to HP BladeSystem c-Class Onboard Administrator with your user ID.
    /passwd <password> This argument enables you to use the password for the user ID specified in the /user parameter. The password is used to log in to remote hosts and HP BladeSystem c-Class Onboard Administrators.
    /current_credential This argument enables the credentials of the local host to be used as the credentials to access the targets instead of providing the username and password explicitly for each target. The assumption is that the current credentials are valid for the targets being accessed. (Applies to Windows® operating systems only.)
    /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.
    /group "group_name" This argument specifies an already defined group name in the HP Smart Update Manager GUI.
    LOG FILES
    /logdir "path" This argument enables you to redirect the output from HP Smart Update Manager or the HP BladeSystem c-Class Onboard Administrator flash utility to a different directory than the default location. For Windows® components, the default location is %SYSTEMDRIVE%\CPQSYSTEM\hp\log\<netAddress> and the redirected location is <path>\hp\log\<netAddress>. For Linux components, the default location is /var/hp/log/<netAddress> and the redirected location is <path>/hp/log/<netAddress>.
    /v[erbose] or /veryv[erbose] These arguments enable you to set the verbosity level for the HP Smart Update Manager execution log file, hpsum_execution_log_<date>_<time>.log. Using one of these arguments increases the level of detail that is retained in the log file. The default value is normal verbosity.
    GENERATING REPORTS
    /report This argument generates a report listing the target summary and how the components in the repository affect the target. For example, whether each component applies to the target or not. The report is generated in HTML and XML with file name formats of HPSUM_Report_<date>_<time>.html and HPSUM_Report_<date>_<time>.xml. By default, the files are located in the present working directory where HP Smart Update Manager is initiated from. If that location is write-protected, the files can be found in the same directory as the HP Smart Update Manager log files. Including other arguments on the command line can modify the contents of the report. Using the /target argument will allow reports to be generated for different targets.
    /inventory_report This argument generates a report listing the components in the specified repository. The report is generated in HTML and XML with file name formats of HPSUM_Inventory_Report_<date>_<time>.html and HPSUM_Inventory_Report_<date>_<time>.xml. By default, the files are located in the present working directory where HP Smart Update Manager is initiated from. If that location is write-protected, the files can be found in the same directory as the HP Smart Update Manager log files.
    /firmware_report This argument generates a report listing the firmware installed on and details of the target. The report is generated in HTML and XML with file names of HPSUM_Firmware_Report.html and fwreport.xml in the directory named HPSUM_Firmware_Report_<date>_<time>. By default, this directory is located in the present working directory where HP Smart Update Manager is initiated from. If that location is write-protected, the directory can be found in the same directory as the HP Smart Update Manager log files.Including other arguments on the command line can modify the contents of the report. Using the /target argument will allow reports to be generated for different targets.
    USING INPUT FILES
    /inputfile "filename" This argument enables you to script the deployment of firmware and software to multiple remote systems at one time. For details of the file format and commands, see the "Input files" section.
    /Deleteinputfile "filename" This argument enables you to instruct HP Smart Update manager to delete the input file after it 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 <component_to_configure>. This command presents the same configuration screens seen in the HP Smart Update Manager GUI. You must run this command from a DVD or other read/write media or the component cannot be configured. Configuration for a given component only needs to be executed once. The configuration is stored within the component and is propagated to all target servers when deployed through HP Smart Update Manager GUI or command line. To change the configuration, rerun hpsum_config against the component and a new configuration writes out. If a component does not need configuration, hpsum_config will return to the console.

    To configure components to be deployed on all editions of the Windows Server® 2008 with the Server Core option, you must access the system as a remote host using HP Smart Update Manager running on a system with a supported Windows® operating system, and then configure the components before deployment. br> 

    Command line examples

    The following command line parameter examples can be executed within these environments:

    Example 1:

    This command line input deploys the latest PSP and firmware components:

    hpsum /use_latest /allow_non_bundle_components /silent

    Results: All the software components from the 7.90 PSP and firmware components, which HP Smart Update Manager determined needed to be installed, were installed.

    Example 2:

    Either of the following command line inputs can deploy the previous version of the PSP only and force all the components to be installed:

    Results: All the software components from the 7.80 PSP, which HP Smart Update Manager determined needed to be installed, were installed. No firmware was installed.

    Example 3:

    This command line input deploys firmware:

    hpsum /romonly

    Results: All the firmware components, which HP Smart Update Manager determined needed to be installed, were installed. No software was installed.

    Example 4:

    Either of the following command line inputs can deploy two software components:

    Results: The two components were installed. No firmware or other software was installed.

    Example 5:

    Either of the following command line inputs can deploy the latest PSP, later versions of components in the bundle, and firmware to three remote hosts and force all components to be installed:

    Results: All the firmware components, software components from the 7.90 PSP, cp008097.exe, and cp008257.exe were installed on Management Server1, Management Server2, and Management Server3. br> 

    Return codes

    HP Smart Update Manager has consolidated return codes from Linux and Windows® smart components into a new, enhanced return code mapping. These return codes determine the status of the component installation. You can also use return codes in a script to control the execution of the script and determine any required branching.

    In Linux, the negative return codes are reported. These return codes are determined by subtracting the negative value from 256.

    To view the installation log file locations, see "Viewing the installation results"

    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. See the error log for details.
    FAILURE_BAD_PARM -2 254 254 A bad input parameter was encountered.
    FAILURE_COMPONENT_FAILED -3 253 253 The installation of the component failed.

    Windows Smart Component return codes

    Error Level Meaning
    0 The Smart Component failed to install. For more details. see the log file.
    1 The Smart Component installed successfully.
    2 The Smart Component installed successfully, but the system must be restarted.
    3 The installation was not attempted because the required hardware was not present, the software was current, or there was nothing to install.

    Linux smart component return codes

    Single target servers:

    Error Level Meaning
    0 The Smart Component installed successfully.
    1 The Smart Component installed successfully, but the system must be restarted.
    2 The installation was not attempted because the required hardware was not present, the software was current, or there was nothing to install.
    3 The Smart Component failed to install. For more details, see the log file.

    Multi-target servers:

    Error Level Meaning
    0 The installation of the deliverable was successful. No reboot was required.
    1 The installation of the deliverable was successful. A reboot is required for the deliverable to be enabled.
    2 The installation was not attempted because the version to be installed matches the version already installed.
    3 The installation was not attempted because of one of the following:
    • The version to be installed is older than the version already installed.
    • Supported hardware was not present, not enabled, or in a state that an installation could not be attempted.
    • Installation was not attempted because the component did not support the environment.
    • There is nothing for the component to accomplish.
    4 If the component is installing to a remote target (such as Onboard Administrator or other network-based deployment), this return code indicates that the target cannot be found.
    5 The installation was canceled by a user before anything could be installed.
    6 The installer cannot execute because of an unmet dependency or installation tool failure.
    7 This return code indicates the actual installation operation (not the installation tool) failed.

    Linux RPM return codes

    Error Level Meaning
    0 The Linux RPM installation was successful.
    1 The Linux RPM installation failed.

     

    Using HP Smart Update Manager input files

    HP Smart Update Manager provides the ability to script the update of multiple, individual targets or groups of targets within a single operation through the input file functionality. To protect your credentials, use a secure server or a management console.

    To create an input file, use Microsoft® Notepad. All section headers and trailers [END] must match. Failure to use the SILENT=YES option causes the GUI mode to be used, but the information provided enables you to skip screens where information has already been provided. The DRYRUN=YES option can be used to do dry runs of installations to ensure the scripts are working without deploying the firmware updates that might be needed on each target. Remove the "DRYRUN=YES" option to perform the updates.

    For parameters that can take list values, list separator can be commas, semicolons or spaces.

    NOTE:  The credentials can be left out of the file for greater security and passed on the command line to HP Smart Update Manager. The only limitation of this is that the userID and credentials must be the same on all..

    When the file has been created, to use it with HP Smart Update Manager, add it as the inputfile parameter to a normal HP Smart Update Manager command line. For example, if the name of the input file is hpsum.in, the command line syntax is hpsum -inputfile hpsum.in. Full paths can be added to the input file location if it is not stored in the same location as the HP Smart Update Manager executables. The field can be enclosed in double quotes to enable paths with spaces. Also, the input file itself might 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.

    Command line usage of input file

    The form for the HP Smart Update Manager 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 may contain the same flags on the command line. The usual command line flags may still be used with the -inputfile flag, and takes precedence over any given input file. The field may be enclosed in double quotes to allow for paths with spaces.

    Input file format and rules

    The input file is divided into two sections


    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__

    Input file parameters

    Parameter Description Possible Values
    SILENT This argument causes the installation to run silently with no 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 = "Failedependencies" parameter is supplied), and an error message is written to the log file. Silent installation of EVA components is not supported. YES, NO
    FORCEALL This argument forces both firmware and software components YES, NO
    FORCEROM This argument forces updates to firmware components YES, NO
    FORCESOFTWARE This argument forces updates to software components YES, NO
    FORCEBUNDLE This argument enables you to override or downgrade an existing installation of components in the selected bundle. YES, NO
    DOWNGRADE (Applies to firmware only.) This argument enables you to downgrade to an earlier version of firmware for multi-target devices such as hard drives and array controllers. YES, NO
    REWRITE (Applies to firmware only.) This argument enables you to rewrite the same version of firmware only for multi-target devices such as hard drives and array controllers. YES, NO
    REBOOTALLOWED This argument enables you to reboot if required. YES, NO
    REBOOTMESSAGE This argument enables you to create a message to be displayed prior to rebooting. Any String (not exceeding 256 characters)
    REBOOTDELAY This argument enables you to delay before rebooting. Time in seconds
    COMPONENTSLIST This argument enables you to limit the list of components to be updated. Component names with file extensions (.exe, .rpm and .scexe)
    BUNDLESLIST This argument enables you to limit the list of bundle xml files to be filtered. Bundle file names
    ALLOWUPDATEBUNDLE This argument is a filter switch and enables the user to install newer versions of 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.
    YES, NO
    SKIPTARGET This argument defines the behavior when a remote target has an existing HP SUM session in progress. This argument enables you to skip the host if there is already an existing HP SUM session. A NO overrides the session in progress and reinitializes the installation framework on the remote host. YES, NO
    IGNOREERRORS This argument causes the installation to continue and ignore errors. The ServerNotFound option can be used to bypass inactive or unavailable remote hosts when deploying firmware or software to multiple remote hosts at the same time.
    FailedDependencies can be used to ignore any failed dependencies and proceed with the ones that are ready to be installed.
    ServerNotFound, BadPassword, FailedDependencies
    SOURCEPATH This argument can be used to provide a single local repository path. This creates an inventory from the given path instead of the local or default repository. Directory path
    USELATEST This argument is a filter switch for use with bundles. The argument enables you to use the latest version of the bundle when multiple versions of bundles are listed on the command line.
    If there are no bundles specified on the command line, and multiple bundles are in the directory, this parameter allows HP SUM to use the bundle with the latest version for installation.
    YES, NO
    DRYRUN This argument simulates the installation for a test run. Nothing is installed. YES, NO
    OPTIONS This parameter can be used to specify the HP SUM CLI options inside the input file, which overrides the configuration settings. Parameters can be separated by a semi-colon, comma or a space. One or more CLI switches
    For example: OPTIONS = /f:rom, /silent
    USESNMP 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 USESNMP argument is used, and the USEWMI argument is not used, the WMI components are optional.
    YES, NO
    USEWMI This argument specifies that components, which use WMI protocol, are available to be selected for installation. These components are optional by default and will not be installed unless this argument is used. When the USEWMI argument is used, and the USESNMP argument is not used, the SNMP components are optional. YES, NO
    ROMONLY This argument is a filter switch and allows the user to view only the firmware components needed for installation.
    Do not use the /romonly argument with the /softwareonly argument.
    YES, NO
    SOFTWAREONLY This argument is a filter switch and allows the user to view only the software components needed for installation.
    Do not use the /softwareonly argument with the /romonly argument.
    YES, NO
    USECURRENTCREDENTIAL (Applies to Windows® operating systems only.) This argument enables the credentials of the local host to be used as the credentials to access the targets instead of providing the username and password explicitly for each target.
    The assumption is that the current credentials are valid for the targets being accessed.
    YES, NO
    WEBUPDATENEEDED This argument enables you to instruct HP SUM to include the components from ftp.hp.com in the list of possible updates. YES, NO
    USEPROXYSERVER This argument enables the inclusion of a proxy server(and port number) to access ftp.hp.com String value For example, 11.22.33.44:80
    USEPROXYSCRIPT This argument enables the inclusion of a proxy script to access ftp.hp.com Web URL (For example, autoproxy.com)
    DELETEINPUTFILE This argument enables you to instruct HP SUM to delete the input file after it has been read in YES, NO (default)
    ONFAILEDDEPENDENCY This argument instructs 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 components and proceeds with any updates that do not have dependency failures. Force attempts all updates, even if they have dependency failures.
    OmitHost (default), OmitComponent, Force
    HOST 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.
    This argument specifies an already defined group name in the HP SUM GUI.
    IP address, DNS name
    UID This argument enables you to log in to the target host with your user ID. UID = <username>
    PWD This argument enables you to use the password for the user ID specified in the UID.
    The password is used to log in to target host.
    UID = <password>

    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
    OPTIONS = /f:rom

    [TARGETS]
    HOST = schinta1
    HOST = schinta2
    UID = root
    PWD = root123
    HOST = 234.567.765.432
    [END]

    NOTE:  HOST Can be assigned the IP address of the server or its DNS name.

    USAGE: hpsum /inputfile <Examples of inputfile.txt file

    Example 1:
    The two targets are passed to be updated. The target can be any server supported by HP Smart Update Manager.
    DRYRUN = YES
    SILENT = YES
    [TARGETS]
    HOST = BL465C-01
    HOST = 192.168.1.2
    [END]

    Example 2:
    A host is passed along with the user ID and password to use for the hosts in the group.
    DRYRUN = YES
    SILENT = YES
    [TARGETS]
    HOST = BL685cG6
    UID = Bigboss2
    PWD = password
    [END]

    Example 3
    SILENT = YES
    IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies
    SKIPTARGET = NO
    SOURCEPATH = C:\fwcd\firmware\hp\swpackages
    [GROUPS]
    HOST=winserver
    UID=Userid
    PWD=password
    [END]

    Example 4
    SILENT = YES
    IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies
    SKIPTARGET = NO
    SOURCEPATH = C:\ fwcd\firmware\hp\swpackages
    FORCEALL = YES
    REBOOTALLOWED = YES
    REBOOTDELAY = 30
    REBOOTMESSAGE = "Install complete, server will reboot in 30 seconds"
    [TARGETS]
    HOST=16.83.62.111
    UID=Userid
    PWD=password
    [END]
    [TARGETS]
    HOST=16.83.61.53
    UID=Userid
    PWD=password
    [END]
    [TARGETS]
    HOST=16.83.62.18
    UID=Userid
    PWD=password
    [END]
    [TARGETS]
    HOST=16.83.61.9
    UID=Userid
    PWD=password
    [END]
     

    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 (that is, 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. For specific commands, see "Command line interface".

    Report Type Description Report File Information
    /report This argument generates a report listing, a target summary, and how the components in the repository affect the target (for example, whether each component applies to the target or not).

    Usage: hpsum /report

    The report files generated are:

    • hpsum_Report_<date>.html
    • hpsum_Report_<date>.xml
    /inventory_report This argument generates a report listing of the components in the specified repository.

    Usage: hpsum /inventory_report

    The report files generated are:

    • hpsum_Inventory_Report_<date>.html
    • hpsum_Inventory_Report_<date>.xml
    /firmware_report This argument generates a report listing of the firmware in the specified repository.

    Usage: hpsum /firmware_report

    The report files generated are hpsum_Report_<date>.html and fwreport.xml is placed in a folder named HPSUM_Firmware_Report_<date>

    An example of the HP SUM report in HTML format

    An example of the HP SUM Inventory report in HTML format

    An example of the HP SUM Firmware report in HTML format


     

    Advanced Topics



    In this section:
    Component configuration
    Server virtualization detection and support
    Configuring IPv6 networks with HP Smart Update Manager
     

    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 it will use default values for that configuration data. If the component has been previously installed and configured and no changes are made to the configuration data, then the existing configuration information will be preserved.

    Component configuration requires that Smart Components are in a write-accessible location. A CD/DVD or read-only network share is not supported.

    Configurable components are indicated in the Optional Actions column of the Select Items to be Installed screen screens. To configure a component, click Configure Now.

    Follow the instructions when the Item Configuration screen appears. When the configuration is complete, the Select Items to be Installed screen reappears.
     

    Deploying firmware and software simultaneously

    HP Smart Update Manager utility enables you to deploy firmware and software components simultaneously. The latest firmware and software components must be present 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. On the Select Bundle Filter screen, select the bundle, and then select the ALLOW NON-BUNDLE PRODUCTS option.

    To proceed with the deployment process, Click OK. The Select Items to be Installed screen appears with the appropriate firmware and software components.

    With the ability to get components from ftp.hp.com, you can deploy software and firmware components without using bundles.

    NOTE:  Linux RPMs and Virtual Connect FW components are not available to download from ftp.hp.com at this time.

    NOTE:  HP Smart Update Manager is compatible with various types of HP bundles.

    For more information on the PSPs, see the HP ProLiant Support Pack for Windows and Linux User Guide on the HP website (http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=345557.
     

    Server virtualization detection and support

    HP Smart Update Manager, running in the context of a Windows® PSP, supports server virtualization that runs on a Windows® host. However, HP Smart Update Manager, running in the context of a Windows® PSP, does not run on a VMware host or on a guest operating system environment regardless of what host hypervisor you use.

    HP Smart Update Manager, running in the context of the HP Smart Update Firmware DVD, does not support server virtualization that runs on a Windows® or Linux host and blocks attempts to install firmware from a guest or child virtual machine. The server virtualization does not run on a VMware host or on a guest operating system environment regardless of which host hypervisor you use. The HP Smart Update Firmware DVD does not boot to a guest operating system environment.
     

    Configuring IPv6 networks with HP Smart Update Manager

    Starting with HP Smart Update Manager version 3.2.0, you can deploy to remote targets in IPv6-based networks for Windows® and Linux target servers. Using HP Smart Update Manager with IPv6 networks presents challenges for IT administrators because of differing levels of functionality provided by various operating systems.

    For Windows®-based servers, HP Smart Update Manager uses well-known methods to communicate with remote target servers. HP Smart Update Manager uses either existing credentials or user-provided user name and password to connect to the admin$ share. This share is an automatic share provided by Windows Server®. After HP Smart Update Manager connects to the admin$ share, HP Smart Update Manager 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 allow HP Smart Update Manager to use SOAP calls over SSL to pass data among local and remote systems. These ports are defined in the "Enabling ports used in HP Smart Update Manager" section later in this document. After the installation is completed or canceled, HP Smart Update Manager stops the remote service, removes it from the target server, closes the port on the Windows® firewall, and releases the share to the target server admin$ share.

    For Linux-based servers, HP Smart Update Manager also uses well-known methods to communicate to remote target servers. HP Smart Update Manager starts by using the user-provided user name and password to create a SSH connection to the target server. After the HP Smart Update Manager connects, HP Smart Update Manager 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 will open ports in the iptables firewall to allow HP Smart Update Manager to use SOAP calls over SSH to pass data between the local and remote systems. These ports are defined in the "Enabling ports used in HP Smart Update Manager" section later in this document. Once the installation is completed or canceled, HP Smart Update Manager stops the remote service, removes it from the target server, closes the port in the iptables firewall, and closes the SSH connection to the target server.

    This information is important so users of HP Smart Update Manager can understand why certain limitations in operating system IPv6 support affect their ability to remotely deploy software and firmware updates to target servers.

    Configuring IPv6 for Windows Server 2003

    For information on setting up a Windows Server® 2003 system within an IPv6 network, see the online Microsoft Technet article Step-by-Step Guide for Setting Up IPv6 in a Test Lab (http://www.microsoft.com/downloads/details.aspx?FamilyID=fd7e1354-3a3b-43fd-955f-11edd39551d7&displaylang=en).

    Before using HP Smart Update Manager to deploy software and firmware updates to remote Windows Server® 2003 servers, you must add a registry entry to allow file sharing connections over IPv6 networks. To make the necessary registry entry:

    1. Start the Registry Editor (Regedt32.exe)
    2. Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
    3. On the Edit menu, click Add Value.
    4. Add the following registry value:
    5. Quit the Registry Editor

    For more information about these steps, see the Microsoft Knowledge Base Item 281308 on the Microsoft website (http://www.microsoft.com).

    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. 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 HP Smart Update Manager in IPv6 Networks.

    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\<ip_address> directory.

    Configuring IPv6 for Windows Server 2008

    HP Smart Update Manager provides the most robust support for remote deployment when using Windows Vista® as a client to Windows Server® 2008-based servers. Using HP Smart Update Manager in this environment enables you to use all the capabilities of IPv6 including link-local, site-local, and global IP addresses for both local and remote target servers. Microsoft Vista®, when used as a client to run HP Smart Update Manager to remote Microsoft Server® 2008 operating systems or as a target operating system on HP Workstation Blade servers, 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.

    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. 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 HP Smart Update Manager in IPv6 Networks.

    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\<ip_address> directory.

    Limitations of IPv6 for Windows® Server 2003 and Windows® Server 2008

    Windows Server® 2003 requires site-local addresses to provide the necessary file-sharing capabilities needed by HP Smart Update Manager. This means that link-local and global IPv6 addresses are not supported as remote targets with HP Smart Update Manager.

    Windows Server® 2008 or Microsoft Vista environments do not have any known limitations to using HP Smart Update Manager.

    NOTE:  Windows® XP clients are not supported in IPv6 networks for HP Smart Update Manager deployment.

    Configuring IPv6 for Linux

    HP Smart Update Manager leverages the IPv6 capabilities of Linux as provided by the Red Hat Enterprise Linux and Novell SUSE Linux Enterprise Server products. Using HP Smart Update Manager in this environment enables you to use all the capabilities of IPv6 including link-local, site-local, and global IP addresses for both local and remote target servers. Remote target servers must have the iptables-ipv6 RPM installed before targeting them from HP Smart Update Manager. Failure to install the iptables-ipv6 RPM prevents HP Smart Update Manager from opening the communications port needed to send data back to the initiating Linux workstation. Also, the Linux firewall can be disabled to allow HP Smart Update Manager to work, but it makes the Linux server vulnerable to attack. For information on how to setup IPv6 in a Linux environment, please see the Linux IPv6 How-To (http://www.linux.org/docs/ldp/howto/Linux+IPv6-HOWTO/index.html).

    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. 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 HP Smart Update Manager in IPv6 Networks. 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 /var/hp/log/<ip_address> directories.

    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. The file will be found 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. Failure to install iptables-ipv6 results in HP Smart Update Manager reporting a discovery failure unless the firewall is disabled.
     

    Troubleshooting



    In this section
    Recovering from a failed ROM upgrade
    Recovering from an installation failure
    Recovering from a discovery failure
    Recovering from a loss of Linux remote functionality
    Recovering from a blocked program on Microsoft Windows®
    Troubleshooting HP Smart Update Manager in IPv6 Networks
    Enabling ports in HP Smart Update Manager
    Recovering from operating system limitations when using a Japanese character set
    Recovering from Fatal Error - application will exit message
    Recovering from a missing reboot message when running on SUSE LINUX Enterprise Server 9
    Recovering a lost HP Smart Update Manager connection
    HP SUM Message 'Found new hardware' during discovery process
    Non-matching Systems error reported when building Source RPMs or installing RPMs built from Source
    Linux component version discrepancy for source RPMs
    HP SUM displays "No components found in the selected repository(ies)" message
    Additional/Optional Actions columns are grayed when HP Smart Update Manager is maximized
    Installation of components failed with 'Update returned an error'
    Issues related to bundle filtering on the Select Items to be Installed and Select Bundle Filter screens

     

    Recovering from a failed ROM upgrade

    Recovering from a failed system ROM upgrade

    Use redundant ROM or 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. This feature protects the existing ROM version, even if you experience a power failure while flashing the ROM.

    When the server boots, the system detects whether the current ROM is corrupt. If a corrupt ROM is detected, the system boots from the backup ROM and alerts you through POST that the ROM is corrupt.

    To access the redundant ROM through RBSU:

    1. Power up your desktop. A prompt appears in the upper right corner of the screen.
    2. Access RBSU by pressing F9.
    3. Select Advanced Options.
    4. Select ROM Selection.
    5. Select Switch to Backup ROM.
    6. Press the Enter key.
    7. To exit the current menu, press the Esc key, or to exit RBSU, press the F10 key. The server restarts.

    If RBSU is inaccessible, you can switch ROM images by changing the switch settings on the system configuration switch. For more information, see your server documentation.

    If both ROM images are corrupt, use ROMPaq recovery.

    ROMPaq recovery

    The Disaster Recovery feature supports systems that do not support the Redundant ROM feature. Disaster Recovery only applies to platforms with non-redundant system ROM. If both the up-to-date and backup versions of the ROM are corrupt, then perform ROMPaq Disaster Recovery procedures:

    1. On another server, download and save the ROMPaq image to the hard drive from the HP website (http://www.hp.com).
    2. Execute the ROMPaq image to create the ROMPaq disk.
    3. Switch to the server with the corrupted ROM.
    4. Power down the server
    5. Insert the ROMPaq disk
    6. Power up the server

    7. 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.
    8. Power down the server
    9. Remove the ROMPaq disk
    10. Power up the server
    11. To manually set the server for ROMPaq disaster recovery:

    12. Power down the server.
    13. Remove the access panel.
    14. Set the system maintenance switch positions for disaster recovery. Switch positions are server-specific; see the server documentation for information about the correct settings for your server.
    15. Insert a ROMPaq diskette with the latest system ROM from the HP website (http://www.hp.com/support).
    16. Install the access panel.
    17. Power up the server.
    18. Allow the system to boot completely.
    19. Repeat steps 1 and 2.
    20. Reset the system maintenance switch positions to their original settings.
    21. Repeat steps 5 and 6.

    Recovering from a failed option ROM upgrade

    To recover from an option ROM upgrade failure, use the recovery method that is appropriate to the specific option.

    Array controller ROMs

    Array controllers support Recovery ROM, which is a redundancy feature that ensures continuous system availability by providing a backup ROM. During the flash process, a new version of the firmware can be flashed to the ROM while the controller maintains the last known version of the firmware. If the firmware becomes corrupt, the controller reverts back to the redundant version of the firmware and continues operating.

    NOTE: Storage option ROMs cannot be downgraded with ROMPaq because ROMPaqs have been retired as a delivery method for storage options.

    Lights-Out management ROMs

    To perform disaster recovery for RILOE II, iLO, and iLO2, see the documentation for your particular Lights-Out management product on the Remote management website (http://www.hp.com/servers/lights-out).
     

    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.

    Examine the OpMan.trace, IPScout.trace, OSScout.trace, InstallClient.log, and InstallManager.log trace files to determine the cause of the failure. These files provide the following information.
    Trace FilesFunction
    OpMan.traceProvides operations trace of the overall installation process.
    IPScout.traceProvides the information on whether the remote target might be contacted and the type of target found (iLO, server, VC, OA).
    OSScout.traceProvides the details of the connection setup and is responsible for cleaning up after an installation and initiating a reboot, if needed and selected by the user, on the target system.
    InstallClient.logProvides the details of the execution of the individual components, including the command line parameters, used to launch the components and the component return code before it is converted to HP Smart Update Manager return codes.
    InstallManager.logProvides the interaction between the Operations Manager and the remote installation client. Any failure in network communications is reported in this file and surfaced as an Installation Failed message for the affected component and potentially all components that follow the failing component.
    discagent.traceProvides the details of the execution of the discovery agent on either the local system during a local installation or the remote target server. If a discovery tool fails, it is reported to this trace file and surfaced as a Discovery Failed message.
    discmanager.traceProvides the interaction between the Operations Manager and the remote discovery client. If a discovery tool fails, it is reported to this trace file and surfaced as a Discovery Failed message.

    It is possible to look in the OpMan.trace file and see which component was winnowed from the installation set and which ones were added. Normally, components are winnowed if:


    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. All the other components were removed for various reasons.

    InstallSet.cpp[212]: Winnow--Adding FileName 0.bin

    InstallSet.cpp[212]: Winnow--Adding FileName 1.bin

    InstallSet.cpp[222]: Winnow--Removing FileName 2.bin

    InstallSet.cpp[212]: Winnow--Adding FileName cp011301.exe

    InstallSet.cpp[222]: Winnow--Removing FileName cp011321.exe

    InstallSet.cpp[222]: Winnow--Removing FileName cp011489.exe

    InstallSet.cpp[222]: Winnow--Removing FileName cp011497.exe

    InstallSet.cpp[212]: Winnow--Adding FileName cp011500.exe

    InstallSet.cpp[222]: Winnow--Removing FileName cp011504.exe

    InstallSet.cpp[222]: Winnow--Removing FileName cp011505.exe

    InstallSet.cpp[222]: Winnow--Removing FileName cp011550.exe

    InstallSet.cpp[222]: Winnow--Removing FileName cp011560.exe

    InstallSet.cpp[242]: Target 0: Added Bundle bp000648.xml
     

    Recovering from a discovery failure


    Troubleshooting connection errors

    If you are receiving an HP Smart Update Manager Connection Error or Discovery Failed messages, follow these main troubleshooting tips.


    HP Smart Update Manager hangs during discovery

    If a system hang is observed during HP Smart Update Manager discovery and the system is connected to external storage, disconnecting the external storage should resolve the problem in most cases.
     

    Recovering from a loss of Linux remote functionality


    Configuring firewall settings

    When the Unable to Access Host message appears, the target firewall is enabled. By default, the target firewall is enabled in Linux.

    To recover remote Linux functionality, the target and host firewall must be disabled or reconfigured to allow IP traffic through the ports needed by HP Smart Update Manager to deploy firmware. For a list of the ports that need to be configured in the firewall, see "Enabling ports in HP Smart Update Manager" in 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.

    When the Windows® Security Alert appears, click Unblock and 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. Select Enabled and Allow the connections.

    For Direct to iLO support, you must enable ping.
     

    Troubleshooting HP Smart Update Manager in IPv6 networks

    If HP Smart Update Manager cannot connect to the remote server, you might receive a Discovery Failed error. Discovery failures can be caused by third-party storage, failure to access the remote target server, and an inability to access system resources. For IPv6 networks, host discovery failures can be caused by the incorrect configuration of the IPv6 network.

    Troubleshooting HP Smart Update Manager in IPv6 Windows® Server 2003 environment

    To validate that the IPv6 network is configured correctly for HP Smart Update Manager support, you must verify the following based on your operating system version.

    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.

    Troubleshooting HP Smart Update Manager in IPv6 Windows® Server 2008 environment

    To validate that the IPv6 network is configured correctly for HP Smart Update Manager support, you must verify the following based on your operating system version.

    Troubleshooting HP Smart Update Manager in IPv6 Red Hat and Novell SUSE-based Linux environments


     

    Enabling ports in HP Smart Update Manager

    The ports that HP Smart Update Manager uses cannot be configured. When HP Smart Update Manager port initiates communications to remote targets, it uses several well-known ports depending on the operating system. For Windows®, it uses ports 138 and 445 to connect to remote targets (equivalent to remote file and print share functionality). For Linux, HP Smart Update Manager uses port 22 (SSH) to start the communications with the remote target.

    HP Smart Update Manager uses defined ports as documented below to communicate between the remote target and the workstation where HP Smart Update Manager is executing. When you run HP Smart Update Manager, it uses the administrator/root privileges to dynamically register the port with the default Windows® and Linux firewalls for the length of the application execution, 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 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 no trace it was there other than the log files.

    To deploy software to remote targets on their secure networks using HP Smart Update Manager, the following ports are used:

    For Windows®:
    Ports Descriptions
    Ports 445 and 137/138/139
    (Port 137 is used only if you are using NetBIOS naming service.)
    These ports are needed to connect to the remote ADMIN$ share on target servers. These are the standard ports Windows® servers use to connect to remote file shares. If you can connect remotely to a remote Windows® file share on the target server, then you have the right ports open.
    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. There is no guarantee that the upper limit is 60007 as it is dependent on how many target devices are selected for installation.

    Ports 61000-61007 These ports are used from the target server back to the system running HP Smart Update Manager. The same mechanism is used by the remote access code as the 60000 ports, with the first trial port as 61000. There is no guarantee that the upper limit is 61007 when a conflict occurs. For the case of ipv4-only and one NIC, the lowest available one is used by HP Smart Update Manager to pass information between processes on the local workstation where HP Smart Update Manager is executed, and the next available one is used to receive messages from remote servers.
    Port 62286 This port is the default for some internal communications. It is the listening on the remote side if there is no conflict. If a conflict occurs, the next available one is used.
    Ports 80 or 63000-63005 The logs are passed to the target and the logs are retrieved via an internal secure web server that uses port 80 if it is available or a random port between 63000 and 63005, if it is not. This support allows updates of the iLO firmware without the need to access the host server and allows servers running VMware or other virtualization platforms to update their iLO without the need to reboot their server or migrate their virtual machines to other servers.

    For Linux:
    Ports Descriptions
    Port 22 This port is establishes a connection to the remote Linux server via SSH.
    Ports 60000-60007 Random ports are used in this range to pass messages back and forth between the local and remote systems via SSH. 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. There is no guarantee that the upper limit is 60007 as it is dependent on how many target devices are selected for installation.

    Ports 61000-61007 These ports are used from the target server back to the system running HP Smart Update Manager. The same mechanism is used by the remote access code as the 60000 ports, with the first trial port as 61000. There is no guarantee that the upper limit is 61007 when a conflict occurs. For the case of ipv4-only and one NIC, the lowest available one is used by HP Smart Update Manager to pass information between processes on the local workstation where HP Smart Update Manager is executed, and the next available one is used to receive messages from remote servers.
    Port 62286 This port is the default for some internal communications. It is used for listening on the remote side if there is no conflict. If a conflict occurs, the next available one is used.
    Ports 80 or 63000-63005 The logs are passed to the target and the logs are retrieved via an internal secure web server that uses port 80 if it is available or a random port between 63000 and 63005, if it is not. This support allows updates of the iLO firmware without the need to access the host server and allows servers running VMware or other virtualization platforms to update their iLO without the need to reboot their server or migrate their virtual machines to other servers.

     

    Recovering from operating system limitations when using a Japanese character set

    Displaying the user-specified reboot message using a Japanese character set when running on a Linux operating system
    You may specify a message to be displayed prior to shutting down the system during a reboot operation. This message, when entered using the Japanese character set, is not displayed properly when running on a Japanese version of a Linux operating system due to a limitation in the operating system.

    Rebooting with the user-specified reboot message using a Japanese character set when running on a Windows operating system
    You may specify a message to be displayed prior to shutting down the system during a reboot operation. This message, when entered using the Japanese character set, causes the reboot not to occur automatically when running on a Japanese version of a Windows® operating system. In order for the reboot to occur and the reboot message to be displayed, you must select the Exit button. 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.

    The HP Smart Update Manager cannot be run in directories containing double-byte characters in the path name. Paths can be created with double-byte characters when using certain versions of the operating system, such as Japanese or Chinese.
     

    Recovering from a missing reboot message when running on SUSE LINUX Enterprise Server 9

    Running HP Smart Update Manager on SUSE LINUX Enterprise Server 9


    The user can specify a reboot message that will appear before a server reboots after a successful installation of firmware or software. However, when running HP Smart Update Manager on SUSE LINUX Enterprise Server 9, the reboot message will not appear because there is no access to the console when using SUSE LINUX Enterprise Server 9. This error is not unique to HP Smart Update Manager and it is an operating system limitation

    NOTE:  Beginning with the Firmware Maintenance CD v8.50, HP Smart Update Manager no longer runs on SUSE Enterprise Linux 9.

     

    Recovering a lost HP Smart Update Manager connection

    Mounting the Smart Update Firmware DVD on virtual media
    When either iLO or NIC firmware are updated, the HP Smart Update Manager connection is lost and cannot install components. If an access error exists, HP Smart Update Manager cancels the installation.
     

    HP SUM 'found new hardware' message

    During the discovery progress, if HP Smart Update Manager displays "Found New Hardware" pop-up message, it is because one of the self discovery components is loading a new driver and the Windows® OS discovers it a new piece of hardware.
    Similar pop-up messages may occur with Windows® 2008 operating systems when Allow Non-bundle version option on the Select Bundle Filter screen is selected.
     

    Non-matching systems error reported when building Source RPMs or installing RPMs built from source

    If HP Smart Update Manager reports non-matching systems error when trying to build Source RPMs or installing ROMs built from Source, then the operating system on the target server does not match the operating system from which you are running HP Smart Update Manager in one of the following ways: 1) The distribution of the Operating System does not match (For example, RHEL 4.7 and RHEL 4.8 would be a mismatch) 2) The architecture of the two Operating Systems does not match (For example, One server running operating system with x86 architecture and the other with x86_64 architecture) 3) The kernel version running on the two systems does not match.
    Resolution options: 1) Run HP Smart Update Manager on the target server itself (instead of remotely deploying HP Smart Update Manager) 2) Build the driver RPM locally and take the resulting RPM file from the standard location (for example, /usr/src/redhat/RPMS/i686/.rpm) and copy it back into the same directory HP Smart Update Manager was located. HP Smart Update Manager will pick up the pre-built RPM, and enable the user to deploy it anywhere they choose.
     

    Linux component version discrepancy for source RPMs

    You may observe differences in the RPM component name which may look like version mismatch for the component on '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. It is just that the RPM build adds information. So it is technically the same component.
    For example, if you select the component HP NC Series Mellanox 10GBE Driver for Linux, in the Select Items to be Installed screen, it appears as hp-minx-en-1.4.3.1-1.src.rpm and in the Installation Results screen, it appears as hp-minx-en-kmp-default-1.4.3.1_2.6.27.19_5-1.x86_64.rpm.
     

    HP SUM displays "No components found in the selected repository(ies)" message

    The error "No components found in the selected repository(ies)" is reported when there is at least one space in the path name of the repository containing the components to be installed.
    To resolve this issue, make sure that there are no spaces in the path name.
     

    Additional/Optional Actions columns are grayed when HP Smart Update Manager is maximized

    The error "No components found in the selected repository(ies)" is reported when there is at least one space in the path name of the repository containing the components to be installed.To resolve this issue, make sure that there are no spaces in the path name.
     

    Installation of components failed with 'Update returned an error' when installing Linux RPMs

    When installing any component, if the installation fails, HP Smart Update Manager will report 'Update returned an error'. You should review the associated component log for the reason for the installation failure. However, when installing RPMs using HP Smart Update Manager you may see this error when the RPMs for more than one Linux distribution are present in a single repository and a PSP bundle from the Select Bundle Filter screen is not selected. In this scenario, when there are multiple versions of source RPMs, the RPMs that are not the latest are not installed and will return "Update not needed" or "Not Updated-already current" messages. HP Smart Update Manager cannot determine which source RPMs go with which distribution because the RPMs do not contain any operating system information.

    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 Smart Update Manager (for example. hpsum /b bp000690.xml), you may experience one or more of the following:

    1) No bundles listed on the Select Bundle Filter screen.

    If you specify a bundle when starting HP Smart Update Manager, the Select Bundle Filter screen will not be shown and the Select Items to be Installed screen will be presented with the specified bundle listed as the filter. This is an expected as the bundle was preselected.

    If you then select the Select Bundle Filter link, the Select Bundle Filter screen will be presented with no bundles available for selection. This occurs because HP Smart Update Manager only recognizes the specified bundle and no others even if other bundles are present in the repository. This is working as designed.

    2) No bundle being used as a filter on the Select Items to be Installed screen.

    If you experience Issue 1 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 will no longer be listed as the filter. To use your bundle as the filter, you must exit and restart HP Smart Update Manager.

    This issue will be fixed in a future release of HP Smart Update Manager
     

    Technical Support



    In this section
    Reference documentation
    Operating system information
    HP contact information

    Reference documentation

    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:

    HP contact information

    For the name of the nearest HP authorized reseller:

    For HP technical support:


     
     

    Acronyms and abbreviations

    GUI
    Graphical User Interface
    HBA
    Host Bus Adapter
    CLI
    Command Line Interface
    HP SUM
    HP Smart Update Manager
    I/O
    Input/Output
    iLO2
    Integrated Lights-Out 2
    NIC
    Network Interface Controller
    OA
    Onboard Administrator
    POST
    Power-On Self Test
    PSP
    ProLiant Support Pack
    RBSU
    ROM-Based Setup Utility
    RILOE II
    Remote Insight Lights-Out Edition II
    SAN
    Storage Area Network
    SAS
    Serial Attached SCSI
    SCSI
    Small Computer System Interface
    SOAP
    Simple Object Access Protocol
    SSH
    Secure Shell
    SSL
    Secure Sockets Layer
    WMI
    Windows Management Instrumentation