HP Smart Update Manager User Guide Version 6.2.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.
© Copyright 2009, 2014 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.
Contents 1 Introduction...............................................................................................9 HP SUM overview.....................................................................................................................9 About the graphical user interface............................................................................................10 Status icon descriptions.........................................................................................................
Adding a server................................................................................................................37 Editing a server.................................................................................................................39 Aborting a server update....................................................................................................40 Server inventory...........................................................................................................
Command-line syntax.........................................................................................................69 Command-line arguments...................................................................................................70 Command-line examples.....................................................................................................78 Return codes.....................................................................................................................
HP SUM engine stops running when HP SUM is mounted from a virtual media source...............103 HP SUM allows all users to log in.......................................................................................103 Some screens are not translated from English.......................................................................103 HP SUM displays the error message “Multiple connections to a server or shared resource by the same user...”.................................................................
Return codes...................................................................................................................114 Example.........................................................................................................................114 GetComponentLogs..............................................................................................................114 Syntax.................................................................................................................
Related information...............................................................................................................123 Typographic conventions.......................................................................................................124 HP Insight Remote Support software........................................................................................124 HP Insight Online.........................................................................................................
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.
About the graphical user interface HP SUM is a web browser-based application. When you launch HP SUM in GUI mode, the system uses the default web browser. The screenshot below shows the major sections of the screen. NOTE: Do not use the Back button or press F5 in your browser window. Item Description 1 Main menu - This menu provides links to all HP SUM screens. 2 • Activity list - Status updates appear briefly, and the activity icon displays the status of recent activities.
Table 1 Status icons Large icon Small icon Description 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.x: HP SUM 5.x HP SUM 6.x Description Repository Baseline A collection of components for use in updating a node. For example, HP SPP or a custom baseline. Target Node Hardware you want to update.
2 Downloading, installing, and launching HP SUM Downloading HP SUM You can download HP SUM from the HP website or from the HP Software Delivery Repository. Downloading HP SUM from the HP website 1. 2. 3. Launch a web browser. Go to http://www.hp.com/go/hpsum/download. Click on the file that you want to download: • HP Smart Update Manager ISO – The HP SUM ISO contains HP SUM and a bootable ISO environment. Firmware and Software components can be added to create a customized baseline.
Migrating nodes from HP SUM 5.x to HP SUM 6.x HP provides scripts that migrate the targets you added to HP SUM 5.x into nodes that HP SUM 6.x recognizes. If you want to edit the targets that you migrate to HP SUM 6.x, 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.x: 1. Navigate to the directory that holds HP SUM. 2. Double-click port_targets.
The following sections discuss deployment from HP SUM. For more information on planning an update, see the HP Smart Update Best Practices Overview, HP Smart Update Best Practices Planning Guide, or HP Smart Update Best Practices Implementer Guide, available on the HP website: http://www.hp.com/go/hpsum/documentation. NOTE: HP SUM does not support deploying updates from a Linux host to a remote Windows node. Run HP SUM on a Windows host to deploy updates to Windows nodes.
Deployment modes The following key terms apply when using HP SUM to deploy updates: Term Definition Local 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. Remote 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 following table describes when typical HP SUM deployment scenarios are used. Scenario Used when Graphical deployment on a local host • You are not familiar with command line tools. • You are deploying components on a local, single host. • Updates do not require scripting. Scripted deployment on a local host • You are familiar with command line tools. • You are deploying components on a local, single host. • Updates require a customized, scripted deployment.
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.
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.
3 Using the HP SUM GUI Updating a node with HP SUM example The following steps offer a simplified example of deploying updates to a single node without using the Localhost Guided Update. 1. Add a baseline to the Baseline Library. For more information, see “Adding a baseline” (page 22). 2. Add a node to the Nodes screen. For more information, see “Adding a node” (page 26). 3. Inventory the node. For more information, see “Node inventory” (page 29). 4. Review the updates and then deploy the updates.
Using Localhost Guided Update in Interactive mode 1. In the navigation menu, click Localhost Guided Update. NOTE: 2. 3. 4. If you need to make a change to your selections on this screen, click Start Over. Click Interactive. Click OK. 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.
NOTE: HP SUM begins to deploy updates after you click OK. HP SUM does not support aborting updates in the Localhost Guided Update Automatic mode. NOTE: HP SUM does not support installing SNMP and WBEM Providers components in automatic mode. Use Interactive mode if you want to install these components. Using the Baseline Library screen The Baseline Library screen displays the baselines and additional packages you will use to update your nodes.
• 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 25). Adding a baseline 1. On the Baseline Library screen, click Add Baselines. NOTE: 2.
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. Baseline reports 1. 2. 3. 4. 5. Add a baseline. For more information, see “Adding a baseline” (page 22). Add a node. For more information, see “Adding a node” (page 26). Perform inventory on the node. Fore more information, see “Node inventory” (page 29).
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. 9. In the Filters section, select the Component Type you want to choose, Firmware, Software, or Both.
1. 2. On the Baseline Library screen, select a baseline. 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 28) or “Deleting a node” (page 32). 3. Click Yes, delete to confirm that you want to delete the baseline. Configuring components Some components might have required or optional configuration settings.
NOTE: If this is the first time you are running HP SUM 6.x, 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.x. For more information, see “Migrating nodes from HP SUM 5.x to HP SUM 6.x” (page 13). The yellow information bar under the node name gives a brief description of the status or action you can perform next on the node. Click the arrow to expand for full details.
To add a node 1. From the Nodes screen, click Add Node. Adding a single node by IP/DNS name a. b. c. d. Select Add a single node by IP/DNS name. Enter the IP address or DNS name. Enter a description for the node. 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: faster.
To add a node by searching a range of IP addresses a. b. c. Select Find nodes on network with an IP range. Click Find Nodes. Enter a range of IP addresses for HP SUM to search, and click Search. HP SUM displays the nodes it finds in the Available Nodes field. d. e. f. Select the nodes you want to add from the Available Nodes section, and then click Add Nodes. If you want to assign a baseline, select a Baseline, Additional Packages in the Baseline to Apply field.
To edit a node 1. 2. From the Nodes screen, highlight the node and then click Actions→Edit. Change the items you want to edit: • Description • Type NOTE: Select the check box if you want HP SUM to automatically add Associated Devices. (Not available for all node types.) • HP SUM displays the currently selected baseline and additional package. Use the drop-down menu if you want to change these.
Deploying a node When you open the Deploy screen, HP SUM displays the IP/DNS address for the node and the node type. The Deploy screen displays components available for deployment, and if a version of the component is installed on the node, HP SUM displays the Installed version and Active version of the component. NOTE: HP SUM supports configuring components on the Baseline Library screen. For more information, see “Configuring components” (page 25).
4. 5. In the Associated Node Details field, select any nodes that you want to update. In the Baseline Library field, select each component that you want to update. Use the Search box to type in search terms for the components. For more information about an update, click the version number. If you are deploying a Linux node, HP SUM displays only RPM updates that are valid for your node. NOTE: You can click Force to downgrade or rewrite a component that is available for downgrade or rewrite.
reports for a node enable you to generate HTML, XML, and CSV reports. On the Reports screen, HP SUM includes a Reports Center that displays previous reports you have generated. NOTE: If you want to generate a report for more than one node. press CTRL and click the nodes you want to select. To generate a report 1. 2. From the Nodes screen, select a report or multiple reports, and then click Actions→Report.
• Serial number • List of devices The following actions are available from the Overview screen: • Add: See “Adding an enclosure” (page 33). • Edit: See “Editing a node” (page 28). • Report: See “Node reports” (page 31). • Deploy: See “Deploying a node” (page 30). Using the Enclosures screen The Enclosures screen displays all of the enclosure nodes that HP SUM has inventoried. You can manage your enclosures from this screen. Adding an enclosure 1. 2. From the Enclosure screen, click Add Node.
f. g. 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 Linux and HP-UX 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. NOTE: Super user and sudo are not available for all nodes.
HP SUM displays the nodes it finds in the Available Nodes field. d. e. f. Select the nodes you want to add from the Available Nodes section, and then click Add Nodes. If you want to assign a baseline, select a Baseline, Additional Packages in the Baseline to Apply field. 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. 2. Click Add.
Enclosure inventory 1. 2. 3. From the Enclosures screen, highlight the enclosure on which you want to take inventory. Click Actions→Inventory. The Enclosure Inventory procedure is the same as Node Inventory procedure. To inventory a node 1. 2. 3. From the Nodes screen, highlight the node and then click Actions→Inventory. Select a baseline, additional package, or both to apply to the node. Click Inventory. Deploying an enclosure 1. 2. 3.
8. Click Analysis, and then click Deploy to begin the deployment. NOTE: To begin the deployment, all dependency issues must be resolved, for example, adding a baseline, administrator credentials, and supported installed versions. 9. Click View log for the node, in the General section of the Node screen, and then click View log for the component you installed, to view the details of the installation. Enclosure reports 1. 2. 3.
d. 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: faster. Selecting the correct node type might help HP SUM complete node inventory 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.
HP SUM displays the nodes it finds in the Available Nodes field. d. e. f. Select the nodes you want to add from the Available Nodes section, and then click Add Nodes. If you want to assign a baseline, select a Baseline, Additional Packages in the Baseline to Apply field. 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. 2. Click Add.
NOTE: Select the check box if you want HP SUM to automatically add Associated Devices. (Not available for all node types.) • HP SUM displays the currently selected baseline and additional package. Use the drop-down menu if you want to change these. NOTE: If you want to delete a baseline or additional package, the baseline or additional package cannot be associated with a node. Associate a new baseline or delete the node to delete a baseline. 3.
3. 4. 5. If you want to downgrade or rewrite options to firmware or software only, click Force options can be applied to, and then select from the following: • Firmware: This displays only firmware updates. • Software: This displays only software updates. In the Associated Node Details field, select any nodes that you want to update. In the Baseline Library field, select each component that you want to update. Use the Search box to type in search terms for the components.
NOTE: HP SUM automatically opens the report after it finishes generating the report. If you do not have the format associated to an application, HP SUM prompts you to save the report. 4. Click Generate. Deleting a server 1. 2. 3. From the Server screen, highlight the server you want to delete. Click Actions→Delete. Click Yes, delete to delete the server. Using the Switches screen The Switches screen displays only switch nodes that HP SUM has inventoried. Adding a switch 1. 2.
f. g. 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 Linux and HP-UX 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. NOTE: Super user and sudo are not available for all nodes.
HP SUM displays the nodes it finds in the Available Nodes field. d. e. f. Select the nodes you want to add from the Available Nodes section, and then click Add Nodes. If you want to assign a baseline, select a Baseline, Additional Packages in the Baseline to Apply field. 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. 2. Click Add.
To inventory a node 1. 2. 3. From the Nodes screen, highlight the node and then click Actions→Inventory. Select a baseline, additional package, or both to apply to the node. Click Inventory. Deploying a switch 1. 2. 3. From the Switches screen, highlight the switch you want to deploy. Click Actions→Review/Deploy. The Switch Deploy function uses the same function as the Node Deploy function. To deploy a node 1. 2. 3. 4. 5.
NOTE: To begin the deployment, all dependency issues must be resolved, for example, adding a baseline, administrator credentials, and supported installed versions. 9. Click View log for the node, in the General section of the Node screen, and then click View log for the component you installed, to view the details of the installation. Switch reports 1. 2. 3. From the Switches screen, highlight the switch for which you want to generate reports. Click Actions→Reports.
NOTE: faster. Selecting the correct node type might help HP SUM complete node inventory 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. Some nodes select how you want HP SUM to progress if it detects an update process on the remote node.
HP SUM displays the nodes it finds in the Available Nodes field. d. e. f. Select the nodes you want to add from the Available Nodes section, and then click Add Nodes. If you want to assign a baseline, select a Baseline, Additional Packages in the Baseline to Apply field. 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. 2. Click Add.
NOTE: Select the check box if you want HP SUM to automatically add Associated Devices. (Not available for all node types.) • HP SUM displays the currently selected baseline and additional package. Use the drop-down menu if you want to change these. NOTE: If you want to delete a baseline or additional package, the baseline or additional package cannot be associated with a node. Associate a new baseline or delete the node to delete a baseline. 3.
3. 4. 5. If you want to downgrade or rewrite options to firmware or software only, click Force options can be applied to, and then select from the following: • Firmware: This displays only firmware updates. • Software: This displays only software updates. In the Associated Node Details field, select any nodes that you want to update. In the Baseline Library field, select each component that you want to update. Use the Search box to type in search terms for the components.
NOTE: HP SUM automatically opens the report after it finishes generating the report. If you do not have the format associated to an application, HP SUM prompts you to save the report. 4. Click Generate. Deleting a VM host 1. 2. 3. From the VM hosts screen, highlight the VM host. Click Actions→Delete. Click, Yes, delete. Using the iLO screen The iLO screen displays only iLO nodes that you have added to HP SUM. Adding an iLO 1. 2. From the iLO screen, click Add Node.
f. g. 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 Linux and HP-UX 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. NOTE: Super user and sudo are not available for all nodes.
HP SUM displays the nodes it finds in the Available Nodes field. d. e. f. Select the nodes you want to add from the Available Nodes section, and then click Add Nodes. If you want to assign a baseline, select a Baseline, Additional Packages in the Baseline to Apply field. 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. 2. Click Add.
iLO inventory 1. 2. 3. From the iLO screen, highlight the iLO on which you want to take inventory. Click Actions→Inventory. The iLO inventory procedure is the same as the Node Inventory procedure. To inventory a node 1. 2. 3. From the Nodes screen, highlight the node and then click Actions→Inventory. Select a baseline, additional package, or both to apply to the node. Click Inventory. Deploying an iLO 1. 2. 3. From the iLO screen, highlight the iLO you want to deploy. Click Actions→Review/Deploy.
NOTE: If HP SUM cannot successfully deploy all updates in a node, it does not reboot the node. View the deployment logs to find and resolve the issue before you reboot the node. 7. 8. HP SUM displays a list of updates that are available. You can select or deselect updates that you don’t want to perform. Click Analysis, and then click Deploy to begin the deployment.
Adding a single node by IP/DNS name a. b. c. d. Select Add a single node by IP/DNS name. Enter the IP address or DNS name. Enter a description for the node. 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: faster. Selecting the correct node type might help HP SUM complete node inventory Some nodes allow you to select the check box so that HP SUM automatically adds Associated Devices.
To add a node by searching a range of IP addresses a. b. c. Select Find nodes on network with an IP range. Click Find Nodes. Enter a range of IP addresses for HP SUM to search, and click Search. HP SUM displays the nodes it finds in the Available Nodes field. d. e. f. Select the nodes you want to add from the Available Nodes section, and then click Add Nodes. If you want to assign a baseline, select a Baseline, Additional Packages in the Baseline to Apply field.
To edit a node 1. 2. From the Nodes screen, highlight the node and then click Actions→Edit. Change the items you want to edit: • Description • Type NOTE: Select the check box if you want HP SUM to automatically add Associated Devices. (Not available for all node types.) • HP SUM displays the currently selected baseline and additional package. Use the drop-down menu if you want to change these.
To deploy a node 1. 2. 3. 4. 5. From the Nodes screen, select a node to update, and then click Actions→Review/Deploy. If you want to change installation options, click Installation Options and then select from the following: • Downgrade: This allows you to downgrade all of the components in the node to an older firmware version without clicking Force for each component in the baseline library list.
To generate a report 1. 2. From the Nodes screen, select a report or multiple reports, and then click Actions→Report. Select the reports you want to generate: • Firmware details: This displays firmware versions that are currently installed on the node. • Deploy preview: This displays components that HP SUM can install on the node. • Failed Dependency details: This displays any failed dependencies on the node. • Last deploy details: This displays details about what HP SUM installed on a node.
NOTE: If you select HP iLO Federation, enter the iLO Federation Group Name that is assigned by HP iLO Federation. Use the username and password for the node IP address you are adding. HP SUM supports adding HP iLO Federation nodes. HP iLO Federation enables you to manage multiple servers from one system running the iLO web interface. HP SUM supports performing inventory on iLO Federation nodes. For more information about HP iLO Federation, see HP iLO 4 User Guide. e. f. g.
HP SUM displays the nodes it finds in the Available Nodes field. d. e. f. Select the nodes you want to add from the Available Nodes section, and then click Add Nodes. If you want to assign a baseline, select a Baseline, Additional Packages in the Baseline to Apply field. 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. 2. Click Add.
NOTE: Select the check box if you want HP SUM to automatically add Associated Devices. (Not available for all node types.) • HP SUM displays the currently selected baseline and additional package. Use the drop-down menu if you want to change these. NOTE: If you want to delete a baseline or additional package, the baseline or additional package cannot be associated with a node. Associate a new baseline or delete the node to delete a baseline. 3.
3. 4. 5. If you want to downgrade or rewrite options to firmware or software only, click Force options can be applied to, and then select from the following: • Firmware: This displays only firmware updates. • Software: This displays only software updates. In the Associated Node Details field, select any nodes that you want to update. In the Baseline Library field, select each component that you want to update. Use the Search box to type in search terms for the components.
3. Click the report format you want HP SUM to generate, HTML, CSV, or XML. NOTE: HP SUM automatically opens the report after it finishes generating the report. If you do not have the format associated to an application, HP SUM prompts you to save the report. 4. Click Generate. Deleting a Virtual Connect 1. 2. 3. From the Virtual Connects screen, highlight the Virtual Connect. Click Actions→Delete. Click Yes, delete.
f. g. 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 Linux and HP-UX 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. NOTE: Super user and sudo are not available for all nodes.
HP SUM displays the nodes it finds in the Available Nodes field. d. e. f. Select the nodes you want to add from the Available Nodes section, and then click Add Nodes. If you want to assign a baseline, select a Baseline, Additional Packages in the Baseline to Apply field. 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. 2. Click Add.
To inventory a node 1. 2. 3. From the Nodes screen, highlight the node and then click Actions→Inventory. Select a baseline, additional package, or both to apply to the node. Click Inventory. Deleting an iLO Federation 1. 2. 3. 68 From the iLO Federation screen, highlight the iLO Federation. Click Actions→Delete. Click Yes, delete.
4 Using legacy scripts to deploy updates Command-line interface You can use the HP SUM command-line interface to script custom installations. Command-line syntax The general command-line syntax for HP SUM is as follows: hpsum [/s] [/h] [/f]:bundle] [/r[eboot] NOTE: On Windows, use a slash before each argument. On Linux, use a hyphen before each argument. For example: hpsum /s /h (Windows) hpsum -s -h (Linux) HP SUM with OA requires a user ID and password to log in.
#Defaults targetpw # ask for the password of the target user. For example, WARNING! • Only use this option with Defaults targetpw. To use super user functionality, configure the user as a super user with all root privileges. You can also use non-root user with a root user to update components. Switch update commands G7 and earlier servers do not support AMS agents. The following tables show what updates occur when you use the switch agent commands.
Installation options Description /f[orce]:all Overrides or downgrades the existing installation of the selected software components, firmware components, and bundles. /g or /downgrade Downgrades to an earlier version of firmware for multi-node devices such as hard drives and array controllers (applies to firmware only). /e or /rewrite Rewrites the current version of firmware for multi-node devices such as hard drives and array controllers (applies to firmware only).
Installation options Description you use /use_location and /c, HP SUM checks both the default repository and the directory provided. /group "group_name" This argument specifies an already defined group name in the HP SUM GUI. /b[undle] or This argument specifies bundles to install. Bundles to install can be specified with or without the /b[undle] argument.
Installation options Description components are optional. This argument does not apply to HP Integrity servers. /use_ams Specifies which AMS components can be installed along with SNMP components. The AMS and SNMP components are available to select by default. When the /use_ams argument is used, the SNMP components are required, and the WMI components are optional. /romonly This filter switch allows you to see only the firmware components needed for installation.
Reboot options Description /r[eboot] If the following conditions are met, this argument causes the server (or host server in a remote installation) to reboot: • The /reboot option is selected or given as a command-line argument. • All components selected for installation are successfully installed. • At least one of the installed components requires a reboot to complete its installation.
Nodes Description /su_password Use root (super user) password to start a session, and inventory and update components when the credentials specified in /username and /passwd do not have root privileges to update components. /su_password cannot be used with /use_sudo access level. NOTE: Specifying /targettype linux reduces inventory time for deployments. This is an optional command line argument. /use_sudo Specifies that username and passwd are sudo user credentials.
Nodes Description /current_credential Enables the credential of the local host to be used as the credential to access the nodes instead of providing the user name and password explicitly for each node. The assumption is that the current credential is valid for the nodes being accessed. (Applies to Windows only) /oa_username This argument provides the user name credential for OA associated with VC specified with the target command-line parameter.
Generating reports Description write-protected, you can find the files in the same directory as the HP SUM log files. /inventory_report Generates a report listing of the components in the specified repository. The report is generated in HTML and XML with file name formats of HPSUM_Inventory_Report__
When HP SUM generates the report, the HP SUM GUI does not appear. When the report is generated, HP SUM displays the report file location. Using input files Description /inputfile “filename” Enables you to script the deployment of firmware and software to multiple remote systems at one time. For more information, see “Input files” (page 81). /deleteinputfile Enables you to instruct HP SUM to delete the input file after it has been read.
Example 4: Either of the following command-line inputs can deploy two software components: • hpsum /f:software cp008097.exe cp008257.exe /s • hpsum /c cp008097.exe /c cp008257.exe /f:software /s Results: The two components were installed. No firmware or other software was installed.
Return code Value Linux Windows Text FAILURE_BAD_PARM -2 254 -2 A bad input parameter was encountered. FAILURE_COMPONENT_FAILED -3 253 -3 The installation of the component failed. Windows smart-component return codes Return code Meaning 0 The smart component was not installed. For more information, see the log file. 1 The smart component was installed successfully. 2 The smart component was installed successfully, but the system must be restarted.
Return code Meaning 4 If the component is being installed to a remote node, such as an OA or other network-based deployment, this return code indicates that the node cannot be found. 5 A user canceled the installation before anything could be installed. 6 The installer cannot run because of an un-met dependency or installation tool failure. 7 The actual installation operation (not the installation tool) failed.
To create an input file, use a text editor. All section headers and trailers must match. You can use the DRYRUN=YES option to perform dry runs of installations to ensure the scripts are working without deploying the firmware updates that might be required on each node. Remove the DRYRUN=YES option to perform the updates. For parameters that can take list values, list separators can be commas, semicolons, or spaces.
File encoding To allow for the inclusion of double-byte characters, the input file is in UTF-8 format. Error reporting If errors occur in the input file, HP SUM exits with a return value of –2 (bad parameter). The details of the location and nature of the error are recorded in hpsum_execution_log__
Parameter Description YES, NO FORCEBUNDLE Enables you to override or downgrade an existing installation of components in the selected bundle. Possible values: YES, NO DOWNGRADE Downgrade to an earlier version of firmware for multi-node devices such as hard drives and array controllers. (Applies to firmware only.) Possible values: YES, NO REWRITE Rewrite the same version of firmware only for multi-node devices such as hard drives and array controllers. (Applies to firmware only.
Parameter Description IGNOREERRORS Causes the installation to continue and ignore errors. The ServerNotFound option can be used to bypass inactive or unavailable remote hosts when deploying firmware or software to multiple remote hosts at the same time. Use FailedDependencies to ignore any failed dependencies and proceed with the ones that are ready to be installed. Possible values: ServerNotFound, BadPassword, FailedDependencies SOURCEPATH Provide a single local baseline path.
Parameter Description These components are only installed by default on Gen8 and later servers. This parameter does not apply to HP Integrity servers. Possible values: YES, NO ROMONLY This is a filter switch that allows you to view only the firmware components required for installation. Do not use the /romonly parameter with the /softwareonly parameter. Possible values: YES, NO SOFTWAREONLY This is a filter switch that allows you to view only the software components required for installation.
Parameter Description Possible values: IP address, DNS name UID Logs in to the nodes with your user ID. Possible values: PWD Uses the password for the user ID specified in the UID. The password is used to log in to nodes. Possible values: LOGFILENAME = "path" Redirects the output from HP SUM or the HP BladeSystem c-Class OA flash utility to a different directory than the default location.
Parameter Description CMASTARTNICAGENT Determines whether the HP Systems Insight Manager NIC agent is started. (Applies to Linux SPP only). Possible values: • YES (start the web agent) • NO (do not start the web agent) CMANOTAINTEDKERNEL Determines whether the HP Lights-Out management driver is started when the health application loads. (Applies to Linux SPP only.
Parameter Description IP address pairs separated by semicolons (for example, 10.1.1.1/255.255.255.0; 10.2.2.2/255.255.255.0) IP-RESTRICTED-LOGINS HP Systems Management Homepage uses this parameter to restrict login access. (Applies to Linux SPP only.) Possible values: YES, NO (default) To enable restrictions on who can log in to the web server, this parameter must be set to yes, and values must be provided to the IP-RESTRICTED-EXCLUDE or IP-RESTRICTED-INCLUDE parameters.
Parameter Description Possible values: • TrustByCert—If you use this value, you must define the CERTLIST parameter to enable access to the server. • TrustByName—If you use this value, you must define the XENAMELIST. • TrustByAll—HP does not recommend using this value because of possible negative security consequences. CAUTION: The accepted values are case-sensitive and must be capitalized as shown.
Parameter Description IGNOREWARNINGS Allows the installation to proceed on a Superdome 2 node even when warnings are returned during analysis. Possible values: YES, NO Superdome 2 servers only UPDATETYPE This argument determines which Superdome 2 firmware is updated. Possible values: ALL, COMPLEX, PARTITIONS Superdome 2 servers only DEVICELIST Use this argument when the UPDATETYPE=PARTITIONS.
Parameter Description REPORT Generates a report listing of the node summary and describes how the components in the repository affect the node; for example, whether each component applies to the node. The report is generated in HTML and XML with file name formats of HPSUM_Report__
HOST = 234.567.765.432 [END] USAGE: hpsum /inputfile Examples of inputfile.txt file: Example: The two nodes are passed to be updated. The nodes do not necessarily have to be OAs. They can be any node that HP SUM supports. DRYRUN = YES SILENT = YES [TARGETS] HOST = BL465C-01 HOST = 192.168.1.2 [END] Example A host DNS is passed along with the user ID and password to use for the hosts in the group.
UID=Userid PWD=password [END] [TARGETS] HOST=16.83.61.48 UID=Userid PWD=password [END] [TARGETS] HOST=16.83.62.196 UID=Userid PWD=password [END] [TARGETS] HOST=16.83.61.24 UID=Userid PWD=password [END] Example: Superdome 2 input files: IGNOREWARNINGS = TRUE [TARGET] HOST = 10.0.0.206 UID = Userid PWD = password UPDATETYPE = PARTITIONS DEVICELIST=npar1,npar2,blade1/4,blade 1/5 REBOOTLIST=npar1,npar2 [END] Usage example of access level. USAGE: hpsum /inputfile
UID = Userid PWD = password [END] [TARGETS] HOST = 10.0.1.73 UID = Userid PWD = password [END] Example: Using super user to update Linux components: SILENT = YES [TARGETS] HOST = 10.0.1.7 UID = Userid PWD = password SUUSERNAME = root SUPASSWORD = rootpwd [END] Example: To update multiple targets using super user in an input file when all targets have the same super user credentials: SILENT = YES SUUSERNAME = root SUPASSWORD = rootpwd [TARGETS] HOST = 10.0.1.
5 Advanced topics Configuring IPv6 networks You can deploy to remote nodes in IPv6-based networks for Windows and Linux node servers. Using HP SUM with IPv6 networks presents challenges for IT administrators. For Windows-based servers, to communicate with remote node servers, HP SUM uses either existing credentials or the user-provided user name and password to connect to the admin$ share. This share is an automatic share provided by Windows Server.
Table 2 HP SUM Windows network ports (continued) Ports Description Ports 445 and 137/138/139 (Port 137 is used only if you are using NetBIOS naming service.) Connects to the remote ADMIN$ share on node servers. These are the standard ports Windows servers use to connect to the remote file shares. If you can connect remotely to a remote Windows file share on the node server, you have the correct ports open. Port 62286 Default for some internal communications.
GatherLogs HP SUM provides a tool that collects all log files into one file. If you are troubleshooting an issue, run gatherlogs. The script is available in the same directory that holds HP SUM.
6 Troubleshooting Collecting trace directories If you need to contact HP for support with an issue, run the GatherLogs utility. GatherLogs is in the same directory as HP SUM. In HP SUM 5.x, HP SUM generates a set of debug trace logs located in the %TEMP%\HPSUM directory on Windows systems. These files contain internal process and debug information which can be useful in determining HP SUM failures. In HP SUM 6.x, the files are stored in the %temp%\HP SUM for 6.x directory. In HP SUM 5.
Debug Trace Files Function is the name of the target in the source selections screen. \Settings.xml Provides general settings information of HP SUM such as Force downgrade or upgrade for a specific target. Log Files Function \hpsum_log.txt Contains information of HP SUM discovery, installation status and errors if any. is the name of the target in the source selections screen. Hpsum_detail_log.txt Contains the log data of the components. hpsum.
HP SUM stops responding when performing inventory on large baselines Solution: Only perform inventory on one large (SPP-size) baseline at a time. Performing inventory on more than one inventory might use too many system resources. HP SUM deletes the baselines and nodes after quitting a Remote Desktop session Solution: This is a known issue with Remote Desktop. For more information, see the article on the Microsoft website: http://technet.microsoft.com/en-us/library/cc755098.
HP SUM displays the message Unable to login or identify node as a supported device when HP SUM cannot find a node Solution: Ping the node to make sure it is on the network. HP SUM might not be able to connect to the node. If the node is running Windows, be sure an $Admin share is enabled. HP SUM displays the message Ready for deployment while HP SUM is performing inventory on a node Solution: Make sure that HP SUM completes an inventory before attempting to deploy updates to a node.
HP SUM cannot downgrade Virtual Connect from 4.10 to 4.01 Solution: Make sure that previous updates are activated before attempting to downgrade the VC. Reset the modules if necessary. Reports troubleshooting HP SUM does not generate reports for nodes that are offline Solution: Verify that HP SUM can ping the node. HP SUM displays only requested reports in CSV and XML format Solution: No action to take. This is the expected result.
windowsdesktop/en-US/d8e7aa2e-95ba-48b5-9ce3-e7cb9f5e57b2/ issues-running-applications-from-network-shares?forum=windowsgeneraldevelopmentissues. Legacy CLI commands troubleshooting HP SUM does not deploy multiple components if all specified separately in one command Solution: Copy the components into a directory and use the /use_location command. If you are deploying more than ten components, use the work around. The /use_web Legacy CLI command does not work Solution: No action. This is a known issue.
7 Console Commands Command keywords are case-insensitive. The mixed casing in this document is for readability. Argument delimiters are those commonly used for each environment or operating system command line, for example / for Windows and - for Linux. The HP SUM binary executable maintains state information as needed on a per-session basis. HP SUM saves this information in the HPSUM_BINARY.ini file. This file is in the C:\ProgramData\ Hewlett-Packard\ location in Windows and your home directory in Linux.
Activate activate enables you to activate updates previously staged or installed. This may involve rebooting or other processes based on specific devices. Syntax hpsum activate [--nodes [nodelist]] [--cancelpending] Parameters The activate command provides the following options: Option Description hpsum The HP SUM script initiates this action. activate The command to activate pending HP SUM updates.
Add add enables you to add baselines or nodes to the current working set for the current session. You can supply passwords for all the nodes or baselines at the beginning of the list. For example, hpsum add --nodes --user userABC --password pwd123 x.x.x.x y.y.y.y NOTE: HP SUM does not automatically add nodes or baselines. Add the nodes and baselines you want to use.
Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful. SUCCESS_NOT_REQUIRED 3 3 The command completed successfully, but was not required or everything was already current. NOTE: The node or baseline already existed. FAILURE_GENERAL -1 255 A general failure occurred. For details, see the logs. FAILURE_BAD_PARM -2 254 A bad input parameter was encountered. For details, see the logs. FAILURE_COMMAND_FAILED -4 253 The command failed.
Option Description --nodes [nodelist] Object to perform the delete operation. Delimit the list with a space. If you do not provide a nodelist, all nodes are deleted. --baselines [baselinelist] Object to perform the delete operation. Delimit the list with a space. If you do not provide a list of baselines, all baselines are deleted. Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful.
Option Description ip: 127.0.0.1 ipv6: ::1 If you do not provide a nodelist, all nodes in the session are deployed. Enables deploying for a group. --groups grouplist Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful. SUCCESS_REBOOT 1 1 The command was successful but a reboot is required. SUCCESS_NEW_SESSION_REQUIRED 2 2 The command was successful but an additional installation session is required to complete the update process.
Parameters The findavailablenodes command provides the following options: Option Description HPSUM The HP SUM script initiates this action. findavailablenodes The command to find all nodes available for updates through HP SUM. --type ip|LDAP|port If you pass the type option, the value must match one of three types: 1. ip Options: ipAddrLow; ipAddrHi 2. LDAP Options: ldapServer; username; ** interactive prompt for password 3.
Parameters The generatereports command provides the following options: Option Description hpsum The HP SUM script initiates this action. generatereports The command to generate reports within the HP SUM session. --type inventory | firmware | installables If you specify the type parameter, it must be one of the | faileddep | installed | combined following: • Inventory • Firmware • Installables • Faileddep • Installed • Combined If you do not provide a type, all types possible are generated.
Syntax hpsum getattributes Parameters The getattributes command provides the following options: Option Description HPSUM The HP SUM script initiates this action. getattributes The command to show attributes for the selected nodes. --nodes [nodelist] A list of the nodes for which to get the attributes. If you do not specify a nodelist, all nodes in the session are shown. Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful.
Option Description location [/details] Baseline location to use for performing the operation. Specify [/details] to get detailed baseline information. list hp.com This parameter retrieves the list of available baselines from ftp.hp.com Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful. FAILURE_GENERAL -1 255 A general failure occurred. For details, see the logs. FAILURE_BAD_PARM -2 254 A bad input parameter was encountered.
Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful. FAILURE_GENERAL -1 255 A general failure occurred. For details, see the logs. FAILURE_BAD_PARM -2 254 A bad input parameter was encountered. For details, see the logs. FAILURE_COMMAND_FAILED -4 252 The command failed. For details, see the logs. Example Windows sample command line C:\> hpsum getcomponentlogs /nodes localhost Linux/HP-UX sample command line $ hpsum getcomponentlogs --nodes 16.1.
Example Windows sample command line C:\> hpsum getcurrentlyinstalledversions /nodes localhost Linux/HP-UX sample command line $ hpsum getcurrentlyinstalledversions --nodes localhost GetEngineStatus Enables you to query the status of the HP SUM Engine. getenginestatus enables you to retrieve the status information session manager. Syntax hpsum getenginestatus Parameters The getenginestatus command provides the following options: Option Description hpsum The HP SUM script initiates this action.
Parameters The getlogs command provides the following options: Option Description hpsum The HP SUM script initiates this action. getlogs The command to get the current trace logs. Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful. FAILURE_GENERAL -1 255 A general failure occurred. For details, see the logs. FAILURE_BAD_PARM -2 254 A bad input parameter was encountered. For details, see the logs.
Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful. FAILURE_GENERAL -1 255 A general failure occurred. For details, see the logs. FAILURE_BAD_PARM -2 254 A bad input parameter was encountered. For details, see the logs. FAILURE_COMMAND_FAILED -4 252 The command failed. For details, see the logs.
Example Windows sample command line C:\>hpsum getnodes 16.157.90.123 /details Linux/HP-UX sample command line $ hpsum getnodes 16.157.90.123 --details Inventory inventory enables you to scan nodes for the currently installed version of firmware, drivers, and hardware components. If no nodes are specified, the default setting is all nodes in the current session.
Syntax Authenticating with credentials for the first time: hpsum login [--username rono --password pwd123 --port 63001 --ssl_port 63002] Authenticating with current credentials: hpsum login Parameters Option Description hpsum The HP SUM script initiates this action. login The command to set credentials for the HP SUM session. username, password Optional parameters Return codes Return code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful.
Parameters The setattributes command provides the following options: Option Description hpsum The HP SUM script initiates this action. setattributes The command to set attributes pending HP SUM operations. --nodes [nodelist] [attribute=value] Section for attributes that you want to apply to nodes. If you do not specify a nodelist, this sets the attribute for all nodes in the session. Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful.
Return codes Return Code Windows Linux Text SUCCESS_NO_REBOOT 0 0 The command was successful. FAILURE_GENERAL -1 255 A general failure occurred. For details, see the logs. FAILURE_BAD_PARM -2 254 A bad input parameter was encountered. For details, see the logs. FAILURE_COMMAND_FAILED -4 252 The command failed. For details, see the logs.
8 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
http://www.hp.com/go/spp/download For information about HP Subscriber's Choice, see the Subscriber's Choice website: http://www.hp.com/go/subscriberschoice For information on the HP Systems Insight Manager, see the following documents on the HP Systems Insight Manager website: http://www.hp.
event notifications to HP, which will initiate a fast and accurate resolution, based on your product’s service level. Notifications may be sent to your authorized HP Channel Partner for onsite service, if configured and available in your country. For more information, see HP Insight Remote Support and Insight Online Setup Guide for ProLiant Gen8 Servers and BladeSystem c-Class Enclosures on the HP website (http://www.hp.com/go/ enterprise/docs).
9 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Glossary AMS Agentless Management Service Analyze The process where HP SUM verifies all dependencies before deploying updates Baseline A set of updates for your hardware CPLD complex programmable logic device Deploy The process where HP SUM begins the update process by installing the component update files to the node.
Index A abort update enclosure, 35 iLO, 53 iPDU, 58 servers, 40 switch, 44 Virtual Connects, 63 VM host, 49 activity, 19 add baseline, 22 adding enclosures, 33 iLO, 51 iLO Federation, 65 iPDU, 55 node, 26 servers, 37 switch, 42 Virtual Connects, 60 VM Hosts, 46 advanced topics, 96 appliance describing icons, 10 arguments, 70 B baseline adding, 22 create custom, 23 delete, 24 reports, 23 baselines, 21 C CLI (Command Line Interface) Command-line arguments, 70 Command-line examples, 78 Command-line interface
adding, 33 edit, 35 files, creating input Input file format and rules, 82 Input files, 81 edit, 57 inventory, 58 report, 59 ipdu delete, 60 IPv6 network configurations Configuring IPv6 networks with HP SUM, 96 G L GUI using, 19 launching HP SUM, 12, 17 Linux, 18 Windows, 18 Linux RPM return codes, 81 Linux smart components, return codes, 80 Localhost Guided Update, 19 logging in, 18 logging off, 18 F H health icon, 10 help obtaining, 123 HP technical support, 123 HP Insight Online, 125 I icon descr
VM host, 50 reports node, 31 return codes Linux RPM return codes, 81 Return codes, 79 VMware ESXi return codes, 81 return codes, Linux smart components, 80 return codes, VMware ESXi, 81 return codes, Windows smart components, 80 RPM return codes, Linux, 81 running HP SUM, 14 S screen components, 10 scripted deployment, 69 servers, 37 abort update, 40 adding, 37 delete, 42 deploy, 40 edit, 39 inventory, 40 report, 41, 46 shutting down HP SUM, 18 status icon, 10 switch abort update, 44 adding, 42 delete, 46
