HP Smart Update Manager Version 6.0.0 User Manual
HP Smart Update Manager User Guide
Version 6.0.0
Abstract
This document describes how to use HP SUM to apply firmware updates to HP ProLiant and HP Integrity servers, and apply
software updates to HP ProLiant servers. This document is intended for individuals who understand the configuration and
operations of Microsoft Windows, Windows Server, Linux, smart components, HP-UX, VMware, and the risk of data loss from
performing updates.
HP Part Number: 613175-401a
Published: November 2013
Edition: 2
© Copyright 2009, 2013 Hewlett-Packard Development Company, L.P.
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.
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.
Acknowledgments
Microsoft®, Windows®, Windows® XP, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.
Contents
1 Introduction...............................................................................................7
HP SUM overview.....................................................................................................................7
About the graphical user interface..............................................................................................8
Status icon descriptions.............................................................................................................9
HP SUM new terms...................................................................................................................9
2 Downloading, installing, and launching HP SUM..........................................10
Downloading HP SUM............................................................................................................10
Downloading HP SUM from the HP SUM website...................................................................10
Downloading HP SUM from the SDR website.........................................................................10
Migrating nodes from HP SUM 5.x to HP SUM 6........................................................................10
Deploying HP SUM.................................................................................................................11
Running HP SUM...............................................................................................................11
Deploying firmware for HP ProLiant servers using the HP Service Pack for ProLiant.......................11
Deploying HP Integrity firmware bundles with HP SUM...........................................................12
Deployment modes............................................................................................................12
Deployment scenarios.........................................................................................................12
Disabling BitLocker to permit firmware updates (Windows only)....................................................13
Launching and logging into HP SUM.........................................................................................14
Launching HP SUM............................................................................................................14
Logging into HP SUM.........................................................................................................15
Logging out of the HP SUM GUI...............................................................................................15
3 Using the HP SUM GUI.............................................................................16
Using the Home screen............................................................................................................16
Using the Activity screen..........................................................................................................16
Using Guided Update.............................................................................................................16
Using the Baseline Library screen..............................................................................................18
Adding a baseline.............................................................................................................18
Creating a custom baseline.................................................................................................19
Deleting a baseline............................................................................................................21
Configuring components.....................................................................................................21
Using the Nodes screen..........................................................................................................21
Selecting multiple nodes.....................................................................................................22
Adding a node..................................................................................................................22
Editing a node...................................................................................................................25
Aborting a node update.....................................................................................................25
Node inventory.................................................................................................................25
Deploying a node..............................................................................................................26
Deploying all partitions in an HP Integrity BL870c i4 or BL890c i4 node..............................27
Node reports....................................................................................................................28
Deleting a node.................................................................................................................28
Server overview.................................................................................................................29
Integrity node overview.......................................................................................................29
Using the Enclosures screen.....................................................................................................29
Adding an enclosure..........................................................................................................29
Editing an enclosure...........................................................................................................29
Aborting an enclosure update.............................................................................................29
Enclosure inventory............................................................................................................30
Deploying an enclosure......................................................................................................30
Enclosure reports...............................................................................................................30
Deleting an enclosure.........................................................................................................30
Contents 3
Using the Servers screen..........................................................................................................30
Adding a server................................................................................................................30
Editing a server.................................................................................................................30
Aborting a server update....................................................................................................30
Server inventory.................................................................................................................30
Deploying a server.............................................................................................................31
Server reports....................................................................................................................31
Deleting a server...............................................................................................................31
Using the Switches screen........................................................................................................31
Adding a switch................................................................................................................31
Editing a switch.................................................................................................................31
Aborting a switch update....................................................................................................31
Switch inventory.................................................................................................................31
Deploying a switch.............................................................................................................31
Switch reports....................................................................................................................32
Deleting a switch...............................................................................................................32
Using the VM Hosts screen......................................................................................................32
Adding a VM host.............................................................................................................32
Editing a VM host..............................................................................................................32
Aborting a VM host update.................................................................................................32
VM hosts inventory.............................................................................................................32
Deploying a VM host.........................................................................................................32
VM host reports.................................................................................................................32
Deleting a VM host............................................................................................................33
Using the iLO screen...............................................................................................................33
Adding an iLO..................................................................................................................33
Editing an iLO...................................................................................................................33
Aborting an iLO update......................................................................................................33
iLO inventory.....................................................................................................................33
Deploying an iLO...............................................................................................................33
iLO reports........................................................................................................................33
Deleting an iLO.................................................................................................................33
Using the Intelligent Power Distribution Units screen.....................................................................33
Adding an iPDU................................................................................................................34
Editing an iPDU.................................................................................................................34
Aborting an iPDU update....................................................................................................34
iPDU inventory...................................................................................................................34
Deploying an iPDU............................................................................................................34
iPDU reports......................................................................................................................34
Deleting an iPDU...............................................................................................................34
Using the Virtual Connects screen.............................................................................................34
Adding a Virtual Connect...................................................................................................34
Editing a Virtual Connect....................................................................................................35
Aborting a Virtual Connect update.......................................................................................35
Virtual Connect inventory....................................................................................................35
Deploying a Virtual Connect...............................................................................................35
Virtual Connect reports.......................................................................................................35
Deleting a Virtual Connect..................................................................................................35
4 Using legacy scripts to deploy updates........................................................36
Command-line interface...........................................................................................................36
Command-line syntax.........................................................................................................36
Using Linux root credentials............................................................................................36
Prerequisites for using Linux root credentials.................................................................36
Switch update commands...............................................................................................37
4 Contents
Command-line arguments...................................................................................................37
Command-line examples.....................................................................................................45
Return codes.....................................................................................................................46
Windows smart-component return codes...............................................................................47
Linux smart-component return codes.....................................................................................47
Linux RPM return codes.......................................................................................................48
VMware ESXi smart-component return codes.........................................................................48
Input files...............................................................................................................................48
Input file format and rules....................................................................................................49
File encoding....................................................................................................................49
Error reporting...................................................................................................................50
Input file parameters...........................................................................................................50
Reports..................................................................................................................................61
Downloading HP SUM and components from the SDR.................................................................62
5 Advanced topics......................................................................................63
Configuring IPv6 networks.......................................................................................................63
Network ports used by HP SUM...............................................................................................63
GatherLogs............................................................................................................................64
6 Troubleshooting........................................................................................65
Collecting trace directories.......................................................................................................65
Baseline troubleshooting..........................................................................................................66
HP SUM lists SUSE Enterprise Linux dependencies for Red Hat Enterprise Linux systems................66
HP SUM displays two versions of the same component when creating a custom baseline.............66
HP SUM stops responding when performing inventory on large baselines..................................66
HP SUM does not return an error when you enter incorrect credentials forDownload from
hp.com.............................................................................................................................66
Node troubleshooting.............................................................................................................66
HP SUM does not respond when editing a node with sudo......................................................66
HP SUM does not display the Deploy button on the Deploy Nodes screen.................................67
An HP-UX node displays the error Inventory failed. The pciinfo module requires manual update
on remote target................................................................................................................67
HP SUM does not detect solid state hard drives......................................................................67
After HP SUM finishes an inventory, the inventory screen does not close....................................67
Cannot add a Windows node when running HP SUM on a Linux host......................................67
HP SUM does not display the Reboot button after it finishes a deployment.................................67
HP SUM does not automatically reboot a node......................................................................67
HP SUM does not display a reboot message in Guided Update...............................................67
When multiple nodes are selected, HP SUM does not display the most correct status..................67
HP SUM displays message Unable to locate the item you requested.........................................67
HP SUM stops responding when performing inventory on multiple nodes...................................67
HP SUM displays the message Unable to login or identify node as a supported device when HP
SUM cannot find a node.....................................................................................................67
HP SUM displays the message Ready for deployment while HP SUM is performing inventory on
a node.............................................................................................................................68
HP SUM does not display an entire screen............................................................................68
HP SUM displays extra credentials boxes on the Edit Node screen...........................................68
You can edit a node while HP SUM is deploying updates to the node.......................................68
HP SUM displays an associated node multiple times...............................................................68
HP SUM automatically performs inventory on a node after editing the node..............................68
Activity screen troubleshooting..................................................................................................68
HP SUM does not update the Activity screen accurately..........................................................68
VMware troubleshooting..........................................................................................................68
HP SUM displays an inventory error on a VMware node.........................................................68
Reports troubleshooting...........................................................................................................68
Contents 5
HP SUM does not generate reports for nodes that are offline...................................................68
HP SUM displays only requested reports in CSV and XML format.............................................68
HP SUM service troubleshooting...............................................................................................69
HP SUM service stops running when HP SUM is mounted from a virtual media source.................69
HP SUM allows all users to log in.........................................................................................69
Some screens are not translated from English.........................................................................69
Legacy CLI commands troubleshooting......................................................................................69
HP SUM does not deploy multiple components at in one command..........................................69
The /use_web Legacy CLI command does not work................................................................69
7 Support and other resources......................................................................70
Contacting HP........................................................................................................................70
Subscription service................................................................................................................70
Related information.................................................................................................................70
Typographic conventions.........................................................................................................71
HP Insight Remote Support software..........................................................................................72
HP Insight Online...................................................................................................................72
8 Documentation feedback...........................................................................73
Glossary....................................................................................................74
Index.........................................................................................................75
6 Contents
1 Introduction
HP SUM overview
HP SUM is a technology included in many HP products for installing and updating firmware and
software on HP ProLiant servers, and firmware on HP Integrity servers.
HP SUM provides a web-based GUI and a command-line scriptable interface for:
• Deployment of firmware for single or one-to-many HP ProLiant and HP Integrity servers and
network-based targets such as iLO, OA, 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).
HP SUM has an integrated hardware and software discovery engine that finds the installed hardware
and current versions of firmware and software in use on nodes you identify. HP SUM installs updates
in the correct order and ensures that all dependencies are met before deploying an update. HP
SUM prevents an installation if there are version-based dependencies that it cannot resolve.
Key features of HP SUM include:
• Dependency checking, which ensures appropriate installation order and component readiness
• Automatic and wizard-like Guided Update process
• Web browser based application
• Create custom baselines and ISOs
• Assign specific baselines to nodes
• Download updates from the web
• Intelligent deployment of only required updates
• Simultaneous firmware and software deployment for multiple remote nodes in GUI and CLI
modes
• Improved deployment performance
• Local online deployment of HP ProLiant servers and enclosures
• Remote (one-to-many) online deployment of HP ProLiant and HP Integrity servers and enclosures
• Local offline firmware deployments with HP Service Pack for ProLiant deliverables
• Remote offline deployment when used with the SmartStart Scripting Toolkit (HP ProLiant G7
and earlier servers), Scripting Toolkit (HP ProLiant Gen8 and later), iLO Virtual Media, or PXE
booted media
• GUI or CLI scripts with extensive logging
• Remote command-line deployment
• Support for updating firmware on network-based targets such as the OA, iLO through the
Network Management Port, VC Ethernet and Fibre Channel switches, and 3Gb/6Gb SAS BL
Switch interconnects on HP ProLiant servers
• Support for deploying firmware updates to supported Integrity servers and Superdome 2
enclosures
• Support for updating VC modules on Integrity servers
HP SUM overview 7
NOTE: HP SUM does not support third-party controllers. This includes flashing hard drives
behind these controllers.
• Remote online deployment of I/O Card firmware on HP ProLiant and HP Integrity targets
running HP-UX
About the graphical user interface
HP SUM is a browser-based application. The screenshot below shows the major sections of the
screen.
NOTE: Do not use the Back button press F5 in your browser window.
DescriptionItem
Main menu - This menu provides links to all HP SUM screens.1
2
6
7
• Activity list - Status updates appear briefly, and the activity icon displays the status of
recent activities. Click the Activities icon, to open the Activity panel.
• Login information - Displays the currently logged-in user, and offers a logout function.
• Help panel - Opens the help pane.
Screen name - Displays the name of the screen.3
Screen filters - Filters screen objects.4
Screen list - Displays a list of items on this screen.5
Baseline or Node name - This lists the baseline or node that you selected in the screen
list. This example shows the name of the selected baseline.
Informational highlight - This bar highlights information that you might need to perform or
know about for the selected item. Click to expand this box if there is more information.
Item details - This area provides full details about the selected item.8
Actions - Lists the available actions.9
NOTE: Screen options vary based on the screen you are viewing.
8 Introduction
Status icon descriptions
HP SUM uses icons to represent the current status of resources and alerts and to control the display.
Table 1 Status icons
DescriptionSmall iconLarge icon
Critical
Failed/Interrupted
Warning
OK
Successful
Disabled
Unknown
An In progress rotating icon indicates a change is being applied
or a task is running.
HP SUM new terms
The following terminology has changed from HP SUM 5.x to HP SUM 6:
DescriptionHP SUM 6HP SUM 5.x
BaselineRepository
InventoryDiscovery
ModeN/A
AnalyzeN/A
A collection of components for use in updating a node. For
example, HP SPP or a custom baseline.
Hardware you want to update.NodeTarget
The process where HP SUM determines node type.ScoutingDiscovery
The process where HP SUM determines the contents of a node
or baseline.
Network directory for baseline updates.LocationN/A
An automated or wizard-style method to update the local node.Guided UpdateN/A
You can run HP SUM in either interactive or non-interactive
mode.
The process where HP SUM verifies all dependencies are met
before beginning deployment.
The process where HP SUM begins the update process.DeployInstall
Status icon descriptions 9
2 Downloading, installing, and launching HP SUM
Downloading HP SUM
Downloading HP SUM from the HP SUM website
You 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 put HP SUM 6.x files in the same directory as HP SUM 5.3.5 and earlier versions
of HP SUM.
Downloading HP SUM from the SDR website
You 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
operating system and architecture type.
You can use yum commands to search for HP SUM and download it to your system. You can also
use a 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, and
then install the RPM.
For more information on using the HP SDR, see the Getting Started and FAQ sections on the HP
Software 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
Pack for 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 6
HP provides scripts that migrate the targets you added to HP SUM 5.x into nodes that HP SUM 6
recognizes. 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.
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}
10 Downloading, installing, and launching HP SUM
The script supports the following options:
DefinitionOption
Continue the migration without using prompts./y
Print the script help./h
/script
/user {username} /password {password}
Deploying HP SUM
The following sections discuss deployment from HP SUM. For more information on planning an
update, see the HP ProLiant and Integrity Firmware Management Best Practices Overview, HP
ProLiant and Integrity Firmware Management Best Practices Planning Guide, or HP ProLiant and
Integrity Firmware Management Best Practices Implementer Guide, available on the HP website:
http://www.hp.com/go/hpsum/documentation.
Running HP SUM
HP SUM provides the following modes:
This option creates a file with the migration commands, it
does not run the script. You can edit the script commands
manually before migrating the targets.
NOTE: Use this option to select the targets you migrate,
or edit the user credentials for an individual target.
This options sets a default username and password
credentials for each node that HP SUM migrates. If you do
not use this option, each node is given the following
credentials:
• user=username
• password=passwd
• GUI—For firmware and software deployments
• Scripted—For silent firmware and software deployments
HP SUM supports local and remote deployments. HP SUM runs in Windows and Linux in online
and offline mode. For more information about deployment modes, see “Deployment modes” (page
12).
NOTE: You cannot use Windows Hyper-V systems to run HP SUM and deploy updates. You can
select Hyper-V systems as a node from HP SUM running on a Windows or Linux system.
NOTE: Before deploying software updates to a server, be sure that a recent backup of the server
is available in the event the deployment procedure fails.
For information on the minimum requirements to run HP SUM, see the HP Smart Update Manager
Release Notes on the HP website:
http://www.hp.com/go/hpsum/documentation
Deploying firmware for HP ProLiant servers using the HP Service Pack for ProLiant
The SPP is a re-packaging of HP ProLiant system software and firmware for HP ProLiant BL/ML/DL/SL
servers and their options, and BladeSystem enclosures including OA, VC, and 3 Gb SAS switches
running supported Windows, Linux, VMware (supported firmware updates only) operating systems.
The single SPP image contains a comprehensive collection of firmware and system software
components including drivers, agents, tools, utilities, and firmware that is tested, managed, and
deployed together as a single solution.
The SPP includes HP SUM for deployment of the SPP components.
Deploying HP SUM 11
For a complete list of HP ProLiant systems and software supported by SPP, and updates available
in an SPP release, see the HP Service Pack for ProLiant Release Notes on the HP website:
http://www.hp.com/go/spp/documentation
Deploying HP Integrity firmware bundles with HP SUM
You can use HP SUM to deploy components delivered with the HP Integrity firmware bundles.
Deploying firmware to HP Integrity servers is done remotely and is the same as deploying other
firmware, such as OA, with the following exceptions:
• Specify the IP address of the Monarch (primary) OA on Superdome 2, or the Monarch iLO 3
management processor on multi-blade servers.
• Specify the server IP address as the target to update I/O firmware on HP-UX servers. You can
only update remote HP-UX targets.
For more information on HP Integrity firmware bundles, see the Manage HP Integrity Servers
Firmware Updates website at http://www.hp.com/go/smartupdate/integrity.
Deployment modes
The following key terms apply when using HP SUM to deploy updates:
DefinitionTerm
Local
Remote
Online
Offline
The installation runs on the physical hardware you are
updating. For example, running a utility on a server to
update the system ROM of the server.
The installation runs on one system, but updates other
physical nodes. For example, updating the OA or HP
Integrity server firmware across a network.
The installation occurs while the host processor is running
in the normal server environment. For example, if the server
runs Microsoft Windows Server 2012, the update occurs
under this environment. The update does not require you
to boot to a special environment to update the firmware.
You might need to reboot the node to activate the firmware.
In offline mode, the HP SUM boots a small Linux kernel
and enables updates to occur on a single server.
• Only updates the local system
• Only uses a single baseline
NOTE: Some features of HP SUM that require the
regular local host operating systems are not supported
in offline mode.
These terms can be used in combination to designate the type of environment required for updates
to occur, such as local-online or remote-online.
Deployment scenarios
HP SUM deploys updates from a local host to one or more remote hosts. If the host running HP
SUM uses Windows, you can update Windows, Linux, VMware, or HP-UX targets. If the host
running HP SUM uses Linux, you can update Linux, VMware, or HP-UX nodes. You can also update
remote HP ProLiant or HP Integrity iLO, OA, and VC nodes from Windows or Linux systems.
12 Downloading, installing, and launching HP SUM
The following table describes when typical HP SUM deployment scenarios are used.
Used whenScenario
Graphical deployment on a local host
Scripted deployment on a local host
Graphical deployment to a remote host
Scripted deployment to a remote host
• You are not familiar with command line tools.
• You are deploying components on a local, single host.
• Updates do not require scripting.
• You are familiar with command line tools.
• You are deploying components on a local, single host.
• Updates require a customized, scripted deployment.
• You are not familiar with command line tools.
• You are deploying components on one or more remote
hosts.
• Updates do not require scripting.
• You are familiar with command line tools.
• You are deploying components on one or more hosts.
• Updates require a customized, scripted deployment to
one or more host systems.
Disabling BitLocker to permit firmware updates (Windows only)
The TPM, when used with BitLocker, measures a system state. Upon detection of a changed ROM
image, it restricts access to the Windows file system if the user cannot provide the recovery key.
HP SUM detects if a TPM is enabled in your system. For some newer models of HP ProLiant servers,
if a TPM is detected in your system or with any remote server selected as a target, HP SUM utilities
for HP 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 in the following situations:
• You do not temporarily disable BitLocker before flashing the system BIOS when using the
Microsoft BitLocker Drive Encryption.
• You have optionally selected to measure HP iLO, Smart Array, and NIC firmware.
If HP SUM detects a TPM, a warning message appears:
CAUTION: A Trusted Platform Module (TPM) has been detected in this system. Failure to perform
proper OS encryption procedures will results in loss of access to your data if recovery key is not
available. Recommended procedure for Microsoft Windows (R) BitLocker (TM) is to \”suspend\”
BitLocker prior to System ROM or Option ROM firmware flash. If you do not have your recovery
key or have not suspended BitLocker, exit this flash. Failure to follow these instructions will results
in loss of access to your data.
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,
Disabling BitLocker to permit firmware updates (Windows only) 13
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.
CAUTION: 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 setting the /tpmbypass parameter
for HP SUM or the firmware update is blocked.
To temporarily disable BitLocker support to allow firmware updates:
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 windows, and then start the firmware update.
To enable advanced startup options:
1. Enter cscript manage-bde.wsf -protectors -disable c:
2. 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.
3. Enter cscript manage-bde.wsf -protectors -enable c:
The following table describes TPM detection scenarios that you might encounter.
If TPM is detected and enabled, the installation is not silent,
and a system ROM must be updated.
If 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. Because the installation is silent, the installation is
If TPM is detected and enabled with Option ROM
Measuring, the installation is not silent, and a system ROM
must be updated.
If 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.
the installation occurs, and the /tpmbypass switch is
supplied.
Launching and logging into HP SUM
ResultScenario
A warning message appears. Select OK to continue. The
installation is not canceled.
No warning appears. A new log file is generated
(%systemdrive%\cpqsystem\log\cpqstub.log).
terminated and cannot continue.
A warning message appears. After selecting OK, you can
continue. The installation is not canceled.
No 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.
The installation occurs.If TPM is detected and enabled, the installation is silent,
Launching HP SUM
HP SUM supports 32–bit and 64–bit processors. When you launch HP SUM, a script chooses the
version of HP SUM to run. HP SUM logs you in using your current user credentials. To run HP SUM,
your userid needs to be part of the administrator group, or, on a Linux system, you can run HP
14 Downloading, installing, and launching HP SUM
SUM using the sudo command. If you are using Windows Server 2012, you must log in with the
Administrator account, or select Run as Administrator.
NOTE: Do not open HP SUM in more than one browser tab or window or run HP SUM CLI
commands when 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 host
1. Unzip the file you downloaded.
2. In the HP SUM directory, double-click hpsum.bat.
Launching HP SUM from an HP SUM download on a Linux host
1. From a command-line, type ./hpsum.
Logging into HP SUM
If HP SUM is already running, and no user is logged in, use your computer’s credentials to log
into HP SUM.
Logging out of the HP SUM GUI
1. Click the user icon, and then click Logout.
2. Select one of the following:
• Log Off - Current user.
• Shutdown - This option will shutdown HP SUM service.
3. Click OK.
HP SUM stores node information between sessions, including user credentials for nodes. The
information is stored in a database file in hex format. To clear the information, run the
clean-cache.cmd (Windows) or clean-cache.sh (Linux). To run clear-cache:
1. Shut down the HP SUM service.
2. From a command-line window, navigate to the directory that contains HP SUM.
3. Type clear-cache.bat (Windows) or clear-cache.sh (Linux).
NOTE: If you are using a GUI, you can navigate to the directory that holds HP SUM and
double-click the file to clear the cache.
NOTE: Running the clean-cache command erases all nodes, baselines, and other information
entered in HP SUM.
Logging out of the HP SUM GUI 15
3 Using the HP SUM GUI
Using the Home screen
When you launch HP SUM, HP SUM displays the Home screen. From this screen, you can click
Guided Update, Baseline Library, or Nodes. There is also a Get Started button that launches Guided
Update. To navigate to other screens, use the navigation menu in the upper-left corner.
Using the Activity screen
The Activity screen provides a brief update of the activities that HP SUM is performing, or has
recently performed. The table displays the source, message, state, and last update time of an
activity.
Using Guided Update
HP SUM's Guided Update function allows you to update the localhost using the default baseline.
The default baseline is the directory from which you are running HP SUM.
NOTE: If the directory from which you are running HP SUM has no updates, then you cannot
use Guided Update. If there is no default baseline, HP SUM displays a message in the Inventory
of Baseline section.
• Interactive: In this mode HP SUM uses the default baseline to update the localhost. You can
choose the updates that HP SUM applies to the localhost.
NOTE: HP SUM does not support configuring components in Guided Update.
• Automatic: In this mode HP SUM automatically updates the localhost and uses the default
baseline.
NOTE: In automatic mode, HP SUM automatically begins updates when you click OK.
16 Using the HP SUM GUI
Using Guided Update in Interactive mode
1. In the navigation menu, click Guided Update.
2. Click Interactive.
3. Click OK.
4. HP SUM displays the baseline and the localhost.
NOTE: HP SUM automatically starts to take inventory of the baseline and the node. The
inventory process duration varies based on the number of updates in the baseline.
5. Click Next after HP SUM finishes the inventory.
Recommended updates ready to deploy are highlighted in blue and HP SUM displays a green
icon in the Ready to proceed column.
NOTE: Items that are up-to-date or optional are not highlighted. Click Force to deploy these
updates. If you want to globally select all components to rewrite or downgrade, click
Actions+Advanced Options and select Rewrite or Downgrade. Click Analyze, and HP SUM
performs an analysis again.
NOTE: Double-click an update to view the component details. If you want to view the
information in the new update, click the hyperlink.
6. Click Deploy.
HP SUM performs component analysis before deploying updates.
7. Review the installation log files.
Using Guided Update in Automatic mode
1. In the navigation menu, click Guided Update.
2. Click Automatic.
3. Click OK.
NOTE: HP SUM begins to deploy updates after you click OK. HP SUM does not support
aborting updates in the Guided Update Automatic mode.
NOTE: HP SUM does not support installing SNMP, WBEM Providers, and AMS components
in automatic mode. Use Interactive mode if you want to install these components.
Using Guided Update 17
Using the Baseline Library screen
The Baseline Library screen displays the baselines and additional packages you will use to update
your nodes. Baselines include the HP SPP, HP Integrity bundle, or custom baselines that include
updates that you select from other baselines or additional packages. Additional packages are
directories that hold updates that are not included in a named update package, for example a
Hot Fix. HP SUM saves baseline information between sessions.
HP SUM displays each added baseline in the left pane. Select a baseline, and HP SUM displays
the following information for each baseline and additional package.
• Release date
• Languages
• Operating systems
• Enhancements
• Fixes – HP SUM includes a search box for finding updates that meet the search parameters.
You can search on file name, description, and update type.
Double-click an update to view its details.
• Component configuration – You need to configure some components before you can deploy
the update. For more information about configuring components, see “Configuring components”
(page 21).
Adding a baseline
1. On the Baseline Library screen, click Add baselines.
2. Do one of the following:
HP SUM default location: This location uses a directory
or file share that the system running HP SUM can access.
Follow these steps:To add this baseline:
a. Select the location type HP SUM default location.
b. Enter the directory path to the baseline, or click
Browse and use the menu to navigate to the
directory.
UNC path (for example \\host\dir): This location uses
UNC paths that the system can access.
NOTE: UNC path is only supported in Windows
systems.
18 Using the HP SUM GUI
a. Select the location type UNC path (for example
\\host\dir).
b. In the Enter URI for the baseline field, type the UNC
address for the source baseline.
Follow these steps:To add this baseline:
c. Enter the username, required.
d. Enter the password, required
NOTE: HP SUM does not support mapped UNC
drives.
Download from hp.com: This location downloads
updates from ftp.hp.com. HP SUM downloads the latest
versions of updates that HP has released.
a. Select the location type Download from HP.
b. Click Browse and use the menu to navigate to the
directory where you want to save the custom
baseline.
c. Enter the URI for the proxy server. (Only required if
you chose to use proxy server.)
d. Enter the username. (Only required if you chose to
use proxy server.)
e. Enter the password. (Only required if you chose to
use proxy server.)
f. Click Done.
NOTE: HP SUM adds all baselines in a directory.
3. Click Add.
Check the activity log to see the status of the baseline.
NOTE: If the baseline does not appear in the baseline list, make sure there are updates in
the directory.
NOTE: HP SUM begins to inventory a baseline as soon as you finish adding the baseline. To
minimize the impact on system resources, HP SUM does not recommend adding other baselines
until the baseline inventory process finishes.
Creating a custom baseline
Creating a custom baseline allows you to deploy specific updates, minimize the size of update
baselines or bootable and non-bootable ISOs, and standardize the updates that you deploy to
your environment.
NOTE: To create a custom bootable ISO, you must have a bootable HP SPP or HP SUM ISO
available in your source baselines.
1. From the Baseline Library screen, click Actions→Create Custom.
2. In the Description text box, enter a description for the baseline. The maximum length for the
description is 50 characters.
3. In the Version boxes, use the navigation arrows to create a version number, for example
2013.5.21.
NOTE: The Baseline Name is automatically generated by combining the description and
version.
4. In the Output Location field, click Browse to navigate to a directory where you want to save
the baseline.
NOTE: HP SUM does not support creating a new directory when it creates the custom
baseline. Create the new directory outside of HP SUM.
NOTE: Do not save more than one custom baseline in a directory.
Using the Baseline Library screen 19
5. Select Make Bootable ISO file if you want to create a bootable ISO with your baseline.
If you choose to make a bootable ISO, click Browse and choose a directory where HP SUM
can find the source for the bootable ISO. The custom baseline bootable ISO includes the
version of HP SUM included in the source ISO. For example, if you choose the HP SUM 6
ISO as the source ISO, HP SUM 6 is included in the ISO. If you choose the ISO with the SPP
2013.09.0 as the source ISO, then HP SUM 5.3.5 is included in the ISO.
6. Select whether you want to Run in background or not.
If you select to create the baseline in the background, you can monitor the progress in the
Activity screen. For more information, see “Using the Activity screen” (page 16).
7. In the Baseline Sources section, select the baselines that contain the components you want to
include in the custom baseline.
NOTE: If the same component is included in more than one source baseline, HP SUM lists
the component multiple times. If you select the component from multiple baselines, HP SUM
displays the component multiple times when you add it as a baseline, but the baseline only
includes one copy of the component file.
8. In the Filters section, select the Component Type you want to choose, Firmware, Software, or
Both.
9. In the Filters section, select each kind of update you want to include in the baseline:
• Critical Updates: Updates that HP requires you to deploy immediately.
• Recommended Updates: Updates that HP recommends you deploy at your earliest
convenience.
• Optional Updates: Update to this version if your system is affected by one of the
documented fixes, or if there is a desire to utilize any of the enhanced functionality
provided by this version.
10. Select the Advanced Filters you want to apply to the baseline:
OptionsFilter category
Select the system architecture to include in the baseline.Architecture
Select the operating systems to include in the baseline.OS Type
Select the device types to include in your baseline.Device Type
11. Click Apply Filters. HP SUM displays a list of available updates.
12. Select the individual component updates you want to include in your baseline.
Use the search function to find specific updates in the list.
13. Click Create ISO or Save Baseline to create the baseline.
When you click Create ISO or Save Baseline, HP SUM does not close the Create Custom
Baseline screen, in case you want to create another custom baseline.
NOTE: If you create an ISO, HP SUM also creates a baseline in the directory. You can add
this baseline to HP SUM so you can use it locally.
IMPORTANT: Do not create more than one custom baseline containing a large number of
components at a time.
14. Click Close to close the Create Custom Baseline screen.
NOTE: HP SUM does not automatically add the custom baseline to the Baseline Library. For more
information on adding a baseline, see “Adding a baseline” (page 18).
20 Using the HP SUM GUI
Deleting a baseline
HP SUM does not support deleting a baseline if it is associated with a node.
To delete a baseline:
1. On the Baseline Library screen, select a baseline.
2. Click Actions→Delete.
NOTE: If the baseline is associated with one or more nodes, HP SUM displays a list of the
nodes. Edit the nodes to change the associated baseline, or delete the node. For more
information, see “Editing a node” (page 25) or “Deleting a node” (page 28).
3. Click Yes, delete to confirm that you want to delete the baseline.
Configuring components
Some components might have required or optional configuration settings. Configuration parameters
include information necessary to set up the component correctly or passwords required for software
installed by the component. The configuration is stored within the component and is propagated
to all nodes. If the optional configuration data of a component is not provided and the component
has not been installed previously, the 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, 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. You can change component options from the Baseline Library screen.
To configure components:
1. On the Baseline Library screen, scroll down to the list of components, and then click Needs
Configuration for each component you need to configure.
NOTE: Configuration options vary based on the component.
NOTE: HP SUM 6.0 does not support configuring components released prior to the HP SPP
2013.09.0. Use HP SUM 5.3.5 to update these components.
Using the Nodes screen
Nodes are hardware environment components. The Nodes screen displays the nodes that you
have added to HP SUM and HP SUM can manage. On the Nodes screen, HP SUM displays four
sets of information about the node:
• General
• Associated devices
• Storage
• NIC/FC-HBA/CNA
Using the Nodes screen 21
NOTE: The details that HP SUM displays vary based on the node type.
NOTE: If this is the first time you are running HP SUM 6, and have set up targets in HP SUM 5.x,
you can use a migration script to populate the Nodes screen in HP SUM 6.0. For more information,
see “Migrating nodes from HP SUM 5.x to HP SUM 6” (page 10).
Selecting multiple nodes
On the Nodes screen, select more than one node by pressing CTRL and clicking the other nodes.
If you select multiple nodes, you can:
• View node IP address, node type, and other information
• Generate, set report options, and view reports in the Reports Center
• Choose baselines to use with the nodes
• Set reboot and force options
• Change credentials
Adding a node
You can add a node using a specific IP address, or by searching an IP address range.
Adding a single node by IP address
1. From the Nodes screen, click Add Node.
2. Enter the IP address for the new node in the IP/DNS field.
22 Using the HP SUM GUI
3. Enter a description for the node.
4. In the Type field, select the node type. If you do not know the node type, select Unknown.
During the inventory process, HP SUM determines the node type.
NOTE: Selecting the correct node type might help HP SUM complete node inventory faster.
Some nodes allow you to select the check-box so that HP SUM automatically adds Associated
Devices. The associated devices identified varies based on the node type. Select what you
want HP SUM to do if it discovers updates already running on the node:
• Leave the update running and bypass the node
• Stop any currently running update process on the node and replace it with updates from
this session
5. If you want, select the baseline, additional package, or both to apply to this node. For more
information on adding a baseline, see “Adding a baseline” (page 18).
6. Select one of the following:
• Use current credentials (requires existing trust relationship with the node): This option is
for Windows nodes only.
• Enter administrator credentials
7. Linux nodes allow you to use sudo credentials to deploy updates without logging into the node
with root credentials. To use sudo commands, you have to install sudo capabilities on the
node.
If you want to use sudo, in the Access Level field, select one of the following.
• Click Use sudo to update components if you want to use sudo credentials.
• Click Enter super user credentials to update components if you want to enter sudo
credentials.
NOTE: Enter the sudo credentials in the Credentials field.
8. Click Add.
Using the Nodes screen 23
Adding a node by searching a range of IP addresses
1. From the Nodes screen, click Add Node.
2. Click Find Nodes.
3. Enter a range of IP addresses for HP SUM to search, and click Search.
4. Select the nodes you want to add, and then click Add.
5. In the Baselines section, select a Baseline, Additional Packages, or both (Optional).
6. In the Credentials section, select whether to Use current user credentials or Enter administrator
credentials (Windows only).
If you choose to enter administrator credentials, enter a username and password.
7. Click Add.
In the Added Nodes section, HP SUM displays the nodes you selected.
8. Click Close to go back to the Nodes screen.
24 Using the HP SUM GUI
Loading...