HP Smart Update Manager Help

Contents

Introduction
        HP Smart Update Manager overview
        Using this guide
        New features of HP SUM 4.1.0
        Minimum requirements
                Minimum requirements for Windows servers
                Minimum requirements for Linux x86 servers
        Supported deliverables overview
                Obtaining the HP SUM utility
                Support and limitations of HP SUM
        Deployment from HP SUM
                Executing HP SUM
                Deploying software using the ProLiant Support Pack (PSP) for Microsoft Windows
                Deploying software using the Integrity Support Pack (ISP) for Microsoft Windows
                Deploying software using the ProLiant Support Pack for Linux
                Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD
                Deploying firmware using the HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundles

HP SUM 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 the location to check for updates
                Download Permission (applicable only for ProLiant servers)
                Selecting an installation host
                Selecting bundles to filter
                Selecting components to install
                Component selection pane
                Viewing the installation results
        Multiple-host installations
                Selecting remote hosts or groups
                Searching for remote hosts
                Managing hosts
                Managing groups
                Entering credentials for hosts
                Selecting bundles to filter on multiple hosts
                Selecting components to install on multiple hosts
                Firmware update on HP Integrity BL860c/BL870c/BL890c i2 Servers
                Viewing the installation results for multiple hosts

Scripted Deployment
        Command-line interface
                Command-line syntax
                Command-line arguments
                Component configuration for Windows components only
                Command-line examples
                Return codes
                Windows smart component return codes
                Linux smart component return codes
                Linux RPM 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
        Software component configuration
        Deploying firmware and software simultaneously
        Server virtualization detection and support
        Configuring IPv6 networks with HP Smart Update Manager
        Configuring IPv6 for Windows Server 2003
        Configuring IPv6 for Windows Server 2008
        Configuring IPv6 for Linux

Troubleshooting
        Recovering from a failed ROM upgrade
        Recovering from a failed system ROM upgrade
        Recovering from a failed option ROM upgrade
        Recovering from an installation failure
        Collecting trace directories
        Recovering from a discovery failure
        Troubleshooting connection errors
        HP SUM hangs during discovery
        Recovering from a loss of Linux remote functionality
        Configuring firewall settings
        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
        Displaying the user-specified reboot message using a Japanese character set
        Rebooting with the user-specified reboot message using a Japanese character set
        Recovering from Fatal Error - application will exit message
        Running in a directory path containing double-byte characters
        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
        Recovering a lost HP Smart Update Manager connection
        HP Smart Update Firmware DVD mounted using iLO virtual media
        Troubleshooting HP Smart Update Manager in IPv6 networks
        Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2003 environment
        Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2008 environment
        Troubleshooting HP Smart Update Manager in IPv6 Red Hat and Novell SUSE-based Linux environments
        HP SUM 'found new hardware' message
        Non-matching systems error reported when building source Linux RPMs or installing Linux 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 SUM is maximized
        Installation of components failed with 'Update returned an error' when installing Linux RPMs
        Issues related to bundle filtering on the Select Items to be Installed and Select Bundle Filter screens
        HP SUM fails on Vista due to McAfee firewalls
        Virtual Connect firmware upgrade using HP SUM fails if VC reports an invalid or bad health state

Technical support
        Reference documentation
        Operating system information
        HP contact information

Acronyms and abbreviations
 

Introduction

In this section

HP Smart Update Manager overview
Using this guide
New features of HP SUM 4.1.0
Minimum requirements
        Minimum requirements for Windows servers
        Minimum requirements for Linux x86 servers
Supported deliverables overview
        Obtaining the HP SUM utility
        Support and limitations of HP SUM
Deployment from HP SUM
        Executing HP SUM
        Deploying software using the ProLiant Support Pack (PSP) for Microsoft Windows
        Deploying software using the Integrity Support Pack (ISP) for Microsoft Windows
        Deploying software using ProLiant Support Pack for in Linux
        Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD
        Deploying firmware using the HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundles
 

HP Smart Update Manager overview

HP SUM is a technology, included in many HP products for installing and updating firmware and software components on HP ProLiant and HP Integrity servers, enclosures, and options.

HP SUM provides a GUI and a command-line scriptable interface for:

IMPORTANT: Throughout this document, most references to the deployment of firmware apply only to HP SUM when used with HP ProLiant servers. For HP Integrity servers, deploying firmware using HP SUM only applies to BL860c/BL870c/BL890c i2 Servers.

HP SUM has an integrated hardware and software discovery engine that discovers the installed hardware and current versions of firmware and software 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 firmware updates are handled in a manner that reduces any downtime required for the firmware update process.

HP SUM does not require an agent for remote installations because 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 SUM copies the log files from the remote targets back to the system where HP SUM is executed.

Key features of HP SUM include:

NOTE: HP SUM does not support third-party controllers. This includes flashing hard drives behind these controllers.

 

Using this guide

HP SUM is delivered with many different deliverables. A deliverable is an HP product which contains HP SUM and a set of firmware or software components. Some examples are the ProLiant Support for Windows and the HP Smart Update Firmware DVD. It is important that you review the overview section that follows this section for your deliverable to verify any specific limitations to HP SUM features that apply. Then, you can review the sections describing the features of HP SUM. For more information, see the Supported deliverables overview section.
 

New features of HP SUM 4.1.0

This release of HP SUM includes the following new support:


 

Minimum requirements

Minimum requirements for Windows operating systems
Minimum requirements for Linux

NOTE: For Linux and Windows operating systems, the respective device drivers for the embedded/add-on devices in the target servers must be installed for HP SUM to discover the devices.

NOTE: For a current list of supported operating systems on ProLiant servers, see the PSP website (http://www.hp.com/servers/psp).

Minimum requirements for Windows servers

To successfully deploy HP SUM on HP ProLiant and Integrity target systems based on a Windows operating system, the following must be available:


 

Minimum requirements for Linux x86 servers

To successfully deploy HP SUM on ProLiant target systems based on a Linux operating system, the following must be available: (HP SUM does not support Linux on HP Integrity systems.)

To successfully deploy HP SUM on remote target systems based on a Linux operating system, the following must be available:

Starting with Linux PSP 8.40 and later, ensure the following platform-specific compatibility libraries are also installed.

 

Supported deliverables overview

HP SUM support is specific to the deliverable in which it is delivered. Make sure you use the correct version of HP SUM that is released along with the deliverable supporting the environment.

NOTE: Not all functionality is available in each version of HP SUM. Before using HP SUM that comes with a deliverable, review the Support and limitations of that version of HP SUM to determine if it has the features that you need.

Obtaining the HP SUM utility

The HP SUM utility is available from the following:

Support and limitations of HP SUM

Before installing HP SUM, use the following table to verify that you are using the appropriate software version.

HP SUM version Delivered with Support and limitations
3.7.1
  • HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundles for Windows and Linux
  • Support for BL860c/BL870c/BL890c i2 Servers firmware - This support is currently available only in HP SUM 3.7.1 and will be integrated into a future release of HP SUM
  • No support for downloading the latest versions of components from the HP FTP site
  • No report functionality is available
  • 4.0.0 For ProLiant Servers:
  • HP ProLiant Support Pack for Windows 8.40
  • HP ProLiant Support Pack for Linux 8.40
  • HP Smart Update DVD 9.0
  • For ProLiant Workstation Blades:
  • HP Workstation Support Pack for Windows for HP WS460c G6 Blade
  • HP Smart Update DVD 9.0 (offline only)
  • No support for BL860c/BL870c/BL890c i2 Servers firmware or Integrity Support Pack
  • 4.0.0.64
  • HP Integrity Support Pack for Windows on Itanium-based systems
  • Support for Integrity Support Pack for Windows 7.00
  • No support for BL860c/BL870c/BL890c i2 Servers firmware deployment
  • No support to download the latest components available from ftp.hp.com through HP SUM GUI and command line options
  • 4.0.1
  • HP ProLiant Support Pack for Windows 8.50
  • HP ProLiant Support Pack for Linux 8.50
  • No support for BL860c/BL870c/BL890c i2 Servers firmware or HP Integrity Support Pack
  • 4.0.2
  • HP Smart Update Firmware DVD 9.10
  • No support for BL860c/BL870c/BL890c i2 Servers firmware or HP Integrity Support Pack
  • 4.1.0
  • HP ProLiant Support Pack for Windows 8.60
  • HP ProLiant Support Pack for Linux 8.60
  • No support for BL860c/BL870c/BL890c i2 Servers firmware or HP Integrity Support Pack

  •  

    Deployment from HP SUM

    In this Section:

    Executing HP SUM
    Deploying software using the ProLiant Support Pack (PSP) for Microsoft Windows
    Deploying software using the Integrity Support Pack (ISP) for Microsoft Windows
    Deploying software using the ProLiant Support Pack for Linux
    Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD
    Deploying firmware for HP Integrity BL860c/BL870c/BL890c i2 Servers

    Executing HP SUM

    HP SUM provides three modes of execution for users:

    Deploying software using the ProLiant Support Pack (PSP) for Microsoft Windows

    The HP SUM utility delivered with the Windows PSP enables you to deploy software components from a single, easy-to-use interface for ProLiant server and options.

    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 SUM utility now provides this functionality. The utility also provides installation logic and version control that automatically verifies dependencies, installing only the correct updates for optimal configuration.

    Users can now deploy the components simultaneously for ProLiant servers and options. For more information about simultaneous deployment, see Deploying firmware and software simultaneously.

    For more information about PSP, 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).

    HP SUM delivered with HP Workstation Support Pack supports the software deployment on Windows for HP ProLiant WS460c G6 Blade. This support is available for the local host only.
     

    Deploying software using the Integrity Support Pack (ISP) for Microsoft Windows

    The HP SUM utility enables you to deploy Windows ISP software components for HP Integrity Servers from a single, easy-to-use interface. This utility enables legacy support of existing software components while simplifying the overall deployment process. You do not have to run the SETUP executable files SETUPC.EXE, SETUPEX.EXE, and SETUP.EXE, because the HP SUM 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.

    NOTE: In HP Integrity servers, HP SUM does not support the ability to download the latest components from ftp.hp.com, as these components are not in the catalog on the HP FTP site.

    NOTE: Use the version of HP SUM that comes with the ISP when deploying the components that are included in that deliverable.

    For more information about ISP implementation by operating system, see the HP Window-on-Integrity website (http://www.hp.com/go/windows-on-integrity-docs), or by server model number, see the HP Integrity Server site (http://www.hp.com/go/integrity_servers-docs).

    Deploying software using the ProLiant Support Pack for Linux

    Beginning with PSP for Linux 8.40 or later, the HP SUM utility enables you to deploy Linux PSP software components (RPMs) 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 SUM provides new GUI and a command-line, scriptable interface for deployment to target servers. HP SUM 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 SUM utility enables software deployment for multiple HP ProLiant servers from a single GUI.

    For more information about PSP, 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 for ProLiant servers using the HP Smart Update Firmware DVD

    The HP Smart Update Firmware DVD provides a collection of firmware bundles containing HP SUM and firmware for ProLiant servers 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 ProLiant servers and options. The Firmware DVD contains all the firmware for the supported HP ProLiant servers including BladeSystem enclosures and Virtual Connect firmware.

    All firmware smart components are placed in the \hp\swpackages directory for use by HP SUM. If additional firmware smart components are required, then the HP Smart Update Firmware DVD can be copied to a USB key, and these additional components added to the \hp\swpackages directory. If HP SUM supports the type of firmware added, then 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 SUM. Before using HP SUM 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.

    NOTE: 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.

    HP SUM 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 HP Smart Update Firmware DVD.

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

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

    IMPORTANT: Before deploying firmware updates to 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 about deploying firmware on HP ProLiant servers, see the HP Smart Update Firmware DVD 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).

    NOTE: Currently, HP SUM cannot be used to deploy firmware on HP Integrity servers except for HP Integrity BL860c/BL870c/BL890c i2 Servers.

     

    HP SUM supported firmware for HP ProLiant servers

    ComponentSupported
    HP ProLiant ML/DL/SL series System ROMYes
    HP Workstation WS460c G6 Blade ROMYes, offline only
    HP ProLiant Blade Servers ROMYes
    HP ProLiant 100-series Servers ROMYes
    iLO 2 firmwareYes, local and remote
    iLO 3 firmware***Yes, local and remote
    LO-100 firmware***Yes
    Broadcom NIC firmwareYes
    Intel NIC firmwareNo
    QLogic NIC firmwareYes, offline only
    Mellanox NIC firmwareYes
    Power Management Controller firmwareYes
    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 firmwareYes, online only
    Onboard Administrator Firmware****Yes, online only
    CPLD/SPLD*****Yes

    When updating HP ProLiant blade servers in an HP BladeSystem Matrix, do not select ftp.hp.com to download the latest components. Ensure the component source contains versions of components that match the BladeSystem Matrix Compatibility chart before using HP SUM to deploy any software of firmware.

    To view the BladeSystem Matrix compatibility chart, see the HP website (www.hp.com/go/matrixcompatibility.)

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

    HP SUM 4.1.0 and later support deploying Virtual Connect firmware version 3.x and later only. HP recommends using VCSU to deploy VC firmware version 2.3x and earlier.

    HP SUM does not upgrade the VC firmware in any situation where the Virtual Connect health state is reported as bad or invalid.

    **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.

    ***HP SUM does not support direct deployment of LO-100 (using the LO-100 BMC IP) or iLO 3 firmware from the remote hosts section. To flash the LO-100 or iLO 3 firmware component, you must go through the server IP.

    ****HP SUM does not support downgrading the Onboard Administrator firmware from a new major release to an older release version (for example, 3.x to 2.x). However, 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 HP Onboard Administrator User Guide.

    *****HP SUM 4.1.0 and later has the ability to flash the CPLD/SPLD for HP ProLiant BL280 G6 and BL490 G6 servers. The CPLD/SPLD flash components are not part of the HP SUM deliverable and must be manually downloaded from the HP website (http://www.hp.com). Run HP SUM and deploy the CPLD/SPLD component.

    IMPORTANT: After flashing the CPLD/SPLD, you must cycle power for the changes to take effect. Remove the blade from the enclosure, and then wait 30 seconds before re-inserting it. Pressing the power button is not sufficient.
    When performing this flash upgrade from a Linux OS environment, the HP ProLiant Channel Interface Device Driver for iLO2 must be installed and running before executing the upgrade. If the HP ProLiant Channel Interface Device Driver is not installed and running, the following error message displays: "The software is not supported for installation on this system. You must install the iLO Channel Interface driver to use this component."
    No driver requirement exists for the Windows OS flash upgrade.

     

    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 the DVD. Insert a USB key containing the Firmware DVD ISO image created by using the HP USB Key Creator for Windows utility into a server USB port or the SUV (Serial-USB-Video) cable attached to the blade.

    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. After installation, the utility places a shortcut in the HP System Tools folder in the Programs start menu.

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

    1. Insert the HP USB drive key in an available USB port.
    2. Select the HP USB Key Utility shortcut in the HP System Tools folder.
    3. Complete each step presented by the application.
    4. The HP USB Key Creator formats the USB key. Ensure that you are using a USB key that is at least 1GB in size and does not contain any valuable files.

    For Linux, the USB key can be created manually:

    1. Obtain SYSLINUX 3.75 or higher from http://www.syslinux.zytor.com, and download it to a Linux workstation.
    2. Install the SYSLINUX RPM obtained in step 1.
    3. If a directory does not already exist, create one for the USB key mount point, for example, mkdir /usbkey.
    4. Insert the USB key, and then mount it. The device mount point might vary, depending on whether other SCSI drives are also installed on the server. Therefore, the device mount point can be sdb1, sdc1, and so on.

      mount /dev/sda1 /usbkey

    5. Use the ./syslinux /usbkey command to write out the boot partition to the USB key. Failure to run this command might lead to a key that does not boot the Firmware DVD until the SYSLINUX command is successful.
    6. Create a directory to mount the DVD image, for example, mkdir /cd_mount_point.
    7. Insert the Firmware DVD or mount the Firmware DVD ISO through a loopback:

      mount /dev/cdrom /cd_mount_point or mount -t iso9660 firmware-<version>.iso /cd_mount_point -o loop

    8. Change to the /usb directory on the DVD:

      cd /cd_mount_point/usb

    9. Execute the usbcreator.sh shell script passing in the DVD mount point and the USB mount point to move the Firmware DVD files to the USB key:

      ./usbcreator.sh /cd_mount_point /usbkey

    10. If additional components must be added to the USB, copy the components into the /hp/swpackages (Linux) or the \hp\swpackages (Windows operating system) directory. If the version can support the type of components added, then HP SUM picks them up automatically.
    11. Unmount the DVD and the USB key. This must match the initial mount point in step 4.
    12. Remove the USB key and DVD.

    13.  

      Using a hard drive

      1. Copy the contents of the \hp\swpackages directory from the DVD or ISO image to a directory on the hard drive where HP SUM is to be executed.
      2. NOTE: Ensure that execute privileges are available in Linux by using the chmod 700 * command. By default, the files are copied off the DVD in Linux as read-only with no execution privileges.

      3. Copy any updated files into the same directory where the files were copied in step 1.
      4. Execute HP SUM to have the new components recognized.

       

      Deploying components not on HP Smart Update Firmware DVD

      Make sure you use the correct version that is released along with the deliverable supporting the environment.

      If you have components that are not on the HP Smart Update Firmware DVD that you want to deploy to a ProLiant server or option, you can include other smart components in the HP SUM environment. To deploy software and firmware components that are not on the HP Smart Update Firmware DVD:

      1. Obtain the components from the HP website (http://www.hp.com).
      2. Create a bootable USB key, or copy the \hp\swpackages directory to the hard drive, and then remove the read-only bit (Linux only).
      3. Add the components to the \hp\swpackages directory on the USB key or to the directory on the hard drive with the components from the HP Smart Update Firmware DVD.
      4. Start HP SUM.
      5. On the Source Selection screen, you can specify the directory where all of the components are located as well as select the Check ftp.hp.com (for ProLiant servers) checkbox if you want to include the latest version of software and firmware components from the HP website (http://www.hp.com).
      6. Select the checkbox for non-bundle versions, and then click OK.

       

      Trusted Platform Module

      The TPM, 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:

      1. Click Start, and then search for gpedit.msc in the Search Text box.
      2. When the Local Group Policy Editor starts, click Local Computer Policy.
      3. Click Computer Configuration>Administrative Templates>Windows Components>BitLocker Drive Encryption.
      4. When the BitLocker settings are displayed, double-click Control Panel Setup: Enable Advanced startup options.
      5. When the dialog box appears, click Disable.
      6. Close all the windows, and then start the firmware update.

      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.

      Scenario Result
      If the TPM is detected and enabled, the installation is not silent, and a system ROM must be updated.A pop-up warning message appears. After OK is selected, you can continue. The installation is not canceled.
      If the TPM is detected and enabled, the installation is silent, the /tpmbypass switch is not given, and any firmware updated must be applied to the server. No pop-up warning appears. A new log file is generated (%systemdrive%\cpqsystem\log\cpqstub.log). Because the installation is silent, the installation is terminated and cannot continue.
      If the TPM is detected and enabled with Option ROM Measuring, the installation is not silent, and a system ROM must be updated.A pop-up warning message appears. After OK is selected, you can continue. The installation is not canceled.
      If the TPM is detected and enabled with Option ROM Measuring, the installation is silent; the /tpmbypass switch is not given, and any firmware updated must be applied to the server. No pop-up warning appears. A new log file is generated (%systemdrive%\cpqsystem\log\cpqstub.log). Because the installation is silent, the installation is terminated and cannot continue.
      If the TPM is detected and enabled, the installation is silent, and the /tpmbypass switch is supplied. The installation occurs.

      Other scenarios do not affect the normal installation procedure.

      Deploying firmware using the HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundles

      You can only deploy this firmware in HP SUM, included in their respective Windows and Linux bundles. For supported HP SUM versions, see Support and limitations.

      Deploying firmware to the HP Integrity BL860c/BL870c/BL890c i2 Servers is done remotely and is the same as deploying other firmware like OA or VC with the following exceptions:

      NOTE: In HP Integrity servers, HP SUM does not support the ability to download the latest components from ftp.hp.com, as these components are not in the catalog on the HP FTP site.

      NOTE: Use the version of HP SUM that comes with the Integrity Bundle when deploying the firmware to the HP Integrity BL860c/BL870c/BL890c i2 Servers.

      HP SUM supported firmware for HP Integrity servers

      Component Supported
      Online System ROM Yes
      FPGA firmware Yes
      iLO-3 MP firmware Yes
      Power Monitor firmware Yes


       

      HP SUM 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 the location to check for updates
              Download Permission (applicable only for ProLiant servers)
              Selecting an installation host
              Selecting bundles to filter
              Selecting components to install
              Component selection pane
              Viewing the installation results
      Multiple-host installations
              Selecting remote hosts or groups
              Searching for remote hosts
              Managing hosts
              Managing groups
              Entering credentials for hosts
              Selecting bundles to filter on multiple hosts
              Selecting components to install on multiple hosts
              Firmware update on HP Integrity BL860c/BL870c/BL890c i2 Servers
              Viewing the installation results on multiple hosts

      Deployment scenarios

      HP SUM deploys firmware and software on a local host or one or more remote hosts. The remote hosts must be online and running the same operating system as the system running HP SUM. For example, when the remote hosts are running Linux, HP SUM must also be running on a Linux operating system.

      The following table describes when typical HP SUM deployment scenarios are used.

      Scenario Used when
      Graphical deployment on a local host
      • 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
      • 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
      • 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
      • 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

      To deploy components to a single local host, use the HP SUM GUI.

      1. Ensure all minimum requirements are met as described in "Minimum requirements."
      2. Ensure that the components to be deployed are accessible to the local host.

      For information about performing the deployment using the GUI, 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 "Scripted deployment" 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, 3 Gb SAS BL Switch firmware, or Fibre Channel Module for c-Class BladeSystem or BladeSystem Onboard Administrator.

    To deploy components to multiple remote hosts using the GUI:

    1. Ensure that all minimum requirements are met as described in "Minimum requirements."
    2. Ensure that the components to be deployed are accessible to the administrative system.

    For more information about performing the deployment using the graphical interface, see "Multiple-host installations using the GUI".

    To deploy components to multiple remote hosts using the CLI:

    1. Ensure that all minimum requirements are met as described in "Minimum requirements."
    2. Ensure that the components to be deployed are accessible to the administrative system.
    3. Create a script to customize the deployment. For more information, see "Scripted deployment."
    4. Execute the script.

     

    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 deploy components on a local host by using the HP Smart Update Manager GUI. To access the HP Smart Update Manager, see Deployment Options.

    Selecting the location to check for updates

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

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

    NOTE: HP SUM does not support the ability to download the latest components from ftp.hp.com to HP Integrity servers.

    For HP ProLiant servers, the following screen appears when selecting the location to check for updates.

    When using HP SUM delivered with the Integrity support pack, the following screen appears when selecting the location to check for updates, since HP SUM does not support the ability to download the latest components from ftp.hp.com for these servers.

    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 SUM builds an inventory of available updates.
     

    Download Permission (applicable only for ProLiant servers)

    Before starting any discovery, HP SUM searches the web digest for self-discovery components that must be downloaded for the discovery process. Self-discovered components are components including but not limited to NIC firmware and tape firmware that HP SUM uses to discover the hardware in the system. If the Check ftp.hp.com checkbox has been selected on the previous screen, then the Download Permission screen might 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 downloading. 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 then click Next.

    The Select Installation Host(s) screen enables you to choose a host for component installation. By default, the first time you run HP SUM on a particular system, the only host available is the local host. However, you can also select remote hosts as your targets. For more information about using the GUI 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 on the Select Installation Host(s) screen is selected, you can sort your view of the host list by selecting Only Hosts, Only Groups, or Both.

    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 SUM 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 perform a remote deployment, exit HP SUM, and then install the expect-5.x package from the Linux operating system media. To proceed with remote deployment, start HP SUM.

    To continue to system discovery, click Next and the discovery process occurs. If the system discovery process finds one or more predefined bundles, the Select Bundle Filter screen appears.
     

    Selecting bundles to filter

    When the discovery process is complete and there is a bundle in the repository, 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 SUM, this screen does not appear.

    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 product versions.

    To proceed with the deployment process, click OK.

    NOTE: If a PSP, ISP, or bundle that supports the target's operating system is not present in the repository, HP SUM might 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 a bundle has been selected, the Select Items to be Installed screen appears. The Select Items to be Installed screen displays information about which components are available for installation on your system and enables you to select or clear components to install.

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

    When updating installation for some but not all NIC firmware 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 SUM.

    When multiple hardware devices such as hard drives or array controllers exist in a single server, HP SUM lists each device only one time. 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 latest to earliest. 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 the Select Bundle Filter link in the 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 Select Items to be Installed screen under certain combinations of dependencies between the components selected for installation.

    If all of the previous conditions are true, then HP SUM detects it and a notification to reboot appears to continue the installation. All installable components appear in the original update list, but only the components shown before the notification are installed. You must reboot to complete the installation and then restart HP SUM 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.

    When Always is selected, then the system will always be rebooted after an installation, unless there is a component installation failure. When 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.

    NOTE: The reboot options do not apply when deploying firmware to HP Integrity BL860c/BL870c/BL890c i2 Servers with HP SUM. HP SUM will reboot the server automatically during the firmware update process when the user has selected Upload and Activate. Checking any other reboot options or setting a reboot delay is not applicable.

    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) components available for installation based on your server and hardware options. HP SUM verifies 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 SUM.

    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 component displays as Build Failed, you must resolve the issue before proceeding with the installation.

    If a failed dependency occurs, then you must resolve it by ensuring the prerequisite libraries or the appropriate software or firmware components are available before proceeding with the installation.

    The following figure displays the Failed Dependencies screen.

    Installation options

    You can specify firmware upgrade behavior for installable components by selecting one or more options from the Additional Options field.

    The following table illustrates how changing the options for firmware upgrade behavior changes 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 the following results.

    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 the following results.

    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. 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 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.

    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:

    A new file contains detailed information on the execution of HP SUM.

    NOTE: Using the offline environments provided by the HP 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

    HP SUM provides simultaneous firmware and software deployment for multiple ProLiant remote targets and options in both GUI and CLI modes. For performance and optimization, if more than 20 remote targets exist for simultaneous update, HP SUM starts with the update for the first 20 targets and when each target update completes, then the next target in line is selected until all targets have been updated.

    After you start HP SUM, the Source Selection screen appears, enabling you to specify where to find the components that you want to deploy. After selecting the component's location, the Inventory Progress screen appears while HP SUM 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.

    To search for remote hosts, see "Searching for remote hosts" 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. To continue, click Next.
    3. Enter the credentials for the host.
    4. Click OK to proceed, as described in Selecting components to install on multiple hosts.
    5. When the installation is complete, the Installations results for multiple hosts screen appears.
    6. NOTE: When running on a Linux system and the expect-5.x package is not installed, HP SUM 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 perform a remote deployment, exit HP SUM, and then install the expect-5.x package from the Linux operating system media. To proceed with remote deployment, start HP SUM.

    Searching for remote hosts

    Clicking Host Search enables you to search for hosts in the network using the following options:

    Managing hosts

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

    NOTE: Local hosts cannot be included in a list with remote hosts or in a group. When selecting iLO and iLO 2 for ProLiant, iLO 3 for ProLiant and Integrity, OA, VC, or 3 Gb SAS BL Switch for ProLiant as a target, only the firmware component for that particular 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 version or the server host.

    NOTE: An LO-100 BMC IP cannot be used as a target to update the LO-100 firmware directly. If used, the following pop-up message displays: Could not contact host.

    You can only update the LO-100 firmware when updating firmware on a 100-series server.

    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 you want to add.
    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 Edit Host. The Edit Host dialog box appears.
    2. Edit the Host Name and Description.
    3. Click OK.

    To delete a host:

    1. On the Manage Hosts screen, click Delete Host.
    2. When the confirmation screen appears, click Yes.

    Managing groups

    To add, edit, or delete groups, click Manage Groups. 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 New Host. For more information on adding hosts, see "Managing hosts."
    5. Click Enter 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 group, and then on the Manage Groups screen, click Edit Group. The Edit Group dialog box appears.
    2. Edit the group name as needed.
    3. Edit the optional user-defined description given to the host as needed.
    4. Click Enter and Remove to add or remove hosts as needed.
    5. Click OK.

    To delete a group:

    1. Select the group on the Manage Groups screen, and then click Delete Group.
    2. When the confirmation screen appears, click Yes.

    Entering credentials for hosts

    When you select a single remote host, the Enter Credentials for Host screen appears. You must enter your username and password as the credentials for the host.

    To enter the credentials for the host, choose one of the following:

    NOTE: When deploying components to non-server targets, you cannot use the Use Current Credentials option since it is not possible to share credentials between a system and a non-server target.

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

    To continue, click OK.

    NOTE: When deploying components to Windows operating system targets, you might be required to enter the username in DOMAIN\USER format, where <user> is the user account name and <domain> is the computer name or active directory domain of the user account.

    When you select a group or multiple hosts, the Enter Credentials for Group screen appears.

    The screen separates the remaining hosts that still require credentials from the completed hosts.

    Each pane is divided into the following columns:

    To enter the credentials for the host, perform the following steps:

    1. In the left pane, select the host from the list of hosts requiring credentials. If all credentials are the same, to select all the hosts on the list, click Select All.
    2. To enter the required credentials and move the selected host to the Completed Hosts pane, click Enter.
    3. To continue, click Next.
    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.


     

    Selecting bundles to filter on multiple hosts

    If the system discovery finds one or more predefined bundles, the Select Bundle Filter screen appears. If you specify a bundle on the command line when starting HP SUM, this screen does not appear.

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

    Selecting components to install on multiple hosts

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

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

    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 SUM 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, on the Select Items to be Installed screen, to proceed with the installation, click Install.
     

    Updating Firmware on HP Integrity BL860c/BL870c/BL890c i2 Servers

    One firmware package for the HP Integrity BL860c/BL870c/BL890c i2 Servers includes System Firmware which requires a reboot to activate the firmware. To activate and configure the firmware, select Configure Now, and then select one of the following options:

    If the user has not changed the default option or has selected Upload and Activate, a warning message displays, indicating that HP SUM will reboot the server during the firmware update process.

    To continue the update, press OK.

    You can deploy the Online System, FPGA, iLO-3 MP and Power Monitor firmware using CLI in silent mode. However, you cannot specify the Upload and Do not Activate mode using CLI. Only the default Update and Activate mode is available, and no parameter is required.
     

    Viewing the installation results for multiple hosts

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

    The Installation Results screen is divided into the following columns:

    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 the process.
    Installation failed One or more of the component installations have failed.

    The Installation Results screen also includes the following buttons:

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

    Proceed as described in Viewing the installation results.
     

    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 SUM command-line interface enables you to script custom installations.

    Command-line syntax

    The general command-line syntax for HP SUM is:
    hpsum [/h[elp]] [/?] [/f[orce]] [/f[orce]:bundle] [/f[orce]:rom] [/f[orce]:software] [/f[orce]:all ] [/g (/downgrade)] [/e (/rewrite)] [/m[utual])] [/c[omponent] <component_to_install>] [/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_proxy] [proxy_server] [/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"][<component1_to_install> <component2_to_install> ...] [<bundle1_to_install> <bundle2_to_install> ...]

    HP SUM 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.

    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. On Linux operating systems, use a hyphen (-) before each argument.

    If the /s[ilent] argument is not included on the command line, the HP SUM GUI appears.

    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.

    NOTE: When using HP SUM with HP Integrity BL860c/BL870c/BL890c i2 Server bundles, HP SUM does not have any command-line arguments to specify the Upload and Do Not activate option. If HP SUM is started from the command line using the silent argument (/s[ilent]), then the system being updated reboots automatically. Also, no reporting functionality using CLI is available when using HP SUM for firmware updates on these servers.

     

    Command-line arguments

    HP SUM recognizes the following command-line arguments. These arguments prepopulate the GUI in the Select Items to be Installed screen. If you specify the host or group, then the Select Items to be Installed screen does not appear.

    You cannot use some arguments, such as /romonly and /softwareonly together.

    Command-line argument Description
    HELP
    /h[elp] or /? This argument displays command line Help information.
    INSTALLATION 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, then 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 SUM GUI appears.

    /allow_update_to_bundle This argument is a filter switch and enables the user to install newer versions of components defined in a PSP, ISP, 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, then only one bundle can be specified with the argument. However, multiple /b arguments and bundles can be specified on the same line.

    If the /b[undle] argument is not used, then multiple bundles can be specified at the same time, but the bundles need to be separated by a blank and listed after all the arguments on the command line.

    Multiple components and bundles can be specified on the same command line. When mixing components and bundles on the command line, the filter switches control what components and bundles are installed.

    /express_install This argument starts express install (for local host only). HP SUM performs discovery, install, or exit without user interaction. The user can cancel or terminate HP SUM.
    /use_location "file_share" This argument specifies a directory or file share that contains the PSP, ISP, and components for use with HP SUM. The file_share format must be a mapped file share and not in UNC format.

    If you do not specify this argument, the directory containing hpsum.exe or HP SUM is used by default. The logged-in account must have access to this location.

    The /user and /passwd arguments do not have any effect when attempting to access the file share. You can use those arguments only when connecting to a target system.

    /use_web This argument specifies that the checkbox for Check ftp.hp.com on the Source Selection screen is selected. This enables components to be retrieved from hp.com and used in the list of possible updates. This argument is not supported on HP Integrity Servers.
    /use_proxy <Proxy server> This argument enables the inclusion of a proxy server (and port number) to access ftp.hp.com. This parameter must be used with /use_web. For example, /use_web /use_proxy <1.22.33.44:80>. This argument is not supported on HP Integrity Servers.
    /proxy_script <Proxy script> This argument enables the inclusion of a proxy script to access ftp.hp.com. This parameter must be used with /use_web. For example, /use_web /proxy_script <autoproxy.com>. This argument is not supported on HP Integrity Servers.
    /use_d[ownloaded] This argument specifies that the checkbox for Include components previously downloaded from HP.com on the Source Selection screen is selected. This enables those previously downloaded components to be included in the list of possible updates. This argument is not supported on HP Integrity Servers.
    /tpmbypass or /ignore_tpm This argument specifies that if a TPM is enabled, then the warning message can be ignored and component installation continues.
    /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. This argument does not apply to HP Integrity Servers.
    /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 are not 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. This argument does not apply to HP Integrity Servers.
    /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 no bundles are specified on the command line, and multiple bundles are in the directory, then the /use_latest argument enables HP SUM to use the bundle with the latest version for installation.
    /romonly This argument is a filter switch and enables the user to view only the firmware components required for installation. When using this filter switch, you must exit, and then restart HP SUM to return to an unfiltered state. Do not use the /romonly argument with the /softwareonly argument. (Applies to firmware only.)
    /softwareonly This argument is a filter switch and enables the user to view only the software components required for installation. When using this filter switch, you must exit, and then restart HP SUM 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

    <error>=BadPassword

    <error>=FailedDependencies

    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 SUM session in progress. This argument overrides the session in progress and reinitializes the installation framework on the remote host.
    /on_failed_dependency This argument informs 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.

    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 operating systems and 60 seconds for Linux.
    • For Linux, the Reboot Delay time is converted from seconds to minutes, and 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.
    CREATING HOST GROUPS
    /group "group_name" This argument specifies an already defined group name in the HP SUM GUI.
    SIMULATING HP SUM
    /dryrun This argument simulates the installation for a test run. Nothing is installed.
    TARGETS
    /user <username> or /username <username> This argument enables you to log in to the remote target (except for the OA target) with the user ID. For the OA target, see /oa_username argument.
    /psswd <password> This argument enables you to use the password for the user ID specified in the /user parameter (except for the OA target). The password is used to log in to remote targets. For the OA target, see /oa_password argument.
    /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.
    LOG FILES
    /logdir "path" This argument enables you to redirect the output from HP SUM 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 SUM 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, a 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 name is of the format, HPSUM_Report_<date>_<time>.html..

    By default, it is located in the present working directory from where HP SUM is initiated. If that location is write-protected, the report can be found in the same directory as the HP SUM log files.

    /inventory_report This argument generates a report listing of the components in the specified repository. The report name is of the format, HPSUM_Inventory_Report_<date>_<time>.html..

    By default, it is located in the present working directory from where HP SUM is initiated. If that location is write-protected, the report can be found in the same directory as the HP SUM log files.

    /firmware_report This argument generates a report listing of the firmware in the specified repository. The report name is of the format, HPSUM_Firmware_Report_<date>_<time>.html.

    By default, it is located in the present working directory from where HP SUM is initiated. If that location is write-protected, the report can be found in the same directory as the HP SUM log files. (This CLI does not apply to firmware updates on the HP Integrity BL860c/BL870c/BL890c i2 Servers.)

    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 "Input files".
    /deleteinputfile "filename" This argument enables you to instruct HP SUM to delete the input file after it has been read in.
    ENTERING OA CREDENTIALS
    oa_username This argument provides the username credential for OA associated with VC specified with "target" command-line parameter. Only one set of OA credentials can be specified with command-line parameters. You can only add multiple VC targets to command-line parameters with "target" parameter if the credentials of OAs associated with specified VCs are the same. The argument oa_username is not required if VC has the same credentials as the associated OA. You do not need to provide an OA network address associated with Virtual Connect. HP SUM queries it from a specified VC target.

    To update multiple VCs with different username and password or VCs with OAs which have different credentials, the corresponding input files OAUID and OAPWD must be used.

    oa_password This argument provides the username credential for OA associated with VC specified with "target" command-line parameter. Only one set of OA credentials can be specified with command-line parameters. You can only add multiple VC targets to command-line parameters with "target" parameter if the credentials of OAs associated with specified VCs are the same. The argument oa_password is not required if VC has the same credentials as the associated OA. You do not need to provide an OA network address associated with Virtual Connect. HP SUM queries it from a specified VC target.
    To update multiple VCs with different username and password or VCs with OAs which have different credentials, the corresponding input files OAUID and OAPWD must be used.

    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 CD or other read-only media, or the component cannot be configured. Configuration for a given component only needs to be executed one time. 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, the hpsum_config command returns 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.
     

    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 software components from the 7.90 PSP and firmware components, which HP SUM determined are required 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 software components from the 7.80 PSP, which HP SUM determined are required to be installed, were installed. No firmware was installed.

    Example 3:

    This command-line input deploys firmware:

    hpsum /romonly

    Results: All firmware components, which are required 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 firmware components, software components from the 7.90 PSP, cp008097.exe, and cp008257.exe were installed on Management Server1, Management Server2, and Management Server3.
     

    Return codes

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

    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 is not present, the software is current, or there is 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 is not present, the software is current, or there is 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 is successful. No reboot is required.
    1 The installation of the deliverable is successful. 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.
    • The supported hardware is not present, not enabled, or in a state that an installation could not be attempted.
    • The smart component does 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 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.

     

    Input files

    HP SUM provides the ability to script the update of multiple, individual targets or groups of targets (HP ProLiant and Integrity server and options) 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 a text editor. 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 perform dry runs of installations to ensure the scripts are working without deploying the firmware updates that might be required 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 SUM, add it as the inputfile <filename> parameter to a normal HP SUM 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 SUM executables. The <filename> 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 SUM command line using an input file is hpsum -inputfile <filename>. The input file itself can contain the same flags on the command line. The usual command line flags can still be used with the -inputfile flag, and takes precedence over any given input file. The <filename> field can be enclosed in double quotes to enable paths with spaces.

    Input file format and rules

    The input file is divided into two sections:


    File encoding

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

    Error reporting

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

    Input file parameters

    Parameter Description Possible values
    SILENT This parameter causes the installation to run silently without GUI or console output. All data is written to the log file. Any generated prompts use the default option and continue the installation without user input.

    If a component requires input before installation (such as configuration information), then the component installation fails (unless the IGNOREERRORS = "FailedDependencies" parameter is supplied), and an error message is written to the log file.

    YES, NO
    FORCEALL This parameter forces both firmware and software components. YES, NO
    FORCEROM This parameter forces updates to firmware components. YES, NO
    FORCESOFTWARE This parameter forces updates to software components. YES, NO
    FORCEBUNDLE This parameter enables you to override or downgrade an existing installation of components in the selected bundle. YES, NO
    DOWNGRADE This parameter enables you to downgrade to an earlier version of firmware for multi-target devices such as hard drives and array controllers. (Applies to firmware only.) YES, NO
    REWRITE This parameter enables you to rewrite the same version of firmware only for multi-target devices such as hard drives and array controllers. (Applies to firmware only.) YES, NO
    REBOOTALLOWED This parameter enables you to reboot, if required. YES, NO
    REBOOTMESSAGE This parameter enables you to create a message to be displayed prior to rebooting. Any string (not exceeding 256 characters)
    REBOOTDELAY This parameter enables you to delay before rebooting. Time in seconds
    COMPONENTSLIST This parameter enables you to limit the list of components to be updated. Component names with file extensions (.exe, .rpm, or .scexe)
    BUNDLESLIST This parameter enables you to limit the list of bundle xml files to be filtered. Bundle file names
    ALLOWUPDATEBUNDLE This parameter is a filter switch and enables you to install newer versions of components defined in a PSP, ISP, or bundle.
    This parameter enables these components to replace the older versions of the same component that might have shipped with the bundles.
    YES, NO
    SKIPTARGET This parameter defines the behavior when a remote target has an existing HP SUM session in progress.
    This parameter enables you to skip the host if an existing HP SUM session already exists. A NO overrides the session in progress and reinitializes the installation framework on the remote host.
    YES, NO
    IGNOREERRORS This parameter 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 parameter 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 parameter is a filter switch for use with bundles. The parameter enables you to use the latest version of the bundle when multiple versions of bundles are listed on the command line.
    If no bundles are specified on the command line, and multiple bundles are in the directory, then this parameter enables HP SUM to use the bundle with the latest version for installation.
    YES, NO
    DRYRUN This parameter 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.

    This parameter replaces the LSPOPTIONS parameter that was previously supported with LDU.

    One or more CLI switch
    USESNMP This parameter 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 parameter is used, and the /usewmi parameter is not used, the WMI components are optional. This parameter does not apply to HP Integrity Servers.
    YES, NO
    USEWMI This parameter specifies that components, which use WMI protocol, are available to be selected for installation.
    These components are optional by default and are not installed unless this parameter is used. When the /usewmi parameter is used, and the /usesnmp parameter is not used, the SNMP components are optional.
    YES, NO
    ROMONLY This parameter is a filter switch and allows the user to view only the firmware components required for installation.
    Do not use the /romonly parameter with the /softwareonly parameter.
    YES, NO
    SOFTWAREONLY This parameter is a filter switch and allows the user to view only the software components required for installation.
    Do not use the /softwareonly parameter with the /romonly parameter.
    YES, NO
    USECURRENTCREDENTIAL This parameter 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.)
    YES, NO
    WEBUPDATENEEDED This parameter enables you to instruct HP SUM to include the components from the HP FTP site (ftp://ftp.hp.com) in the list of possible updates. (This parameter does not apply to Integrity Servers.) YES, NO
    USEPROXYSERVER This parameter enables the inclusion of a proxy server (and port number) to access the HP FTP site (ftp://ftp.hp.com). (This parameter does not apply to Integrity Servers.) String value

    For example, 11.22.33.44:80

    USEPROXYSCRIPT This parameter enables the inclusion of a proxy script to access the HP FTP site (ftp://ftp.hp.com). (This parameter does not apply to Integrity Servers.) Web URL (for example, autoproxy.com)
    DELETEINPUTFILE This parameter enables you to instruct HP SUM to delete the input file after it has been read in. YES, NO (default)
    ONFAILEDDEPENDENCY This parameter 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 parameter 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 parameter is the active Onboard Administrator. When specifying the IP address, you can use either the IPv4 or IPv6 format.
    This parameter specifies an already defined group name in the HP SUM GUI.
    IP address, DNS name
    UID This parameter enables you to log in to the target hosts with your user ID. <username>
    PWD This parameter enables you to use the password for the user ID specified in the UID.
    The password is used to log in to target hosts.
    <password>
    LOGFILENAME This parameter enables you to set the name of the log file generated by HP SUM to something other than the default of /var/log/hppldu.log. The path must already exist or the log file remains the default file name. Log file name
    CMALOCALHOSTRWCOMMSTR This parameter enables you to specify an SNMP read/write community string for local host access. (Applies to Linux PSP only.) SNMP read/write community string
    CMALOCALHOSTROCOMMSTR This parameter enables you to specify an SNMP read-only community string for local host access. (Applies to Linux PSP only.) SNMP read-only community string
    CMAMGMTSTATIONRWIPORDNS This parameter enables you to specify the IP address or DNS host name of a system with read/write access to serve as a management station. You can specify multiple locations separated by a space. (Applies to Linux PSP only.) IP address, DNS name
    CMAMGMTSTATIONRWCOMMSTR This parameter enables you to specify an SNMP read/write community string for a system with read/write access that serves as a management station. You can specify multiple strings separated by a space. (Applies to Linux PSP only.) SNMP read/write community string
    CMAMGMTSTATIONROIPORDNS This parameter enables you to specify the IP address or DNS host name of a system with read-only access to serve as a management station. You can specify multiple locations separated by a space. (Applies to Linux PSP only.) IP address, DNS name
    CMAMGMTSTATIONROCOMMSTR This parameter enables you to specify an SNMP read/write community string for a system with read-only access that serves as a management station. You can specify multiple strings separated by a space. (Applies to Linux PSP only.) SNMP read/write community string
    CMADEFTRAPCOMMSTR This parameter enables you to set a default SNMP community string for traps. (Applies to Linux PSP only.) SNMP community string
    CMATRAPDESTINATIONCOMMSTR This parameter enables you to specify the SNMP destination trap community string. (Applies to Linux PSP only.) SNMP trap destination
    CMATRAPDESTINATIONIPORDNS This parameter enables you to specify the IP address or DNS host name of a server as a destination for SNMP traps, such as Systems Insight Manager. (Applies to Linux PSP only.) IP address, DNS name
    CMASYSCONTACT This parameter enables you to specify a person or phone number for administration of this system. (Applies to Linux PSP only.) String value
    CMASYSLOCATION This parameter enables you to designate the location of this system. (Applies to Linux PSP only.) String value
    CMASTARTWEBAGENT This parameter determines whether the HP Insight Systems Manager Web Agent is started when the health application loads. (Applies to Linux PSP only.)
    • YES (start the web agent)
    • NO (do not start the web agent)
    CMASTARTSTORAGEAGENT This parameter determines whether the HP Insight Systems Manager Storage Agent is started when the health application loads. (Applies to Linux PSP only.)
    • YES (start the storage agent)
    • NO (do not start the storage agent)
    CMANOTAINTEDKERNEL This parameter determines whether the HP Lights-Out management driver is started when the health application loads. (Applies to Linux PSP only.)
    • YES (start the HP Lights-Out management driver)
    • NO (do not start the HP Lights-Out management driver)
    HPVCAVCRMSERVER This parameter informs the VCA of the name of the VCRM to use as a software distribution repository. (Applies to Linux PSP only.) VCRM name
    HPVCAVCRMLOGINID This parameter is the login ID that the VCA uses to communicate with the VCRM. (Applies to Linux PSP only.) VCA login ID
    HPVCAVCRMLOGINPASSWD This parameter is the password for the login ID specified in the HPVCAVCRMLOGIN parameter. (Applies to Linux PSP only.) VCA login password
    ADMIN-GROUP This parameter is used by the HP Systems Management Homepage (hpsmh) to set up security for the web server. (Applies to Linux PSP only.) Up to five Linux groups, separated by spaces or semicolons, to enable administrative access to the web services.
    USER-GROUP This parameter is used by the HP Systems Management Homepage to set up security for the web server. (Applies to Linux PSP only.) Up to five Linux groups, separated by spaces or semicolons, to enable user-level access to the web servers.
    OPERATOR-GROUP This parameter is used by the HP Systems Management Homepage to set up security for the web server. (Applies to Linux PSP only.) Up to five Linux groups, separated by spaces or semicolons, to enable operator-level access to the web servers.
    ANONYMOUS-ACCESS This parameter determines whether an anonymous user can access the HP Systems Management Homepage. (Applies to Linux PSP only.) YES, NO (default)
    IP-BINDING This parameter is used by the HP Systems Management Homepage to determine whether hpsmh can use all available NICs and detect subnets for its web services. (Applies to Linux PSP only.) YES, NO (default)
    IP-BINDING-LIST This parameter is used by the HP Systems Management Homepage to restrict the NICs and subnets to use for its web servers.
    The IP-BINDING parameter must be set to yes for this parameter to be used during installation. (Applies to Linux PSP only.)
    IP address/NetMask pairs separated by semicolons (for example, 10.1.1.1/255.255.255.0;10.2.2.2/255.255.255.0)
    IP-RESTRICTED-LOGINS This parameter is used by the HP Systems Management Homepage to restrict login access. (Applies to Linux PSP only.) YES, NO (default)
    To enable restrictions on who can log in to the web server, this parameter must be set to yes, and values must be provided to the IP-RESTRICTED-EXCLUDE or IP-RESTRICTED-INCLUDE parameters.
    IP-RESTRICTED-EXCLUDE This parameter is used by the HP Systems Management Homepage to exclude specific IP address/NetMask pairs from logging into the web services. (Applies to Linux PSP only.)
    This parameter is ignored unless the IP-RESTRICTED-LOGINS parameter is set to yes.
    List of IP address ranges separated by semicolons (for example, 10.1.1.1-10.1.1.10;10.2.2.2-10.2.2.10)
    IP-RESTRICTED-INCLUDE This parameter is used by the HP Systems Management Homepage to enable login only from the IP address/NetMask pairs specified. (Applies to Linux PSP only.)
    This parameter is ignored unless the IP-RESTRICTED-LOGINS parameter is set to yes.
    List of IP address ranges separated by semicolons (for example, 10.1.1.1-10.1.1.10;10.2.2.2-10.2.2.10).
    LOCALACCESS-ENABLED This parameter is used by the HP Systems Management Homepage to determine whether to enable local anonymous access to the web services. (Applies to Linux PSP only.)
    • YES (default to include anonymous access)
    • NO
    LOCALACCESS-TYPE This parameter is used by the HP Systems Management Homepage to determine the type of access granted to local users. (Applies to Linux PSP only.)
    • Anonymous (default)
    • Administrator

    CAUTION: Selecting local access with administrator privileges as the login provides full access to any user with access to the local console, without prompting for a user name or password.
    TRUSTMODE This parameter is used by the HP Systems Management Homepage to set up the trust relationship mode. (Applies to Linux PSP only).
    • TrustByCert - If this value is used, the CERTLIST parameter must be defined to enable access to the server.
    • TrustByName - If this value is used, the XENAMELIST parameter must be defined.
    • TrustByAll - HP does not recommend using this value because of possible negative security consequences.
    CAUTION: The accepted values are case-sensitive and must be capitalized as shown. Failure to do so prevents the trust relationship from being set up properly during installation and might affect access to the web server.
    CERTLIST This parameter enables a user to provide a list of certificate files or servers where certificates can be obtained for trust relationships for the HP Systems Management Homepage. (Applies to Linux PSP only.) Certificate file name or Server DNS name
    XENAMELIST This parameter enables a user to provide a list of servers, separated by semicolons, for trust relationships for the HP Systems Management Homepage. (Applies to Linux PSP only.)
    This parameter is only valid if the TRUSTMODE parameter is set to TrustByName. (Applies to Linux PSP only.)
    Server DNS name
    HPQLA2X00FO This parameter is used by the hp_qla2x00 QLogic Fibre Channel Driver to determine the failover mode to use. (Applies to Linux PSP only.)
    • SinglePath
    • SecurePath
    • QLogicFailure
    (No default value)
    HPQLA2X00FORCE This parameter is used by the hp_qla2x00 QLogic Fibre Channel Driver to determine whether to skip detection of third-party storage. (Applies to Linux PSP only.) "Y", "N" (default)
    OAUID This parameter provides the username credentials for OA associated with VC. You must define a value of these variables before HOST variable in [TARGETS] section. This parameter only applies for VC firmware. User can define OAUID variable multiple times before each HOST variable.
    OAPWD This parameter provides the password credentials for OA associated with VC. You must define a value of these variables before HOST variable in [TARGETS] section. This parameter only applies for VC firmware. User can define OAPWD variable multiple times before each HOST variable.

    Examples of the HP SUM input file include:
    REBOOTALLOWED = YES
    REBOOTREQUIRED = NO
    REBOOTMESSAGE = "Server is going down for a reboot"
    REBOOTDELAY = 15
    COMPONENTSLIST = cp001234.exe, cp001235.exe
    BUNDLESLIST = bp001234.xml
    ALLOWUPDATEBUNDLE = YES
    SKIPTARGET = NO
    IGNOREERRORS = ServerNotFound, FailedDependencies
    SOURCEPATH = c:\pkgsource1
    USELATEST = YES
    SILENT = YES
    OPTIONS = /f:rom

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

    USAGE: hpsum /inputfile <path:\inputfile.txt>

    Examples of inputfile.txt file:

    Example 1: The two targets are passed to be updated. The targets do not necessarily have to be OAs. They can be any target supported by HP SUM.
    DRYRUN = YES
    SILENT = YES
    [TARGETS]
    HOST = BL465C-01
    HOST = 192.168.1.2
    [END]

    Example 2: A host DNS 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-8.70-0\hp\swpackages
    [GROUPS]
    HOST=winserver
    UID=Userid
    PWD=password
    [END]

    Example 4
    SILENT = YES
    IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies
    SKIPTARGET = NO
    SOURCEPATH = C:\ fwcd\firmware-8.70-0\hp\swpackages
    FORCEALL = YES
    REBOOTALLOWED = YES
    REBOOTDELAY = 30
    REBOOTMESSAGE = "Install complete, server will reboot in 30 seconds"
    [TARGETS]
    HOST=16.83.62.141
    UID=Userid
    PWD=password
    [END]
    [TARGETS]
    HOST=16.83.61.48
    UID=Userid
    PWD=password
    [END]
    [TARGETS]
    HOST=16.83.62.196
    UID=Userid
    PWD=password
    [END]
    [TARGETS]
    HOST=16.83.61.24
    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 (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.

    This argument is not supported on HP Integrity Servers.

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

    The reports are generated as an XML and HTML file which can be viewed in a web browser. The supported browsers for viewing the report files are Microsoft Internet Explorer 6.0 and Mozilla Firefox 3.5 and above. By default, the reports are located in the current working directory from where HP SUM was initiated. If that current location is write-protected, the reports are located in the same directory as the HP SUM log files.

    When generating the requested report, the HP SUM GUI does not appear. When the report is generated, HP SUM reports the location where the report files can be found.

    The following figure illustrates the HP SUM report in HTML format.

    The following figure illustrates the HP SUM Inventory report in HTML format.

    The following figure illustrates the HP SUM Firmware report in HTML format.


     

    Advanced topics


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

    Software component configuration

    Some components might have required or optional configuration settings. Configuration parameters can include information necessary to set up the component correctly or passwords required for software installed by the component. If the optional configuration data of a component is not provided and the component has not been installed previously, then default values for that configuration data are used. If the component has been previously installed and configured and no changes are made to the configuration data, then the existing configuration information is 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 on the Select Items to be Installed screen. 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

    This topic applies to ProLiant servers and options supported by the server, but does not apply to Integrity servers.

    HP SUM utility enables you to deploy firmware and software components simultaneously. The latest firmware and software components must be located in the same directory.

    To deploy firmware and software components simultaneously, select the location where the firmware and software components are located in the Source Selections screen. 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 (ftp://ftp.hp.com), you can deploy software and firmware components without using bundles.

    NOTE:Linux RPMs and Virtual Connect FW components are not available for download from ftp.hp.com using HP SUM 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 SUM, running in the context of a Windows PSP or ISP, supports server virtualization that runs on a Windows host. However, HP SUM, 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 SUM, 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.

    For Windows-based servers, 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, it copies a small service to the target server for the duration of the installation. After this service starts, HP Smart Update Manager uses this service to communicate between the local and remote target server. During this process, HP Smart Update Manager opens ports in the Windows firewall to enable HP Smart Update Manager to use SOAP calls over SSL to pass data among local and remote systems. These ports are defined in Enabling ports in HP Smart Update Manager. 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 then releases the share to the target server admin$ share.

    For Linux-based servers, 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, it copies a small service to the target server for the duration of the installation. After this service starts, HP Smart Update Manager uses this service to communicate between the local and remote target server. During this process, HP Smart Update Manager opens ports in the iptables firewall to enable HP Smart Update Manager to use SOAP calls over SSL to pass data between the local and remote systems. These ports are defined in Enabling ports used in HP Smart Update Manager. When 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 then closes the SSH connection to the target server.

    Configuring IPv6 for Windows Server 2003

    For information on setting up a Windows Server 2003 operating 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 enable file sharing connections over IPv6 networks. To make the 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 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. Windows Vista, when used as a client to run HP Smart Update Manager to remote Windows Server 2008 operating systems or as a target operating system on HP Workstation server blades, provides the infrastructure that supports full IPv6 deployment of software and firmware updates from HP Smart Update Manager.

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

    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 Windows 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 to the initiating Linux workstation. You can disable the Linux firewall to allow HP Smart Update Manager to work, but the Linux server becomes vulnerable to attack.

    For information on how to setup IPv6 in a Linux environment, 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. You can find the file on the distribution media for both Red Hat Enterprise Linux and Novell SUSE Linux Enterprise Server operating systems. HP Smart Update Manager uses this file to open a port in the IPv6 firewall to communicate with the Linux system that runs HP Smart Update Manager. Failure to install iptables-ipv6 results in HP Smart Update Manager reporting a discovery failure unless you disable the firewall.
     

    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 Linux RPMs or installing Linux 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 SUM is maximized
    Installation of components failed with 'Update returned an error' when installing Linux RPMs
    Issues related to bundle filtering on the Select Items to be Installed and Select Bundle Filter screens
    HP SUM fails on Vista due to McAfee firewalls
    Virtual Connect firmware upgrade using HP SUM fails if VC reports an invalid or bad health state

     

    Recovering from a failed ROM upgrade

    Recovering from a failed system ROM upgrade

    Use redundant ROM or ROMPaq to recover from a system ROM upgrade failure.

    Redundant ROM recovery

    When you flash the system ROM, ROMPaq writes over the backup ROM and saves the current ROM as a backup, enabling you to switch easily to the alternate ROM version if the new ROM becomes corrupted for any reason. This feature protects the existing ROM version, even if you experience a power failure while flashing the ROM.

    When the server boots, the server detects if the current ROM is corrupt. If a corrupt ROM is detected, then the system boots from the backup ROM and sends an alert 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, then 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 nonredundant 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.

    To manually set the server for ROMPaq disaster recovery:

    1. Power down the server.
    2. Remove the access panel.
    3. Set the system maintenance switch positions for disaster recovery. Switch positions are server-specific. For information about the correct settings for your server, see the server documentation.
    4. Insert a ROMPaq diskette with the latest system ROM from the HP Smart Update Firmware DVD or the HP website (http://www.hp.com/support).
    5. Install the access panel.
    6. Power up the server.
    7. Allow the system to boot completely.
    8. Repeat steps 1 and 2.
    9. Reset the system maintenance switch positions to the original settings.
    10. 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 iLO 2, 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.

    NOTE: To break out to a Linux console while booted to the HP Smart Update Firmware DVD, press Ctrl Alt d b x. Each key (d, b, x) is hit in succession. This command allows you to collect logs from the \tmp\hp_sum directory.

    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 files Function
    OpMan.trace Provides operations trace of the overall installation process.
    IPScout.trace Provides the information on whether the remote target might be contacted and the type of target found (iLO, server, VC, OA).
    OSScout.trace Provides 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.log Provides 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.log Provides 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.trace Provides 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.trace Provides 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 SUM Connection Error or Discovery Failed messages, follow these troubleshooting tips:


    HP SUM hangs during discovery

    If a system hang is observed during HP SUM discovery and the system is connected to external storage, in most cases disconnecting the external storage should resolve the issue.
     

    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.
     

    Recovering from a blocked program on Microsoft Windows


    Configuring Windows firewall settings

    The Windows Security Alert appears when a program is blocked from accepting connections from the Internet or a network.

    To set the rules for the Windows Firewall and Security Policy, click Unblock, and then set your firewall settings to the following:

    1. Click Start>Control Panel>Administrative Tools>Windows Firewall with Advanced Security>Inbound Rules>Remote Administration (NP-IN).
    2. Select Enabled, and then select Allow the connections.

    For Direct to iLO support, you must enable ping.
     

    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 and file 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 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 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 Description
    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 Description
    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 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 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 might specify a message to appear before the system shuts down during a reboot operation. When using a Japanese character set and running on a Japanese version of a Linux operating system, the message does not appear properly.

    Rebooting with the user-specified reboot message using a Japanese character set when running on a Windows operating system
    You might specify a message to appear before the system shuts down during a reboot operation. When using a Japanese character set and running on a Japanese version of a Windows operating system, the message causes the reboot not to occur automatically.
    For a successful reboot, you must click Exit. When the message is entered using CLI, the reboot message looks corrupted since the Japanese character set is not supported in CLI.
     

    Recovering from Fatal Error - application will exit message

    Running in a directory path containing double-byte characters

    When running in a directory path containing double-byte characters, the HP Smart Update Manager encounters a fatal error while trying to initialize.

    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


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

    NOTE: HP SUM is no longer supported on SUSE Enterprise Linux 9.

     

    Recovering a lost HP Smart Update Manager connection

    HP Smart Update Firmware DVD mounted using iLO virtual media

    When either iLO and NIC firmware are updated, the HP SUM connection is lost and cannot install components.

    Booting the Firmware DVD from iLO virtual media is only supported in Offline Automatic Firmware Update mode. Users attempting to boot in this manner might experience issues from connection timeouts, difficulties updating iLO firmware, and mouse syncing issues. If an access error exists, HP SUM cancels the installation.
     

    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.

    You can always copy HP Smart Update Manager to the target servers and execute using the local installation method.

    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


     

    HP SUM found new hardware message

    During the discovery progress, HP SUM might display the following pop-up message: Found New Hardware. This message appears because one of the self-discovery components is loading a new driver and the Windows operating systems discovers it as a new piece of hardware.

    Similar pop-up messages might occur with Windows 2008 operating systems when the Allow Non-bundle version option on the Select Bundle Filter screen is selected.
     

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

    If HP SUM reports non-matching systems error when trying to build source Linux RPMs or installing Linux RPMs built from source, then the operating system on the target server does not match the operating system from which you are running HP SUM in one of the following ways:


    Resolution options:
    1. Run HP SUM on the target server itself instead of remotely deploying HP SUM.
    2. Build the driver RPM locally and take the resulting RPM file from the standard location (for example, /usr/src/redhat/RPMS/i686/<driver>.rpm) and then copy it back into the HP SUM repository. HP SUM 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 might observe differences in the RPM component name which might appear to be a version mismatch for the component on the Select Item to be Installed screen and the Installation Results screen. This is caused by the RPM build phase. The resulting component is actually the same version. The RPM build adds information, so it is technically the same component.

    For example, if you select the component HP NC Series Mellanox 10GBE Driver for Linux on the Select Items to be Installed screen, it appears as hp-minx-en-1.4.3.1-1.src.rpm and on 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 No components found in the selected repository(ies)error appears when at least one space is in the path name of the repository containing the components to be installed.

    To resolve this issue, make sure no spaces are in the path name.
     

    Additional/Optional Actions columns are grayed when HP SUM is maximized

    If the Select Items to be Installed screen or Installation Results screen in HP SUM is maximized, the Additional column and sometimes the Optional Actions columns are grayed out.

    To resolve this issue, restore the screen to the original size.
     

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

    When installing any component, if the installation fails, then HP SUM displays Update returned an error message. To determine the installation failure, review the associated component log.

    However, when installing RPMs using HP SUM you might 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 multiple versions of source RPMs exist, the RPMs that are not the latest are not installed and Update not needed or Not Updated-already current messages are returned. HP SUM 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 SUM (for example, hpsum /b bp000690.xml), you might experience one or more of the following:

    If this issue occurs, from the GUI run HP SUM.
     

    HP SUM fails on Vista due to McAfee firewalls

    This is a known issue with McAfee that McAfee firewalls block HP SUM traffic. To resolve this issue, enable the port traffic associated with the HP SUM application by performing the following steps:

    1. From the system tray, click the McAfee icon.
    2. Select Manage Features.
    3. Select McAfee Host Intrusion Protection. As displayed in the following image, in the Message column, notice the entry similar to the following: Blocked Incoming TCP from the HOST (15.255.101.110) during execution of HP SUM.
    4. From the menu, select Task>Unlock Interface.
    5. Copy and then paste the following password: WObeQZGDCAG4
    6. NOTE: This password expires on April 7, 2011.

    7. Select the Firewall Policy tab.
    8. On the bottom of the screen, click Add.
    9. From the screen image, use the following settings for the new firewall rules on your system.
    10. Click OK to ensure new firewall rules have been implemented.

    11. Restart HP SUM. Performing the above steps does allow HP SUM to function, although after a period of time (ranging from minutes to hours), McAfee disables HP SUM access.


     

    Virtual Connect firmware upgrade using HP SUM fails if VC reports an invalid or bad health state

    Virtual Connect firmware can be upgraded using HP SUM only if the health state of the VC is in a good state. If the health state is invalid or bad, HP SUM does not upgrade the VC firmware.

    If a VC upgrade is attempted in an invalid or bad health state, HP SUM installation fails. The details of the failure can be viewed in the installation log by clicking the View Installation log link in the Additional section.

    Some of the VCSU Health Status bad states are:

    To resolve this issue, the VCSU must be used to upgrade the firmware.
     

    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, see the Microsoft website (http://www.microsoft.com).

    For information about Linux operating systems, see one of the following websites:

    HP contact information

    For the name of the nearest HP authorized reseller:

    For HP technical support:


     

    Acronyms and abbreviations

    BMC
    Baseboard Management Controller
    CLI
    Command Line Interface
    CPLD
    complex programmable logic device
    FPGA
    Field Programmable Gate Array
    GUI
    graphical user interface
    HBA
    host bus adapter
    HP SUM
    HP Smart Update Manager
    I/O
    input/output
    iLO
    Integrated Lights-Out
    iLO 2
    Integrated Lights-Out 2
    iLO 3
    Integrated Lights-Out 3
    ISP
    Integrity Support Pack
    LDU
    Linux Deployment Utility
    NIC
    network interface controller
    OA
    Onboard Administrator
    POST
    Power-On Self Test
    PSP
    HP ProLiant Support Pack
    RBSU
    ROM-Based Setup Utility
    RDP
    Rapid Deployment Pack
    RILOE II
    Remote Insight Lights-Out Edition II
    SAN
    storage area network
    SAS
    serial attached SCSI
    SCSI
    small computer system interface
    SEP
    Symantec Endpoint Protection
    SNMP
    Simple Network Management Protocol
    SOAP
    Simple Object Access Protocol
    SPLD
    System Programmable Logic Device
    SSH
    Secure Shell
    SSL
    Secure Sockets Layer
    TPM
    trusted platform module
    VC
    Virtual Connect
    VCA
    Version Control Agent
    VCM
    Virtual Connect Manager
    VCRM
    Version Control Repository Manager
    VCSU
    Virtual Connect Support Utility
    VLAN
    virtual local area network
    WMI
    Windows Management Instrumentation