HP Integrity rx2800, Smart Update Manager User Manual

HP Smart Update Manager

Part Number 613175-003

User Guide

August 2010 (Third Edition)

© Copyright 2009, 2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express

warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license.

Microsoft, Windows, Windows Server, Windows XP, and Windows Vista are U.S. registered trademarks of Microsoft Corporation. AMD is a trademark of Advanced Micro Devices, Inc. Intel is a trademark of Intel Corporation in the U.S. and other countries.

Intended audience

This guide is intended for individuals who are familiar with the configuration and operation of Microsoft® Windows®, Windows Server® 2003, Windows Server® 2008, Linux, smart components, and deployment of firmware and software to systems and options. Because of the risk of data loss, only individuals experienced with using firmware and software should implement the procedures in this guide.

Contents

Introduction .................................................................................................................................. 6

HP Smart Update Manager overview ........................................................................................................... 6

Using this guide ........................................................................................................................................ 7

New features of HP SUM 4.1.0 .................................................................................................................. 7

Minimum requirements ............................................................................................................................... 7

Minimum requirements for Windows servers ....................................................................................... 7

Minimum requirements for Linux x86 servers ....................................................................................... 8

Supported deliverables overview ............................................................................................................... 11

Obtaining the HP SUM utility .......................................................................................................... 11

Support and limitations of HP SUM .................................................................................................. 11

Deployment from HP SUM ........................................................................................................................ 12

Executing HP SUM ......................................................................................................................... 12

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

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

Deploying software using the ProLiant Support Pack for Linux .............................................................. 15

Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD ................................ 16

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

Bundles ........................................................................................................................................ 23

HP SUM User Interface ................................................................................................................ 24

Deployment scenarios .............................................................................................................................. 24

Graphical deployment on a local host .............................................................................................. 24

Scripted deployment on a local host ................................................................................................ 24

Deployment to multiple remote hosts ................................................................................................. 25

Keyboard support.................................................................................................................................... 25

Local host installations .............................................................................................................................. 26

Selecting the location to check for updates ........................................................................................ 26

Download Permission (applicable only for ProLiant servers) ................................................................. 29

Selecting an installation host ........................................................................................................... 30

Selecting bundles to filter ................................................................................................................ 32

Selecting components to install ........................................................................................................ 34

Component selection pane ............................................................................................................. 38

Viewing the installation results ......................................................................................................... 43

Multiple-host installations .......................................................................................................................... 45

Selecting remote hosts or groups ..................................................................................................... 46

Searching for remote hosts .............................................................................................................. 47

Managing hosts ............................................................................................................................ 47

Managing groups .......................................................................................................................... 51

Entering credentials for hosts ........................................................................................................... 54

Selecting bundles to filter on multiple hosts ........................................................................................ 58

Selecting components to install on multiple hosts ................................................................................ 59

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

Viewing the installation results for multiple hosts ................................................................................ 63

Scripted deployment ................................................................................................................... 65

Command-line interface ........................................................................................................................... 65

Command-line syntax ..................................................................................................................... 65

Command-line arguments ............................................................................................................... 66

Component configuration for Windows components only ................................................................... 71

Command-line examples ................................................................................................................ 71

Return codes ................................................................................................................................. 73

Windows smart component return codes .......................................................................................... 73

Linux smart component return codes ................................................................................................. 74

Linux RPM return codes .................................................................................................................. 74

Input files ............................................................................................................................................... 74

Command-line usage of input file ..................................................................................................... 75

Input file format and rules ............................................................................................................... 75

File encoding ................................................................................................................................ 76

Error reporting .............................................................................................................................. 76

Input file parameters ...................................................................................................................... 76

Reports .................................................................................................................................................. 85

Advanced topics ......................................................................................................................... 90

Software component configuration ............................................................................................................ 90

Deploying firmware and software simultaneously......................................................................................... 91

Server virtualization detection and support ................................................................................................. 91

Configuring IPv6 networks with HP Smart Update Manager .......................................................................... 91

Configuring IPv6 for Windows Server 2003 ..................................................................................... 92

Configuring IPv6 for Windows Server 2008 ..................................................................................... 93

Configuring IPv6 for Linux............................................................................................................... 95

Troubleshooting .......................................................................................................................... 98

Recovering from a failed ROM upgrade ..................................................................................................... 98

Recovering from a failed system ROM upgrade ................................................................................. 98

Recovering from a failed option ROM upgrade ................................................................................. 99

Recovering from an installation failure ...................................................................................................... 100

Collecting trace directories ........................................................................................................... 100

Recovering from a discovery failure ......................................................................................................... 101

Troubleshooting connection errors ................................................................................................. 101

HP SUM hangs during discovery ................................................................................................... 102

Recovering from a loss of Linux remote functionality ................................................................................... 102

Configuring firewall settings .......................................................................................................... 102

Recovering from a blocked program on Microsoft Windows ....................................................................... 103

Configuring Windows firewall settings ........................................................................................... 103

Enabling ports in HP Smart Update Manager .................................................................................. 103

Recovering from operating system limitations when using a Japanese character set ........................................ 105

Displaying the user-specified reboot message using a Japanese character set when running on a Linux

operating system ......................................................................................................................... 105

Rebooting with the user-specified reboot message using a Japanese character set when running on a

Windows operating system ........................................................................................................... 105

Recovering from Fatal Error - application will exit message ......................................................................... 106

Running in a directory path containing double-byte characters .......................................................... 106

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

Running HP Smart Update Manager on SUSE LINUX Enterprise Server 9 ............................................ 106

Recovering a lost HP Smart Update Manager connection ........................................................................... 107

HP Smart Update Firmware DVD mounted using iLO virtual media ..................................................... 107

Troubleshooting HP Smart Update Manager in IPv6 networks...................................................................... 107

Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2003 environment ...................... 107

Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2008 environment ...................... 108

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

HP SUM found new hardware message ................................................................................................... 109

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

........................................................................................................................................................... 109

Linux component version discrepancy for source RPMs ............................................................................... 110

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

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

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

Issues related to bundle filtering on the Select Items to be Installed and Select Bundle Filter screens .................. 111

HP SUM fails on Windows Vista® due to McAfee firewalls ........................................................................ 112

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

Technical support ...................................................................................................................... 117

Reference documentation ....................................................................................................................... 117

Operating system information ................................................................................................................. 118

HP contact information ........................................................................................................................... 118

Acronyms and abbreviations ...................................................................................................... 119

Index ....................................................................................................................................... 122

Introduction

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:

• Deployment of firmware for single or one-to-many HP servers and network-based targets such as

iLOs, OAs, and VC Ethernet and Fibre Channel modules.

• Deployment of software for single or one-to-many HP ProLiant servers (supported in Windows® and

Linux environments) and HP Integrity servers (supported in Windows® environments).

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

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.

firmware using HP SUM only applies to BL860c/BL870c/BL890c i2 Servers.

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:

• Dependency checking, which ensures appropriate installation order and dependency checking

between components

• Intelligent deployment deploys only required updates

• Simultaneous firmware and software deployment for multiple remote targets in both GUI and CLI

modes (ProLiant servers and options only)

• Improved deployment performance

• Local or remote (one-to-many) online deployment

• Local offline firmware deployments with the earlier HP Firmware Maintenance CD or the HP Smart

Firmware Update DVD for ProLiant servers and options

• Remote offline deployment when used with the SmartStart Scripting Toolkit or iLO Virtual Media

• GUI- or CLI-scriptable with extensive logging

• Remote command-line deployment

Introduction 6

• Support for updating firmware on network-based targets such as the OA, iLO 2/iLO 3 through

Network Management Port, and VC Ethernet and Fibre Channel modules on HP ProLiant servers

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 after 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 (on page 11) section.

New features of HP SUM 4.1.0

This release of HP SUM includes the following new support:

• Updated support for Virtual Connect FW deployment for VC firmware 3.x and later

NOTE: HP recommends using VCSU to deploy VC firmware v2.3x and earlier.

• New CLI and input file parameters for Virtual Connect

o CLI—oa_username and oa_password o Input file parameters—OAUID and OAPWD

• Added support for online deployment of HP 3 Gb SAS BL Switch Firmware

• Added Host Search options on the Select Installation Host(s) screen

Minimum requirements

• Minimum requirements for Windows operating systems ("Minimum requirements for Windows

servers" on page 7)

• Minimum requirements for Linux ("Minimum requirements for Linux x86 servers" on page 8)

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:

Introduction 7

• A local administrative system with 512 MB of memory

• Sufficient hard-drive space of at least twice the file size of the components to be deployed

• WMI enabled

• All remote host servers connected to the same network and use TCP/IP to enable the systems to be

seen by the administrative system

• An account with administrator privileges on each host server

HP recommends that the user name and password for the administrator account on each host server are the same as those on the local administrative system. If administrator privileges are not set up in this manner, you must have the user name and password for each remote server available. Alternatively, you can use a domain account on the local administrative system that has administrator privileges on the host servers.

• The beginning and ending IP addresses entered for the range of hosts (targets) must be on the same

subnet.

• To install firmware on HP Integrity BL860c/BL870c/BL890c i2 Servers, you must run HP SUM from

an x86 or x86 Linux machine. You cannot deploy firmware on a Windows Integrity system from a Windows Integrity system.

NOTE: HP Smart Update Manager requires a true Administrator login and not an elevated

RUN AS Administrator. If you are unable to perform the net use * \\server\ADMIN$ for Microsoft Windows® target servers, you do not have sufficient privileges to run HP Smart

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=SupportManu

al&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=18964&prodSeriesId=345557).

Update Manager.

NOTE: When attempting to use the remote deployment functionality of HP SUM on any

edition of Windows Server® 2008 or Windows Vista®, you must ensure that the File and Print Services feature is enabled and that the File and Print Services exception has been enabled in the Windows® firewall. Failure to do so prevents HP SUM from deploying remote Windows® target servers.

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 Integrity Server site (http://www.hp.com/go/integrity_servers-docs

For more information about HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers, see the HP Integrity and HP 9000 firmware update options on the HP website (http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=c003

99523&jumpid=reg_R1002_USEN).

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

• A local administrative system with 512 MB of memory

• glibc 2.2.4-26 or later

), or by server model number, see the HP

Introduction 8

• gawk 3.1.0-3 or later

• sed 3.02-10 or later

• pciutils-2.1.8-25.i386.rpm or later

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

• tcl-8.x package

• expect-5.x package

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

• For Red Hat Enterprise Linux 4x86 servers:

o compat-libstdc++-296-2.96-132.7.2.i386 or later o lm_sensors-2.8.7-2.i386 or later o net-snmp-5.1.2-11.i386 or later o perl (required to provide the libperl.so) o libnl (required for QLogic and Emulex drivers)

• For Red Hat Enterprise Linux 4 AMD64/EM64T servers:

o compat-libstdc++-296-2.96-132.7.2.i386 or later o lm_sensors-2.8.7-2.x86_64 or later o net-snmp-5.1.2-11.x86_64 or later o perl (required to provide the libperl.so) o libnl (required for QLogic and Emulex drivers)

• For Red Hat Enterprise Linux 5 x86 servers:

o compat-libstdc++-2.96-2.96-132.7.2.i386 or later o lm_sensors-2...7-2.i386 or later o net-snmp-5.3.1-14.e15.i386 or later o perl (required to provide the libperl.so) o libnl (required for QLogic and Emulex drivers)

• For Red Hat Enterprise Linux 5 AMD64/EM64T servers:

o compat-libstdc++-296-2.96-132.7.2.i386 or later o lm_sensors-2.8.7-2.x86_64 or later o net-snmp-5.3.1-14.e15.x86_64 or later o perl (required to provide the libperl.so) o libnl (required for QLogic and Emulex drivers)

• For SLES 10 x86 servers:

o compat-2006.1.25-11.2.i586 or later o compat-libstdc++-5.0.7-22.2.i586 or later o perl (required to provide the libperl.so) o libnl (required for QLogic and Emulex drivers)

Introduction 9

• For SLES 10 AMD64/EM64T servers:

yast2

o compat-2006.1.25-11.2.x86_64 or later o compat-32bit-2006.1.25-11.2.x86_64 or later o compat-libstdc++-5.0.7-22.2.x86_64 or later o perl (required to provide the libperl.so) o libnl (required for QLogic and Emulex drivers) o e2fsprogs-32bit

• For SLES 11 x86 servers:

o perl (required to provide the libperl.so) o libstdc++33-3.3.3-11.9.i586 or later o perl-SNMP-5.4.2.1-6.3.i586 or later o net-snmp-5.4.2.1-6.3.i586 or later o libnl (required for QLogic and Emulex drivers)

• For SLES 11 AMD64/EM64T servers:

o glib-1.2.10-15.i386 or later o libstdc++33-32bit-3.3.3-11.9 or later o perl-SNMP-5.4.2.1-6-3.x86_64 or later o net-snmp-5.4.2.1-6.3.x86_64 or later o libnl (required for QLogic and Emulex drivers)

You must have the following RPMs, required only on the local Linux system running HP SUM to perform builds of NIC source RPMs:

o gcc-2.96-108.1 or later o kernel-devel (This RPM is required for Red Hat Enterprise Linux 5.x. Install the kernel-devel in

addition to any kernel-specific devel package such as kernel-xen-devel or kernel-PAE-devel.)

o kernel-syms o RPM build tools

In addition, components that are compiled from source code (such as NIC drivers) require the presence of the following build tools:

• gcc-2.96-108.1 or later

• cpp-2.96-108.1 or later

• binutils-2.11.90.0.8 or later

• glibc-devel-2.2.4-26 or later

• kernel-headers-<_version_> (The version number depends on which kernel is used.)

NOTE: To perform Linux deployments, a root equivalent user account must be used. SSH

support must be enabled and firewall opened to enable SSH communications on remote Linux servers or HP SUM is not able to deploy updates. By default, SUSE LINUX Enterprise Server 10 and 11 block SSH support through the firewall. If SSH support has been disabled in the firewall, to enable it and open ports, use the

command.

Introduction 10

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

•

IMPORTANT: The HP Smart Update Manager does not support cross-platform deployments

(for example, deployments from Linux systems to Windows® systems).

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 ("Obtaining the HP SUM

utility" on page 11, "Support and limitations of HP SUM" on page 11) of that version of HP

Obtaining the HP SUM utility

The HP SUM utility is available from the following:

SUM to determine if it has the features that you need.

• HP ProLiant Support Packs for Windows® 7.90 and later

• HP ProLiant Support Packs for Linux 8.40 and later

• HP Smart Update Firmware DVD (for HP ProLiant servers)

• HP Integrity Support Pack for Windows® 6.00 and later on Itanium®-based systems

• HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundle for Linux

• HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundle for Windows®

CAUTION: Use the version of HP SUM that comes with the Integrity Support Pack or Integrity

Bundle when deploying the components that are included in that deliverable.

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

3.7.1

4.0.0 For ProLiant servers:

Delivered with Support and limitations

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 No support for BL860c/BL870c/BL890c i2

HP ProLiant Support Pack for

Windows® 8.40

Servers firmware or Integrity Support Pack

Introduction 11

•

HP SUM

Delivered with Support and limitations

version

HP ProLiant Support Pack for Linux

8.40

HP Smart Update Firmware DVD 9.0

For ProLiant Workstation Blades:

HP Workstation Support Pack for

Windows for HP WS460c G6 Blade

HP Smart Update Firmware DVD 9.0

(offline only)

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

4.0.2

4.1.0

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

HP Smart Update Firmware DVD 9.10 • No support for BL860c/BL870c/BL890c i2

Servers firmware or HP Integrity Support Pack

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

Executing HP SUM

The following sections discuss deployment from HP SUM.

HP SUM provides three modes of execution for users:

• GUI—For firmware and software deployments

• Express—For software deployments only (local host only)

• Scripted—For firmware and software deployments running silently

HP SUM enables you to deploy to both local and remote deployments. HP SUM can run in both standard Windows® and Linux operating systems in online mode and in offline mode (available on HP Smart Update Firmware DVD) through special boot environments based on Linux boot kernels as long as the prerequisites are met.

Use the following table to determine the correct execution mode for the server use case.

Introduction 12

•

IMPORTANT: Before deploying software updates to a target server, be sure that a recent

backup of the target server is available in the event the deployment procedure fails.

Scenario Description HP SUM command HP deliverable

Interactive, graphical deployment on a local host (Run HP SUM on the server being updated.)

Use this scenario when you:

Are not familiar with

command line tools

Are deploying

components on a local, single host

Do not require

scripting

Windows®:

hpsum

Linux:

./hpsum

Online:

HP ProLiant Support Pack for Windows® and Linux

or Smart Update Firmware

DVD

Offline:

Smart Update Firmware DVD

Want to select the

components to be installed

Scripted deployment on a local host (Run HP SUM from a network share on a local server.)

Interactive, graphical deployment to a remote host (Run HP SUM from a workstation and update remote hosts over the network using the GUI)

Use this scenario when you:

Are familiar with

command line tools

Are deploying

components on a local, single host

Must perform a

customized, scripted deployment

Are unable to unlock

the required HP SUM network ports for remote deployment

Use this scenario when you:

Are not familiar with

command line tools

Do not require

scripting

Want to select the

components to be installed

Need to update

multiple targets including OA, VC, and server-based firmware

Need to select

individual firmware to update

Need to select

individual hardware devices to be updated

Windows®:

hpsum -s

Linux:

./hpsum -s

Windows®:

hpsum

Linux:

./hpsum Targets can be a

server, OA, iLO, or VC IP address or DNS name.

Online:

HP ProLiant Support Pack for Windows® and Linux

or Smart Update Firmware

DVD or HP Integrity Support Pack

for Windows

Offline:

None

Online:

HP ProLiant Support Pack for Windows and Linux

or Smart Update Firmware

DVD or HP Integrity Support Pack

for Windows or HP Integrity

BL860c/BL870c/BL890c i2 Servers Bundles for Windows® and Linux

Offline:

None

Introduction 13

•

Scenario Description HP SUM command HP deliverable

Scripted deployment to a remote host

(Run HP SUM from a workstation and update a remote host over the network using scripts.)

Use this scenario when you:

Are familiar with

command line tools

Must perform a

customized, scripted deployment

Need to update

multiple targets including OA, VC, and server-based firmware

Need to update all

enclosure firmware

Windows®:

hpsum -s target Target1

-target Target2

-username User1

-password PW1

Linux:

./hpsum -s target Target1

-target Target2

-username User1

-password PW1

Online:

HP ProLiant Support Pack for Windows® and Linux

or Smart Update Firmware

DVD or HP Integrity Support Pack

for Windows or HP Integrity

BL860c/BL870c/BL890c i2 Servers Bundles for Windows® and Linux

Offline:

None*

Automatic Deployment to one or more servers in a HP BladeSystem enclosure

(use the HP Smart Update Firmware DVD with embedded HP SUM to deploy firmware updates to one or more blades)

Use this scenario when you:

Do not have an

operating system installed on a server blade

Want an automatic

way to deploy firmware updates

Do not require log

files or user interaction with the installation process

The HP Smart Update Firmware DVD takes care of this automatically

Online:

None

Offline:

HP Smart Update Firmware DVD

Want to update

multiple blades in an enclosure in a single operation

Update an existing enclosure manually

For more information, see BladeSystem Matrix compatibility chart at www.hp.com/go/matrix compatibility (http://www.hp.com/g

o/matrixcompatibility)

The same scenario as shown in the “Interactive, graphical deployment to a remote host” or “Scripted deployment to a remote host” scenarios discussed previously in this table

Windows®:

hpsum

Linux:

./hpsum

Online:

HP BladeSystem Firmware Update Bundles for Windows® and Linux

or HP Smart Update Firmware

DVD

Offline:

HP Smart Update Firmware DVD

Introduction 14

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 (on page 91)".

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

), or by server model number, see the HP

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

Introduction 15

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.

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

• In offline mode, the HP Smart Update Firmware DVD boots a small Linux kernel and enables

firmware updates to occur on a single server using the HP SUM software.

• In online mode, users can leverage the autorun utility to launch HP SUM or browse the DVD to the

\hp\swpackages directory and execute it directly.

All firmware smart components are placed in the \hp\swpackages directory for use by HP SUM. If additional firmware smart components are 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

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.

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.

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.

Introduction 16

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=SupportManu

al&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

Component Supported

HP ProLiant ML/DL/SL series System ROM Yes

HP Workstation WS460c G6 Blade ROM Yes, offline only

HP ProLiant Blade Servers ROM Yes

HP ProLiant 100-series Servers ROM Yes

iLO 2 firmware Yes, local and remote

iLO 3 firmware3 Yes, local and remote

LO-100 firmware3 Yes

Broadcom NIC firmware Yes

Intel® NIC firmware No

QLogic NIC firmware Yes, offline only

Mellanox NIC firmware Yes

Power Management Controller firmware Yes

Smart Array Controller firmware Yes

SAS and SATA hard drive firmware behind Smart Array controllers

SAS and SATA hard drive firmware behind non-Smart Array controllers

Emulex, QLogic, and Brocade Fibre Channel Host Bus Adapter firmware

Tape blade firmware Yes

Virtual Connect firmware1 Yes, online only

HP StorageWorks 600 Modular Disk System (MDS600)2 Yes, offline only

HP 3Gb SAS BL Switch firmware Yes, online only

Onboard Administrator Firmware4 Yes, online only

Yes

Yes, offline only

Introduction 17

Component Supported

CPLD/SPLD5 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 (http://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

IMPORTANT: After flashing the CPLD/SPLD, you must cycle power for the changes to take

). Run HP SUM and deploy the CPLD/SPLD component.

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.

Introduction 18

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 (http://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.

umount /dev/cdrom umount /dev/sda1

12. Remove the USB key and DVD.

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.

Introduction 19

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

2. Copy any updated files into the same directory where the files were copied in step 1.

privileges.

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

• The user does not temporarily disable BitLocker before flashing the System BIOS when using the

Microsoft BitLocker Drive Encryption.

• The user has optionally selected to measure iLO, Smart Array, and NIC firmware.

Introduction 20

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.

Introduction 21

Close all the windows, and then start the firmware update.

To enable advanced startup options, use the following command: cscript manage-bde.wsf -protectors -disable c:

When the firmware update process is completed, the BitLocker Drive Encryption support can be reenabled by following steps 1 through 4 but clicking Enabled in step 5 instead. The following command can be used to re-enable BitLocker Drive Encryption after firmware deployment has completed.

cscript manage-bde.wsf -protectors -enable c:

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.

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.

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.

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.

A pop-up warning message appears. After OK is selected, you can continue. The installation is not canceled.

Introduction 22

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

The installation occurs. installation is silent, and the /tpmbypass switch is supplied.

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 ("Obtaining the HP SUM utility" on page

11, "Support and limitations of HP SUM" on page 11)".

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:

• You must specify the IP address of the iLO-3 MP on the server as the target to be updated.

• On the Select Items to be Installed screen, you must choose whether you want to Upload and

Activate or Upload but Do Not Activate. If you choose not to activate immediately, the firmware is only updated when the server is rebooted.

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

Introduction 23

HP SUM User Interface

•

Deployment scenarios

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

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

Scenario Used when

Graphical deployment on a local host

Scripted deployment on a local host

Graphical deployment to a remote host

Scripted deployment to a remote host

Are not familiar with command line tools. Are deploying components on a local, single host. Do not require scripting.

Are familiar with command line tools. Are deploying components on a local, single host. Must perform a customized, scripted deployment.

Are not familiar with command line tools. Are deploying components on one or more remote hosts. Do not require scripting.

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 (on page 7)."

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 (on page

26)."

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 (on page 7)."

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 (on page 65)" for more

information.

4. Execute the script.

HP SUM User Interface 24

Deployment to multiple remote hosts

NOTE: A remote host can be the IP address or DNS name of a remote server, remote iLO

NIC port, Virtual Connect Ethernet or Fibre Channel Module for c-Class BladeSystem,

To deploy components to multiple remote hosts using the GUI:

1. Ensure that all minimum requirements are met as described in "Minimum requirements (on page 7)."

2. Ensure that the components to be deployed are accessible to the administrative system.

BladeSystem Onboard Administrator, or 3 Gb SAS BL Switch firmware.

For more information about performing the deployment using the graphical interface, see "Multiple-host installations using the GUI ("Multiple-host installations" on page 45)."

To deploy components to multiple remote hosts using the CLI:

1. Ensure that all minimum requirements are met as described in "Minimum requirements (on page 7)."

2. Ensure that the components to be deployed are accessible to the administrative system.

3. Create a script to customize the deployment. For more information, see "Scripted deployment (on

page 65)."

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.

• Depending on the operating system, you must press ALT to see the task corresponding to the

underlined letter.

• The accelerator keys work by pressing ALT + the underlined letter.

• Press Space to select items such as hosts or groups.

• Press Tab to select from a list, and then press the arrow keys to toggle radio buttons.

HP SUM User Interface 25

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

Selecting the location to check for updates

HP Smart Update Manager, see Deployment Options.

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.

HP SUM User Interface 26

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:

• Directory—This field enables you to select the directory where the components you want to deploy

are located. It can be located on a locally accessible file system. The default location is the directory from where HP SUM is executed. To change the directory value, click Browse to launch a selectdirectory menu. To set the field back to the initial value, click Default.

• Check ftp.hp.com—(Only for HP ProLiant servers) Select this checkbox to get firmware and software

components located on the HP FTP site (ftp://ftp.hp.com of the firmware and software components available from HP. The components, which are applicable (denoted with an HP.com icon) are available for selection on the Select Items to be Installed screen. When using this method, both firmware and software components are available for selection depending on the options set on the Set Bundle Filter screen when PSPs or bundles are included in the components to be deployed. To limit only the appearance of available firmware components, use the /romonly command-line argument and use the /softwareonly command line argument for software components. The components are not downloaded from the HP FTP site to a target until the Install button is actually selected unless the component is required to discover supported devices. If components are required for discovery, then you are prompted to allow this action. If components are already up-to-date, the components do not appear.

o The Check ftp.hp.com (only for ProLiant servers and select options) checkbox is cleared by

default. To receive updates from the web, select the Check ftp.hp.com checkbox. To use a proxy server and enable the proxy details group box, select the Use Proxy Server checkbox.

o Proxy Details—Enter the proxy information in the Proxy Details group box to be used to access

the HP FTP site. To auto-detect the proxy information, click Detect Proxy. If you use a proxy server in accessing the HP FTP site, the proxy information is saved and prepopulated on the next deployment.

NOTE: HP SUM does not support FTP over HTTP proxy.

). The HP FTP site contains the latest versions

HP SUM User Interface 27

NOTE: FTP downloaded from HTTP proxy fails. Components from the HP FTP site are only

presented for selection on the Select Items to Install screen if their versions are newer than what is already on the system. If a system has all of the latest versions of firmware and software, no components from HP.com are presented on the Select Items to be Installed screen.

NOTE: HP SUM does not support the ability to download the latest Linux RPMs and Virtual

Connect components from ftp.hp.com for ProLiant servers.

NOTE: HP SUM does not support the ability to download the latest components from

ftp.hp.com to HP Integrity servers.

• Include components previously downloaded from HP.com—This option includes the components that

have been previously downloaded from the HP FTP site as available for selection on the Select Items to be Installed screen. The default location for the previously downloaded components is %TEMP%\hp_sum\RepositoryManager\Repxx\<component_number> directory. To use components already downloaded from the HP website, select this checkbox.

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

HP SUM User Interface 28

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:

• Select All—Selects all available components for download.

• Clear All—Clears all components selected for download.

• Cancel—Exits the Download Permission screen and returns to the Source Selections screen.

• OK—Downloads all selected components.

NOTE: Emulex HBAs, QLogic HBAs, Brocade HBAs, and offline-only components cannot be

retrieved from the HP website and can only be installed offline. These components do not

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

appear on the web components list.

HP SUM User Interface 29

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 (on page 45)".

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

• Host Name—Displays the host IP address or DNS name.

• Type—Categorizes the system as a host or group.

• Last Used—Enables you to sort the list by the most recently used hosts.

• Description—Displays the user-defined description given to a host.

When the Remote Host or Group option on the Select Installation Host(s) screen is selected, you can sort your view of the host list by selecting Only Hosts, Only Groups, or Both.

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

• Host Search—Enables you to search for remote hosts using the following options:

HP SUM User Interface 30

+ 94 hidden pages

HP Integrity rx2800, Smart Update Manager User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual