HP Smart Update Manager Release NotesVersion 6.0.0

HP Part Number: 679985-007Published: September 2013Edition: 1

© Copyright 2012, 2013 Hewlett-Packard Development Company, L.P.

Open source software

• OpenPegasus version 2.10.0

For more information, see the OpenPegasus website at http://www.OpenPegasus.org.

• Mongoose version 2.11

For more information, see the Mongoose website at http://sourceforge.net/projects/mongoose/develop.

• open-WSMan

For more information, see the open-WSMan website at http://sourceforge.net/projects/openwsman.

• zlib version 1.2.3

For more information, see the zlib website at http://zlib.net.

• libcurl version 7.21.6

For more information, see the libcurl website at http://curl.haxx.se/libcurl.

• gSOAP version 2.8.3

For more information, see the gSOAP website at http://gsoap2.sourceforge.net.

• libssh2 version 1.2.8

For more information, see the libssh2 website at http://www.libssh2.org.

• libxml2 version 2.7.8

For more information, see the libxml2 website at http://www.xmlsoft.org.

• libxslt version 1.1.26

For more information, see the libxslt website at http://www.xmlsoft.org.

• OpenSSL version 1.0.0d

For more information, see the OpenSSL website at http://www.openssl.org

• Cygwin libraries

. For more information, see http://cygwin.com/index.html.

• Genisoimage

For more information, see http://cdrkit.org/.

Version6.0.0

DescriptionHP SUM is a technology you can use to update firmware and software on HP ProLiant servers, andfirmware on HP Integrity servers. The latest version of HP SUM is available on the HP website at http://www.hp.com/go/hpsum.

NOTE: HP SUM can update some firmware for VMware vSphere 5.x and later.

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 asiLO, OA, and VC Ethernet and Fibre Channel modules.

• Deployment of drivers, agents, and tools for single or one-to-many HP ProLiant servers (supportedin Windows and Linux environments).

Operating systems and devices

Prerequisites

IMPORTANT: Before deploying any components to a system, be sure that a recent backup of thesystem is available in the event the deployment procedure fails.

Enable the network ports that HP SUM uses. For more information, see “Network ports used by HPSUM” (page 4).

HP SUM runs on

• Windows 2008 (and variants)

• Windows 2012 (and variants)

• Red Hat Enterprise Linux 5.x

• Red Hat Enterprise Linux 6.x

• SUSE Linux Enterprise Server 10.x

• SUSE Linux Enterprise Server 11.x

HP SUM deploys to

• Windows 2008 (and variants)

• Windows 2012 (and variants)

• Red Hat Enterprise Linux 5.x

• Red Hat Enterprise Linux 6.x

• SUSE Linux Enterprise Server 10.x

• SUSE Linux Enterprise Server 11.x

• HP-UX iv3 1109 or higher

• VMware ESX-I (requires WBEM provider from HP)

• OA, VC, iLO, c-Class Switches, SAN Switches, iPDU

Description 3

VMware ESXi operating systemsYou can update servers running VMware ESXi operating systems remotely while running HP SUM ona Linux or Windows system. HP SUM only supports updating firmware for VMware nodes. Firmwarethat HP releases is available in the HP SPP. For information on the recommended driver and firmwareversions for HP ProLiant servers running VMware ESXi, see the VMware firmware and software recipeavailable on the HP Online Depot website at http://vibsdepot.hp.com/. For more information on thefirmware updates available in the HP SPP, see the HP Service Pack for ProLiant Release Notes.

VMware firmwareThe following must be true to update a VMware vSphere node:

• The node must be running VMware vSphere 5 or later.

• The node must be active on the network so HP SUM can detect it.

• You are not attempting to run HP SUM on the VMware vSphere node. You cannot execute HPSUM locally to update a VMware vSphere node.

• You are executing HP SUM on a Windows or Linux host computer.

• The VMware server must be running hp-smx-provider-500.03.01.2–434156 or later. Downloadthe providers for the appropriate version of VMware vSphere release from one of the followinglocations:

◦ Version 1.3.5 and later of the HP Insight Management WBEM Provider offline bundle. Youcan download the bundle from the HP Online Depot at http://vibsdepot.hp.com.

◦ The provider is included in version 5.25 and later of the HP Custom Image. You can downloadthe HP Custom Image ISO from the Custom VMware Image for HP ProLiant Servers websiteat http://www.hp.com/go/esxidownload.

Supported bundles

• HP SPP– The minimum HP SPP version is 2012.10.0

• HP Integrity bundles - HP SUM 6.0.0 supports all currently released HP Integrity bundles

Supported browsers

• Internet Explorer version 8 or later

• Firefox version 17 ESR or later

• Chrome version 24 or later

Network ports used by HP SUMHP SUM requires that certain network ports are available for proper operation. If you lock downnetwork ports, make sure that the ports listed in the network port tables are open so that HP SUMworks correctly when connecting to remote node servers and hosts. If you are unable to unlock thesenetwork ports, the only option is to run HP SUM locally and update network-based hosts, such as theOA, iLO, and VC modules, through their web interfaces.Updates for most node types require network traffic in both directions between the server running HPSUM and the node. The server running HP SUM creates a local HTTP server, which is used to servefirmware binaries to the node and to communicate node status. The remote node issues HTTP requestsand posts status updates to the server running HP SUM during the update process. If there is a routingproblem or firewall blocking traffic back from the remote node to the system running HP SUM, firmwareupdates might be blocked, status updates blocked or delayed, or both.

4 Operating systems and devices

Table 1 HP SUM Windows network ports

DescriptionPorts

Establishes a connection to a remote node via SSH to perform node inventory.Port 22

A secure data port used to transfer information.Port 443

Connects to the remote ADMIN$ share on node servers. These are the standardports Windows servers use to connect to the remote file shares. If you can connect

Ports 445 and 137/138/139 (Port 137is used only if you are using NetBIOSnaming service.) remotely to a remote Windows file share on the node server, you have the correct

ports open.

Default for some internal communications. This port listens on the remote side ifthere is no conflict. If a conflict occurs, the next available port is used.

Port 62286

Updates are passed to the node and retrieved through an internal secure webserver that uses the first available port in the range of 63001-63002. This allows

Ports 63001–63002

iLO and VC firmware updates without having to access the host server. It alsoallows the servers to run VMware or other virtualization platforms to update theiLO firmware without requiring a server reboot or a migration of the virtualmachines to other servers.Remote HP Integrity iLO and Superdome 2 updates require these ports to beopen on systems for network traffic in both directions to transfer firmware files.

You can use these FTP ports to perform switch updates.Ports 21 or 63006–63010

Table 2 HP SUM Linux network ports

DescriptionPorts

Establishes a connection to a remote node via SSH to perform node inventory.Port 22

A secure data port used to transfer information.Port 443

Default for some internal communications. This port listens on the remote side if thereis no conflict. If a conflict occurs, the next available port is used.

Port 62286

Updates are passed to the node and retrieved through an internal secure web serverthat uses the first available port in the range of 63001-63002. This support allows

Ports 63001–63002

iLO and VC firmware updates without having to access the host server. It also allowsservers running VMware or other virtualization platforms to update their iLO withouthaving to reboot their server or to migrate their virtual machines to other servers.Remote HP Integrity iLO and Superdome 2 updates require these ports to be open onsystems for network traffic in both directions to transfer firmware files.

You can use these FTP ports to perform switch updates.Ports 21 or 63006–63010

Special network configuration note for HP Integrity serversHP Integrity servers have management network and production interfaces. These are usually kept onseparate subnets in an installation. To perform full remote administration of the server, access is requiredfor both networks. If you keep both networks isolated, you need to perform management and operatingsystems tasks separately.

Enhancements• Browser-based GUI

• Perform multiple tasks at the same time

• Guided Update for the local host

• Create and manage custom baselines

• Create bootable ISOs from baselines

• Assign a baseline to a node

Enhancements 5

• Native x64 versions

• Remove Linux library requirements

• Persistent data storage of baseline, node, and credentials

• Available as a separate download on HP.com

• Update complex or partitions on Superdome 2 nodes

• Domain-level updates for Integrity I4 blades

• Update Integrity platform firmware through iLO and I/O firmware on HP-UX systems, while runningHP SUM on a Windows or Linux system

• 100% backwards compatible with previous Integrity firmware bundles

• Automatically discover associated targets

Downloading HP SUM

Downloading HP SUM from the HP SUM websiteYou can download the latest version of HP SUM from the HP SUM website at http://www.hp.com/go/hpsum.Unzip the file and save it to a directory on your system.

NOTE: Do not locate HP SUM 6.x files in the same directory as HP SUM 5.3.5 and earlier versionsof HP SUM.

Downloading HP SUM from the SDR websiteYou can download HP SUM as an RPM from the HP Software Delivery Repository at http://downloads.linux.hp.com/. The SDR contains a version of the HP SUM RPM for each supported operatingsystem and architecture type.You can use yum commands to search for HP SUM and download it to your system. You can also usea web browser to navigate the HP SDR and download the rpm.Use the following commands to search, download, or install HP SUM from the SDR:

Command exampleAction

yum search hpsumSearch for HP SUM with yum

yum install hpsumInstall HP SUM with yum

rpm -Uvh hpsum-5.3.5-66.rhwl5.i386.rpmDownload HP SUM from the SDR with a web browser, andthen install the RPM.

For more information on using the HP SDR, see the Getting Started and FAQ sections on the HPSoftware Delivery Repository website at http://downloads.linux.hp.com/SDR/index.html.For more information on using HP SUM with the SDR, see Linux best practices using HP Service Packfor ProLiant (SPP) and Software Delivery Repository (SDR) at http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03479393/c03479393.pdf.

Migrating nodes from HP SUM 5.x to HP SUM 6HP provides scripts that migrate the targets you added to HP SUM 5.x into nodes that HP SUM 6recognizes. If you want to edit the targets that you migrate to HP SUM 6, use the /script parameter.This generates a file that you can edit with a text editor application.

NOTE: The migration script does not support sudo credentials.

6 Downloading HP SUM

To migrate nodes to HP SUM 6:1. Navigate to the directory that holds HP SUM.2. Double-click port_targets.bat (Windows) or port_targets.sh (Linux).You can also run the scripts from the command line.Script syntax:port_targets.bat [/y] [/h] [/script] [/user {username} /password {password}

The script supports the following options:

DefinitionOption

Continue the migration without using prompts./y

Print the script help./h

This option creates a file with the migration commands, itdoes not run the script. You can edit the script commandsmanually before migrating the targets.

NOTE: Use this option to select the targets you migrate, oredit the user credentials for an individual target.

/script

This options sets a default username and password credentialsfor each node that HP SUM migrates. If you do not use thisoption, each node is given the following credentials:

/user {username} /password {password}

• user=username

• password=passwd

Launching and logging into HP SUM

Launching HP SUMHP SUM supports 32-bit and 64-bit processors. When you launch HP SUM, a script chooses whichversion of HP SUM to run. HP SUM logs you in using your current user credentials. To run HP SUM,your user needs to be part of the administrator group, or if you are on a Linux system, you can runHP SUM if you use the sudo command. If you are using Windows Server 2012, you need to log inwith the Administrator account, or use the Run as Administrator option.

NOTE: Do not open HP SUM in more than one browser tab or window or run HP SUM CLI commandswhen the GUI is open.

For more information about supported browsers, see the HP Smart Update Manager Release Notes,available at the HP Smart Update Manager Information Library, http://www.hp.com/go/hpsum/documentation.Launching HP SUM from an HP SUM download on a Windows host1. Unzip the file you downloaded from HP.2. In the HP SUM directory, double-click hpsum.bat.Launching HP SUM from an HP SUM download on a Linux host1. From a command-line, type ./hpsum.

Logging into HP SUMIf HP SUM is already running, and no users are logged in, use your computer’s credentials to log intoHP SUM.

Launching and logging into HP SUM 7

Issues and suggested actionsThe following are known issues and limitations with HP SUM. For a full list of troubleshooting itemssee the HP Smart Update Manager User Guide

HP SUM service stops running when HP SUM is mounted from a virtual media sourceSolution: Do not mount a virtual media source through an iLO. A known issue causes the iLO to restartand causes HP SUM to stop working.

HP SUM allows all users to log inSolution: All users can log into HP SUM. Only users with administrator permission can deploy updatesor add nodes.

Some screens are not translated from EnglishSolution: No action. This is a known issue that will be fixed in a future version.

HP SUM does not deploy multiple components at in one commandSolution: Copy the components into a directory and use the /use_location command. If you aredeploying more than ten components, use the work around.

The /use_web Legacy CLI command does not workSolution: No action. This is a known issue. This version of HP SUM does not support this command.

HP SUM does not build source RPMsSolution: No action. This is how HP SUM designed to work.

HP SUM legacy CLI documentation includes incorrect information about the/oa_username attribute

Solution: Use the /oa_username and /oa_password attributes even if the OA and VC use thesame credentials.

This argument provides the user name credential for OAassociated with VC specified with the target command-line

/oa_username

parameter. Only one set of OA credentials can be specifiedwith command-line parameters. You can add multiple VCnodes to command-line parameters with the targetparameter only if the credentials of OAs associated withspecified VCs are the same. You do not need to provide anOA network address associated with VC. HP SUM queriesit from a specified VC node.To update multiple VCs with different user names andpasswords, or VCs with OAs that have different credentials,use the corresponding input files OAUID and OAPWD.

Provides the password credential for OA associated with VCspecified with the "node" command-line parameter. Only

/oa_password

one set of OA credentials can be specified with command-lineparameters. You can add multiple VC nodes to command-lineparameters with the "node" parameter only if the credentialsof OAs associated with specified VCs are the same. You donot need to provide an OA network address associated withVC. HP SUM queries it from a specified VC node.To update multiple VCs with different user names andpasswords, or VCs with OAs that have different credentials,use the corresponding input files OAUID and OAPWD .

8 Issues and suggested actions

HP SUM requires minimum versions of VC and OA to support HP Integrity nodesSolution: Verify that HP Integrity i2 OA versions are 3.30 and VC version 3.6, and HP Integrity i4servers are OA version 3.60 and VC version 3.70.

Documentation feedbackHP is committed to providing documentation that meets your needs. To help us improve thedocumentation, send any errors, suggestions, or comments to Documentation Feedback(docsfeedback@hp.com). Include the document title and part number, version number, or the URL whensubmitting your feedback.

Documentation feedback 9