HP Smart Update Manager User Guide

Transcription

1 HP Smart Update Manager User Guide Abstract This guide is intended for individuals familiar with the configuration and operation of Microsoft Windows, Windows Server, Linux, smart components, and deployment of firmware and software. Because of the risk of data loss, only individuals experienced with using firmware and software should implement the procedures. HP Part Number: a Published: January 2013 Edition: 6a

2 Copyright 2009, 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , 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. Acknowledgments Microsoft, Windows, Windows Vista, and Windows Server are U.S. registered trademarks of Microsoft Corporation.

3 Contents 1 Introduction...6 HP SUM overview...6 Deploying HP SUM...7 Running HP SUM...7 Deploying firmware for ProLiant servers using the Service Pack for ProLiant...9 HP SUM supported firmware for ProLiant servers...10 Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD...10 Deploying Integrity firmware bundles with HP SUM...11 HP SUM supported firmware for Integrity servers...11 Deployment modes...11 Deployment scenarios...12 Trusted Platform Module Using the HP SUM GUI...15 Keyboard support...15 Source selections...15 Setting Proxy Server options...16 Using multiple repositories...17 Adding the repository...17 Editing the repository...18 Removing the repository...18 Configuring the components...18 Downloading components for target discovery...19 Updating mixed ProLiant and Integrity environments...19 Selecting the targets...20 Inter-target dependency...21 Dependency checking...21 Target types...21 Finding and discovering targets...22 Adding a single target...22 Entering target credentials...22 Editing a target...22 Removing a target...23 Managing groups...23 Pending firmware updates for ilo (HP Integrity servers only)...23 Reviewing and installing updates...24 Installing updates...25 Aborting an installation...25 Viewing failed dependencies...25 Selecting bundles...25 Selecting components...26 Selecting devices...27 Viewing firmware details...27 Viewing firmware mismatch details (HP Integrity servers only)...28 Installation options...28 Reboot options...29 Scheduling updates...29 Generating and viewing reports...29 Generating a Report...29 Viewing a report...30 Contents 3

4 3 Using scripts to deploy updates...31 Command-line interface...31 Command-line syntax...31 Switch update commands...31 Command-line arguments...33 Component configuration for Windows components only...39 Command-line examples...40 Return codes...41 Windows smart-component return codes...41 Linux smart-component return codes...42 Linux RPM return codes...42 Input files...43 Input file format and rules...43 File encoding...44 Error reporting...44 Input file parameters...44 Reports Advanced topics...55 Configuring IPv6 networks...55 Configuring IPv6 for Windows Server Configuring IPv6 for Windows Server Configuring IPv6 for Linux...56 Network ports used by HP SUM Troubleshooting...59 Recovering from an installation failure...59 Collecting trace directories...59 Recovering from a discovery failure...60 Troubleshooting connection errors...60 HP SUM hangs during discovery...61 HP SUM hangs during boot...61 Recovering from a loss of Linux remote functionality...61 Configuring firewall settings...61 Recovering from a blocked program on Microsoft Windows...62 Configuring Windows firewall settings...62 Recovering from operating system limitations when using a Japanese character set...62 Displaying the user-specified reboot message using a Japanese character set when running on a Linux operating system...62 Rebooting with the user-specified reboot message using a Japanese character set when running on a Windows operating system...62 Running in a directory path containing multi-byte characters...62 Recovering a lost HP SUM connection...63 HP Smart Update Firmware DVD and SPP mounted using ilo virtual media...63 Troubleshooting HP SUM in IPv6 networks...63 Troubleshooting HP SUM in IPv6 Windows Server 2003 environment...63 Troubleshooting HP SUM in IPv6 Windows Server 2008 environment...64 Troubleshooting HP SUM in IPv6 Red Hat and Novell SUSE-based Linux environments...64 Microsoft Windows displays a Found new hardware message...65 Non-matching systems error reported when building source Linux RPMs or installing Linux RPMs built from source...65 Linux component version discrepancy for source RPMs...65 HP SUM displays No components found in the selected repository(ies) message...65 Installation of components failed with 'Update returned an error' when installing Linux RPMs...65 HP SUM fails on Windows hosts due to McAfee firewalls Contents

5 HP SUM prevents an upgrade of Virtual Connect firmware if the VC health is invalid or bad health state...67 Downgrade of ProLiant G6 Server ROM from or later to or earlier using HP SUM is not supported...68 ProLiant G2, G5, and G6 Servers - After Upgrading to the May 2011 (or Later) Revision of the System ROM, Special Steps Must Be Performed if it Is Necessary to Downgrade the System ROM to Revisions Earlier Than May Support and other resources...69 Information to collect before contacting HP...69 How to contact HP...69 Subscription service...69 Documentation feedback...70 Related information...70 Typographic conventions...71 HP Insight Remote Support software Documentation feedback...73 Acronyms and abbreviations...74 Index...75 Contents 5

6 1 Introduction HP SUM overview HP SUM is a technology included in many HP products for installing and updating firmware and software components on HP ProLiant and HP Integrity servers, enclosures, and options. HP SUM provides a GUI and a command-line scriptable interface for: Deployment of firmware for single or one-to-many ProLiant and Integrity servers and network-based targets such as ilos, OAs, and VC Ethernet and Fibre Channel modules. Deployment of software for single or one-to-many ProLiant servers (supported in Windows and Linux environments) and Integrity servers. 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 target servers. This capability prevents extraneous network traffic by sending only the required components to a target host. HP SUM installs updates in the correct order and ensures that all dependencies are met before deploying an update. HP SUM prevents an installation if there are version-based dependencies that it cannot resolve. HP SUM does not require an agent for remote installations, because it copies a small, secure SOAP server to the target for the duration of the installation. After the installation is complete, the SOAP server and all remote files associated with the installation, except installation log files, are removed. HP SUM copies the log files from the remote targets back to the system where HP SUM is executed. Key features of HP SUM include: Dependency checking, which ensures appropriate installation order and dependency checking between components Intelligent deployment of only required updates Simultaneous firmware and software deployment for multiple remote targets in both GUI and CLI modes Improved deployment performance Local or remote (one-to-many) online deployment of ProLiant and Integrity server and enclosures Local offline firmware deployments with the earlier HP Smart Update Firmware DVD or HP Support Pack for ProLiant deliverables Remote offline deployment when used with the SmartStart Scripting Toolkit (G7 and earlier servers), Scripting Toolkit (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 modules, and 3Gb/6Gb SAS BL Switch interconnects on ProLiant servers Support for deploying firmware updates to supported Integrity servers and Superdome 2 enclosures Support for updating VC modules on Integrity servers NOTE: HP SUM does not support third-party controllers. This includes flashing hard drives behind these controllers. 6 Introduction

7 Deploying HP SUM The following sections discuss deployment from HP SUM. For more information on planning an update, see the HP ProLiant Firmware Management Best Practices Overview, HP ProLiant Firmware Management Best Practices Planning Guide, or HP BladeSystem ProLiant Firmware Management Best Practices Implementer Guide, available on the HP SUM documentation website at NOTE: HP SUM stores host and group information from session to session. However, user names, passwords, and existing credentials are not stored in a session or from session to session. Running HP SUM HP SUM provides three ways of running for users: GUI For firmware and software deployments Express For software deployments only (local host only) Scripted For silent firmware and software deployments HP SUM supports local and remote deployments. HP SUM runs in standard Windows and Linux operating systems in online and offline mode. For more information about deployment modes, see Deployment modes (page 11). NOTE: You cannot use Windows Hyper-V systems to deploy updates. You can select Hyper-V systems as a target from HP SUM. Use the following table to determine the correct execution mode for the server use case. NOTE: Before deploying software updates to a target server, be sure that a recent backup of the target server is available in the event the deployment procedure fails. Deploying HP SUM 7

8 Scenario Description HP SUM command HP deliverable Interactive, graphical Use this scenario when you: Windows: deployment on a local host Are not familiar with hpsum Run HP SUM on the server command line tools being updated. Linux: Are deploying components on a local,./hpsum single host Do not require scripting Want to select the components to be installed Online: HP Smart Update Firmware DVD HP Service Pack for ProLiant Offline: HP Smart Update Firmware DVD HP Service Pack for ProLiant Scripted deployment on a Use this scenario when you: Windows: local host Are familiar with hpsum -s Run HP SUM from a network command line tools share on a local server. Linux: Are deploying components on a local,./hpsum -s single host Must perform a customized, scripted deployment Are unable to unlock the required HP SUM network ports for remote deployment Interactive, graphical Use this scenario when you: Windows: deployment to a remote host Are not familiar with hpsum Run HP SUM from a command line tools workstation and update Linux: Do not require scripting remote hosts over the./hpsum network using the GUI. Want to select the components to be Targets can be a installed Windows, Linux, or VMware ESXi 5.0 server, OA, ilo, or VC IP address or DNS name. Need to update multiple targets including OA, VC, and server-based firmware NOTE: HP SUM can Need to select individual firmware to update Need to select individual hardware devices to be updated Need to target VMware host servers detect updates that are available for a VMware server and generate reports, it cannot deploy updates. Online: HP Smart Update Firmware DVD HP Integrity bundles HP Service Pack for ProLiant Offline: None Online: HP Service Pack for ProLiant Smart Update Firmware DVD HP Integrity Support bundles HP Integrity BL8x0c i2, rx2800 i2 and Superdome 2 Servers Bundles for Windows and Linux Offline: None Scripted deployment to a remote host Run HP SUM from a workstation and update a remote host over the network using scripts. Use this scenario when you: Are familiar with command line tools Must perform a customized, scripted deployment Need to update multiple targets including OA, VC, and server-based firmware Windows: hpsum -s -target Target1 -target Target2 -username User1 -password PW1 Linux:./hpsum -s -target Target1 -target Online: HP ProLiant Support Pack for Windows and Linux HP Smart Update Firmware DVD HP Integrity Support Pack for Windows 8 Introduction

9 Scenario Description HP SUM command HP deliverable Need to update all enclosure firmware Need to target VMware host servers Target2 -username User1 -password PW1 HP Integrity BL8x0c i2, rx2800 i2, and Superdome 2 Servers Bundles for Windows and Linux HP Service Pack for ProLiant Offline: SmartStart Scripting Toolkit (G7 and older) Scripting Toolkit (Gen8 and older) Automatic Deployment to one or more servers in a HP BladeSystem enclosure Use the HP Smart Update Firmware DVD or HP SPP with embedded HP SUM to deploy firmware updates to one or more blades automatically. Use this scenario when you: Do not have an operating system installed on a server blade Want an automatic way to deploy firmware updates Do not require log files or user interaction with the installation process Want to update multiple blades in an enclosure in a single operation The HP SPP and Smart Update Firmware DVD take care of this automatically Online: None Offline: HP Smart Update Firmware DVD HP Service Pack for ProLiant Update an existing enclosure The same scenario as shown Windows: manually in the Interactive, graphical deployment to a remote hpsum For more information, see the HP CloudSystem Matrix host or Scripted Linux: Compatibility website at deployment to a remote host scenarios discussed./hpsum matrixcompatibility. previously in this table Online: HP Smart Update Firmware DVD HP Service Pack for ProLiant Offline: HP Smart Update Firmware DVD HP Service Pack for ProLiant Deploying firmware for ProLiant servers using the Service Pack for ProLiant SPP is a re-packaging of HP ProLiant system software and firmware for ProLiant ML/DL/SL servers and their options, and BladeSystem enclosures including OA,VC, and 3 GB SAS switches running supported Windows, Linux, and VMware operating systems. The single SPP image contains a comprehensive collection of firmware and system software components including drivers, agents, non-agents, utilities, and firmware that is tested, managed, and deployed together as a single solution. NOTE: HP SUM can detect updates that are available for a VMware server and generate reports, it cannot deploy updates. SPP includes HP SUM for deployment of the SPP components. For a complete list of HP ProLiant systems and software supported by SPP, see the HP Service Pack for ProLiant Release Notes on the HP SPP website at Deploying HP SUM 9

10 HP SUM supported firmware for ProLiant servers Component System ROM ilo 2 firmware Broadcom NIC firmware Intel NIC firmware NetXen NIC firmware, QLogic NIC firmware PowerPIC firmware Smart Array controller firmware SAS and SATA hard drive firmware behind Smart Array controllers SAS and SATA hard drive firmware behind non-smart Array controllers Emulex, QLogic, and Brocade Fibre Channel HBA firmware Tape Blade firmware OA firmware VC firmware CPLD firmware HP StorageWorks MDS 600 enclosure firmware MSA 2000 firmware (P2x00 firmware) D2600/D2700 firmware 3Gb/s and 6 Gb/s SAS BL switches FCoE/CNAs SES firmware Supported Yes Yes, both server-based and directly to the ilo Management NIC port Yes Yes Yes, online Yes, beginning with bundle 1.60 and later Yes Yes, some older SATA hard drives require offline mode No Yes Yes Yes, online only Yes, online only Yes Yes No Yes, when attached through a Smart Array controller Yes, online only Yes Yes Deploying firmware for ProLiant servers using the HP Smart Update Firmware DVD 10 Introduction The HP Smart Update Firmware DVD provides a collection of firmware bundles containing HP SUM and firmware for ProLiant servers in an ISO image that can be used either in offline (automated or interactive mode), or online (a scripted or interactive mode) modes. The HP Smart Update Firmware DVD provides firmware for supported ProLiant servers and options. The Firmware DVD contains all the firmware for the supported ProLiant servers including BladeSystem enclosures and Virtual Connect firmware. In offline mode, the Smart Update Firmware DVD boots a small Linux kernel and enables firmware updates to occur on a single server using HP SUM. In online mode, users can leverage the autorun utility to launch HP SUM or browse the DVD to the \hp\swpackages directory and then execute it directly. All firmware smart components are placed in the \hp\swpackages directory for use by HP SUM. If additional firmware smart components are required, then the HP Smart Update Firmware DVD can be copied to a USB key, and these additional components added to the \hp\swpackages directory. IMPORTANT: Before deploying firmware updates to a target server, be sure that a recent backup of the target server is available in the event the deployment procedure fails.

11 For more information about deploying firmware on ProLiant servers, see the HP Service Pack for ProLiant User Guide on the HP SPP website at Deploying Integrity firmware bundles with HP SUM You can use HP SUM to deploy components delivered with the Integrity Server Bundles, or use HP SUM to pull updates from the web. Deploying firmware to the Integrity servers is done remotely and is the same as deploying other firmware, such as OA, with the following exceptions: You should specify the IP address of the Monarch (primary) OA on Superdome 2 enclosures, or the Monarch ilo 3 MP on multi-blade servers. On the Select Components screen, click Configure Now, and then select whether you want to Upload and Activate or Upload but Do Not Activate. The Upload and Activate option automatically powers down and reboots the server after the update finishes, which activates the firmware. If you select the Upload but Do Not Activate option, the server does not automatically reboot, so you must either manually reboot or wait for the next regularly-scheduled maintenance reboot for the firmware to be activated. By default, SUM selects Upload but Do Not Activate. HP SUM supported firmware for Integrity servers Component Online System ROM firmware FPGA firmware ilo-3 MP firmware Power Monitor firmware Superdome 2 Complex and npartition firmware OA firmware VC firmware Supported Yes Yes Yes Yes Yes Yes Yes Deployment modes The following key terms are used when using HP SUM to deploy updates: Term Local Remote Online Definition The installation runs on the physical hardware you are updating. For example, running a utility on a server to update the server's system ROM. The installation runs on one system, but updates other physical targets. For example, updating the OA firmware across a network through a web browser. The installation occurs while the host processor is running in the normal server environment. For example, if the server runs Microsoft Windows Server 2008, the update takes place under this environment. The update does not require you to boot to a special environment to update the Deploying HP SUM 11

12 Term Definition firmware. You might need to reboot the target to activate the firmware. Offline 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 repository 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 firmware and software on a local host or one or more remote hosts. If the host running HP SUM is using a Windows operating system, you can update Windows, Linux, or VMware target. HP Integrity servers can be running HP-UX or other operating systems, but the updates are driven by a Windows or Linux workstation that performs the updates through the ilo or OA. NOTE: HP SUM can detect updates that are available for a VMware server and generate reports, it cannot deploy updates. 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. Graphical deployment to a remote host You are not familiar with command line tools. You are deploying components on one or more remote hosts. Updates do not require scripting. Scripted deployment to a remote host You are familiar with command line tools. Trusted Platform Module You are deploying components on one or more hosts. Updates require a customized, scripted deployment to one or more host systems. The TPM, when used with BitLocker, measures a system state and, upon detection of a changed ROM image, restricts access to the Windows file system if the user cannot provide the recovery key. HP SUM detects if a TPM is enabled in your system. If a TPM is detected in your system or with any remote server selected as a target, for some newer models of ProLiant servers, HP SUM utilities for HP ilo, Smart Array, NIC, and BIOS warn users prior to a flash. If the user does not 12 Introduction

13 temporarily disable BitLocker and does not cancel the flash, the BitLocker recovery key is needed to access the user data upon reboot. A recovery event is triggered if: 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. To enable firmware updates without the need to type in the TPM password on each server, the BitLocker Drive Encryption must be temporarily disabled. Disabling the BitLocker Drive Encryption keeps the hard drive data encrypted. However, BitLocker uses a plain text decryption key that is stored on the hard drive to read the information. After the firmware updates have been completed, the BitLocker Drive Encryption can be re-enabled. Once the BitLocker Drive Encryption has been re-enabled, the plain text key is removed and BitLocker secures the drive again. NOTE: Temporarily disabling BitLocker Drive Encryption can compromise drive security and should only be attempted in a secure environment. If you are unable to provide a secure environment, HP recommends providing the boot password and leaving BitLocker Drive Encryption enabled throughout the firmware update process. This requires 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: Trusted Platform Module 13

14 The following table describes TPM detection scenarios that you might encounter. Scenario 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. Result 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). Because the installation is silent, the installation is terminated and cannot continue. If TPM is detected and enabled with Option ROM Measuring, the installation is not silent, and a system ROM must be updated. A warning message appears. After selecting OK, you can continue. The installation is not canceled. If TPM is detected and enabled with Option ROM Measuring, the installation is silent; the /tpmbypass switch the installation is silent, the installation is terminated and cannot continue. is not given, and any firmware updated must be applied to the server. If TPM is detected and enabled, the installation is silent, The installation occurs. and the /tpmbypass switch is supplied. 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. 14 Introduction

15 2 Using the HP SUM GUI Keyboard support The HP SUM GUI has accelerator keys that enable you to manage and control common tasks quickly. To ensure proper navigation, the following are a few reminders. Press ALT to see the task corresponding to the underlined letter. The accelerator keys work by pressing ALT + the underlined letter. Press Space to select items such as hosts or groups. Press Tab to select from a list, and then press the arrow keys to toggle radio buttons. Source selections Repositories are the directories that contain the SPP, bundles, and individual smart components HP SUM uses to update targets. Bundles are groups of firmware and software components that HP releases. HP SUM allows you to choose one or more repositories and check the HP FTP site for the latest versions of the components. NOTE: If more than one repository contains the same component, HP SUM uses the component located in the repository closest to the top of the Current Repositories table. Keyboard support 15

16 Current Repositories table The Current Repositories table displays: Name This field displays the repository name. Select the repositories you want to use by clicking the checkbox next to the repository name. If you want to edit a repository, highlight the entire line to activate the Edit and Remove buttons. HP SUM automatically creates a repository named Default and scans it for updates. This repository is the folder that holds the HP SUM application. The HP FTP site (ftp://ftp.hp.com) contains the latest versions of the firmware and software components available from HP. The components are available for selection on the Review/Install Updates screen. When using this method, both firmware and software components are available for selection. The components are not downloaded from ftp.hp.com to a target until the Install button is clicked unless the component is needed to discover supported devices. If components are needed for discovery, you are prompted to allow this action. The ftp.hp.com check box is cleared by default. To pull updates from the web, click the ftp.hp.com check box. If HP SUM has downloaded a component, HP SUM does not download it again. This repository cannot be edited except to set the repository filter. Use the last downloaded repository from the HP FTP site This option includes the components that have been previously downloaded from the ftp.hp.com site. To use components downloaded from the HP website, select this check box. The repository cannot be edited. Location This field displays the location of the repository. Addition Information This field provides more information about the bundle. Click Proxy Options in this field to change proxy settings if necessary to access ftp.hp.com. Status This field displays the repository's contents, and if you need to configure any components in the repository. Click Repository Contents to view the contents of the chosen repository. Click the version link to view the description, installation notes, enhancements and fixes, and version history of the component or bundle. Click Configure Components to select components to configure. This option is available only for a local repository with components that require configuration. NOTE: HP SUM does not display Configure Components if the HP SUM and the components are on read-only media. NOTE: The check box by the repository name selects whether the updates are used during an update; it does not select the row for editing or removal. Setting Proxy Server options Proxy server information may be needed to allow HP SUM to access ftp.hp.com to determine if updates are available and needed. 1. On the Source Selections screen, click Proxy Options in the Current Repositories table. The link is in the Additional field of the Check for Latest Updates from ftp.hp.com row in the table. 2. In the Enter the Proxy Details dialog box, check Use Proxy server details. 16 Using the HP SUM GUI

17 3. Select Server or Script. If you chose Server, enter the server IP Address and Port information. If you chose Script, enter the script location in one of the following ways: Click Detect Proxy to automatically add the default location of the configuration script. Manually enter the address. 4. Enter the User ID and Password (if necessary). 5. Click OK. Using multiple repositories HP SUM allows you to select one or more repositories when selecting components to be installed. You can have a different filter set for each repository. Be aware of the following items: HP SUM uses the highest version of a bundle or component it finds in any of the selected repositories. If the same highest bundle or component version is found in multiple repositories, HP SUM uses the version listed highest on the Current Repositories table. If a component is located in both a local repository and it is also on ftp.hp.com, HP SUM uses the local version. Adding the repository If the default repositories do not include the component or bundle updates: Source selections 17

18 1. Click Add Repository, and then choose Firmware Only, Software Only, or Both. You can choose the updates to use when you add or edit a repository. By default, HP SUM displays firmware and software updates. If you want to view which updates are being used in an existing repository, select the repository in the Current Repositories table, and then click Edit Repository. Both - HP SUM displays component firmware and software updates that are ready. Firmware only - HP SUM only displays component firmware updates that are ready. Software only - HP SUM only displays software firmware updates that are ready. NOTE: If you select firmware or software only, you might not have any updates to apply to a device on the Select Bundles or Select Components screens. 2. Enter an optional name for the repository in Repository Name. 3. Click Browse to open a navigation window, or enter the path to the directory that holds the updates in Repository Location. 4. Click OK. Editing the repository You can edit a repository to change its name or location, or to filter the repository s updates. 1. If you want to change the name of a repository, select the line of the repository you want to edit, and then click Edit Repository. NOTE: The check box by the repository name controls whether a repository is used in updates; it does not select the row for editing or removal. 2. Edit the Repository Name. 3. Select Firmware Only, Software Only, or Both. You can choose the updates to use when you add or edit a repository. By default, HP SUM displays firmware and software updates. If you want to view which updates are being used in an existing repository, select the repository in the Current Repositories table, select the repository in the Current Repositories table, and then click Edit Repository. Both - HP SUM displays component firmware and software updates that are ready. Firmware Only - HP SUM only displays component firmware updates that are ready. Software Only - HP SUM only displays software firmware updates that are ready. NOTE: If you select firmware or software only, you might not have any updates to apply to a device on the Select Bundles or Select Components screens. Removing the repository 1. Select the repository you want to remove by clicking its row in the table to highlight it. NOTE: The check box by the repository name controls whether a repository is used in updates; it does not select the row for editing or removal. 2. When the correct row is highlighted, click Remove Repository. 3. Click Yes if you want to remove the repository, click No to cancel. Configuring the components Some components might have required or optional configuration settings. Configuration parameters can include information necessary to set up the component correctly or passwords required for 18 Using the HP SUM GUI

19 software installed by the component. The configuration is stored within the component and is propagated to all targets. If the optional configuration data of a component is not provided and the component has not been installed previously, then default values for that configuration data are used. If the component has been previously installed and configured and no changes are made to the configuration data, then the existing configuration information is preserved. Component configuration requires that Smart Components are in a write-accessible location. A CD, DVD, or read-only network share is not supported. Components you can configure are indicated in the Status column on the Select Sources screen. 1. Click Configure Components, select the component you want to configure, and then click Configure. 2. Follow the instructions when the Item Configuration screen appears. 3. When you finish configuring all the components, click OK to return to the Source Selections screen. NOTE: If more than one repository contains the same component, HP SUM only uses the component located in the repository closest to the top of the Current Repositories table. Downloading components for target discovery If you select to pull updates from the web, when you click Next on the Source Selections screen you see the Download Permissions screen. This list includes both Linux and Windows components used for target discovery. If your environment does not include targets running the Linux or Windows operating system, you can remove these components from the list to reduce the number of components that HP SUM downloads to your system. Updating mixed ProLiant and Integrity environments If you are updating an environment with both ProLiant and Integrity servers, do the following: Review the support matrix. Be sure to use OA and VC versions supported by both ProLiant and Integrity servers. For more information, see the HP BladeSystem Release Sets for Mixed ProLiant and Integrity website at mixed-release-sets.html. Download the latest HP SPP version and HP Integrity bundles. NOTE: You can also use the Check for Latest Updates from ftp.hp.com function in HP SUM. Unzip the HP SPP and Integrity bundle in separate directories. In HP SUM, make sure that you have added both the HP SPP and HP Integrity bundle. NOTE: Use the latest version of HP SUM that was included in the SPP or Integrity bundle you downloaded. You must use HP SUM version or later. Perform your updates, making sure you do not update the OA or VC to a version not listed in the support matrix. Source selections 19

20 Selecting the targets The Select Targets screen automatically detects the local system running HP SUM and adds it to the targets list. To find new targets, click Find Targets or Add Single Target. For more information, see Finding and discovering targets (page 22) or Adding a single target (page 22). If you have an enclosure that has different target types that share credentials and need to be updated at the same time, create a group to manage them. For more information on creating and editing groups, see Managing groups (page 23). The table displays the following target information: Check box Targets with selected check boxes are updated. Click the check box to select or clear a target for update. Target Name This field displays the IP address of the target or group. Status This field displays a message indicating whether or not the target is ready to be updated. Enter the credentials for each target you are updating. For more information, see Entering target credentials (page 22). NOTE: The target status Ready means that HP SUM can detect the target, and is able to take inventory of the target. No analysis occurs until you click Next. Last Updated This field displays the last time the target was updated. Associated Targets This field displays the associated devices of the target. 20 Using the HP SUM GUI

21 Description This field displays the description of the target. Type This field displays the type of target (for example, ilo or Onboard Administrator). NOTE: For HP SUM to discover a Broadcom NIC during an online update, you must bring the NIC up in Linux. From a command line, enter # ifup ethx or # ifconfig ethx up. Inter-target dependency HP SUM finds potential targets by checking the OA host server list for all targets you add. HP SUM asks you if you want to add the potential targets it found, and does dependency checking for these servers. Dependency checking Target types Dependency checking is an integral function of creating a supported configuration before HP SUM deployment. During this process, HP SUM ensures that the requirements for a component or target update are met. These include system requirements (for example, libraries and services) for the component, target, or associated devices of the target have compatible software and firmware revisions. This process is initiated automatically and silently after the HP SUM discovery process and it involves: 1. Checking the dependencies of component /target/ or devices associated with targets. Examples of dependency checking include: Health component requirement for installation of the SNMP Agents Required operating system libraries Compatibility of OA, VC, and ilo firmware versions 2. Indicating if there is a dependency failure. Failures are displayed in the HP SUM GUI, and also saved in a log file. To resolve any dependencies that were indicated during this process, review the logs and correct the failures. After resolving the dependencies, restart the HP SUM application. NOTE: For Superdome 2 servers that do not support online firmware updates, power down all Superdome 2 partitions in the complex. If you do not power down all the partitions, a Failed Dependencies error appears. On the Select Devices screen, click Ignore Warnings, and HP SUM powers down the partitions for you after you begin the installation process. Supported target types include: Server a local host or a remote server ilo Onboard Administrator Virtual Connect Superdome 2 Onboard Administrator VMware Host NOTE: HP SUM can detect updates that are available for a VMware server and generate reports, it cannot deploy updates. NOTE: Only supported for remote installation and requires the HP CIM providers installed. HP SAS B/L Interconnect Switch Selecting the targets 21

22 Finding and discovering targets 1. Click Find Targets. 2. Select IP Address Range, Port Address, or LDAP Scan for Remote Targets, and then click OK. IP Address Enables you to search a range of IP addresses in IPv4 or IPv6 format. Enter the required address range information, click Search, select the target, and then click Add to List. NOTE: HP SUM searches only c-class IP addresses, and a maximum of 255 targets. For example, you can search for IP address through , but HP SUM does not support searching ports through Port Address Enables you to search in a range of IP addresses and specific port address. LDAP Scan for Remote Targets Enables you to search for targets using an LDAP query. Adding a single target 1. Click Add Single Target. 2. Type the IP or DNS address of the target. 3. Select the type of target from the dropdown list (optional). If you leave this field as the default setting, HP SUM detect the type of target during the discovery process. If you select the correct target type, the discovery process is faster. 4. Type a brief description of the target (optional). 5. Enter the root or administrator username and password. 6. Click OK. This begins the discovery process of the target that is added. Entering target credentials You must enter the credentials (administrator user name and password) for all targets, including the local host, if you are updating it. 1. In the Select Targets screen table, select one or more targets by clicking to highlight the rows. 2. Click Enter Credentials. 3. In the Enter Credentials for the Target(s) dialog box, select one or more targets. The credentials you enter are applied to all selected targets. The Select All button selects all targets in the list. 4. Click Add Credentials. 5. In the Enter Credentials for Target dialog box: a. Enter a user name and password with root or administrator rights. b. Select what HP SUM should do if it detects an update already running. 6. Click OK to save and close the dialog box. 7. Click Done. 8. In the Select Targets screen table, the Status field displays progress messages as HP SUM verifies the credentials you entered. Editing a target NOTE: HP Integrity servers only: If an ilo is part of a domain, HP recommends managing the entire domain, not just the ilo. During the discovery process, if HP SUM detects that an ilo is part of a target domain, HP SUM asks you if you want to manage the entire domain, or if you want to continue to update just the ilo. To add the OA and manage the entire domain, click Enter OA Credentials. 1. Highlight a target, and then click Edit Target. 2. Type a brief description of the target (optional). 22 Using the HP SUM GUI

23 3. Enter the root or administrator user name and password. 4. Click OK after entering the information to exit this page. Removing a target Select a target, highlighting the entire line, and then click Remove Target. If you remove a target, HP SUM removes the target from any groups and any scheduled updates. Managing groups To add a new group: 1. Enter a Group Name. 2. Enter a Description (optional). 3. From the Available Targets list, select the targets to add to the group. 4. Click Add. 5. When you are finished, click OK. To edit an existing group: 1. Select targets in the Available Targets list and then click Add to add one or more targets to the group. 2. Select the targets in the Targets in Group list, and then click Remove to remove one or more targets from the group. 3. Enter a Description (optional). 4. Click OK. Pending firmware updates for ilo (HP Integrity servers only) If you update a previously updated Integrity server via ilo but did not power down and reboot to activate the system firmware change, HP SUM asks you what to do with the pending update. You can choose to: Leave the system for manual reboot to activate. This disables the target in HP SUM and you will need to manually power down and reboot the system to activate the pending update. After the reboot, you can open HP SUM and proceed with the firmware update. Let HP SUM power down the system and reboot the operating system to let the activation happen. HP SUM sends a graceful shutdown request to the operating system and then powers down the server to let the activation occur. Then HP SUM powers back up the server. After the system restarts, you can continue with new updates. Let HP SUM cancel the pending update. This option will cancel the staged update. After the system restarts, HP SUM will rediscover the target and you can continue with the new updates. NOTE: Some updates are critical updates that you need to apply. Before you cancel a pending update, make sure it is not a critical fix that prevents you from applying current updates. NOTE: Cancelling an update and not performing new updates might leave the server in a state where you cannot boot it. The ilo and system firmware might be mixed and incompatible. If you cancel a pending update, make sure you perform a new full firmware update. Selecting the targets 23

24 Reviewing and installing updates This screen appears after HP SUM completes the dependency checks for each target. The status column notifies you whether each target has updates available, is ready to update, or if there are dependencies you need to resolve. On the Select Bundles or Select Components screen, you can select the devices on each target that you want to update. Click Select Bundles to use a collection of components that have been tested together for the target. The Select Bundles screen also allows you to install unbundled components in addition to the bundles available for the target. Click Select Components to apply individual components to devices. For more information on selecting bundles or components, see Selecting bundles (page 25) or Selecting components (page 26). The Selection area of the screen displays the following information: Target Name This field displays the name of the target selected for update. Status This field displays the status of the target. The status message Ready to update indicates that at least one update is selected for installation. Status messages about failed dependencies also appear in this field. To select updates, resolve failed dependencies, or view device selection problems, click Select Bundles or Select Components. Both links display a list of all available updates for your targets. 24 Using the HP SUM GUI The Select Bundles screen lists updates bundled in release sets first, by bundle, followed by unbundled updates components. If a bundle is checked, then at least one part of that bundle is selected. Expand the items to view and select or clear the disk controllers and disk drives available for update. The Select Components screen lists all available updates separately, whether or not they are included in bundles. The list has two parts. Updates that are selected to be installed are listed at the top, followed by any updates that are not selected. You can select or clear updates in this view, as well as in the Select Bundles view. If a component is part of multiple bundles, it is only shown once. If there are multiple versions of a component,

25 HP SUM adds an expansion box next to the most recent version of the component. To install an older version of the component, expand the list, and then select the older component version. NOTE: If you select individual components from the Select Unbundled Components list on the Select Bundles screen, these selections are also applied to the Select Components screen. Last Updated This field displays the last time this target was updated by HP SUM from the current host running HP SUM. Associated Target This field displays the IP address of the target, if the target is listed on another server's OA host servers list. Description This field displays a brief description of the target. Installing updates Select all targets you want to update, and then click Install to begin installing the updates after you have resolved all dependency issues. For more information, see Selecting devices (page 27). Aborting an installation Click Abort Installation once to complete the installation of the current component and abort the installation of the remaining components. NOTE: Aborting an installation is only available in online mode. Viewing failed dependencies If a failed dependency occurs, you must resolve it by ensuring the prerequisite libraries or the appropriate software or firmware components are available before proceeding with the installation. Click Failed Dependencies to see what changes you need to make. Selecting bundles The Bundle Components Selections screen displays the following information for a selected target: Select Devices Displays all bundled and unbundled updates you can install on the target. Status Displays whether the target is ready to be updated, or if there are dependencies that need to be resolved before beginning the update. Installed Version Displays the bundle or component version installed on the target. Active Version Displays the version of the bundle or component that is currently active. This might differ from the installed version if the bundle or component required a restart, and the restart has not happened yet. Reviewing and installing updates 25

26 Available Version Displays the newest version available, if it is not active. Some updates require rebooting the target. If the target has not been rebooted, then the new version is installed, but not yet active. Optional Displays links to actions you can perform to for the target. Select Devices Selects devices associated with this target. You can select the bundles that you want to apply, and view any errors or warnings that might be associated with the bundle or component. Installation Options Open the Install Options screen. For more information about installation options, see Installation options (page 28) Re-analyze Can display an error or warning before applying the update. If you see the same error or warning after correcting the problem, click Re-analyze to run the discovery process again. HP SUM automatically chooses and analyzes the newest bundle or component. If you want to use a different bundle or component, check the bundle or component version you want to apply, de-select the version you do not want to apply, and then click Re-analyze to perform discovery and look for any errors or warnings that might affect the installation. NOTE: If HP SUM shows no devices you can update, you might need to change the types of updates to use on the Edit Repository screen. For more information, see Editing the repository (page 18). To select the bundles to update the selected target: 1. Click Select Bundles on the Review/Install Updates screen. 2. Check the bundle that you want to apply to the target. To update individual components that are not part of a bundle: 1. Click Select Bundles on the Review/Install Updates screen. 2. Click the arrow next to Unbundled Components to expand the list. 3. Check each component that you want to update on the selected target. If there is a dependency failure, click Failed Dependency to see potential solutions for the component. NOTE: If you select individual components from the Select Unbundled Components list on the Select Bundles screen, these selections are also applied to the Select Components screen. Selecting components Use this screen to install individual smart components that are not contained in a bundle. You can choose the devices to update, and choose whether to activate the updates immediately, or wait until the next scheduled target maintenance. NOTE: If HP SUM shows no devices you can update, you might need to change the types of updates to use on the Edit Repository screen. For more information, see Editing the repository (page 18). 1. In the Review/Install Updates screen, click Select Components for a target. The Select Components screen shows applicable components. 2. HP SUM selects the recommended updates automatically. 3. HP Integrity servers only: Click Configure Now and then select Upload and Activate to activate the update. To wait until the next scheduled maintenance to activate the update, select Upload and Do not Activate. This function is supported by HP Integrity servers only. 26 Using the HP SUM GUI

27 4. Check each component that you want to update on the selected target. If there is a dependency failure, click Failed Dependency to see potential solutions for the component. NOTE: HP Integrity servers only: If you see an error that reads, "Mismatch Found" or "Mismatch Found Update Required", click the message to view the Select Devices screen. For more information on this error, see Viewing firmware mismatch details (HP Integrity servers only) (page 28). 5. Click OK. Selecting devices On the Select Devices screen, select the devices on the target that you want to update. You can also review any dependency problems that need to be resolved before HP SUM begins the update installation. NOTE: HP Integrity servers only: Some targets that are part of a domain allow you to update the entire domain at the same time. If you do not want to update the entire domain at once, select the check box next to the partitions you want to update. To select devices: 1. To reach the Select Devices screen, click Select Devices on the Select Bundles or Select Components screen. 2. Select the check box for the device that you want to update. The Status field displays messages about the selected device. If you cannot update a device, the Status field displays a brief explanation. NOTE: HP Integrity servers only: If a multi-blade server displays a Mismatch Firmware or Mismatch Firmware Update Required error, HP SUM resolves the mismatch as part of the update when you click Install. For more information on a firmware mismatch, see Viewing firmware mismatch details (HP Integrity servers only) (page 28). 3. View any errors or warnings displayed at the bottom of the screen. Correct errors before continuing. HP SUM cannot proceed with updates until you resolve the errors. Warnings do not prevent the installation, but continuing an installation without correcting the problem that caused the warning might cause more serious problems. To continue without resolving the warnings, select Ignore Warnings. 4. After you have selected the devices, click OK to exit this screen. Viewing firmware details You can view the firmware detail screen from these screens: Review/Install Updates Select Bundles Select Components To open the view firmware details, do one of the following: Click Installed Version on the Select Bundles or Select Components screen. HP Integrity servers only: Click Mismatch Found on the Review/Install Updates screen, if displayed. The View Firmware Details screen provides information about: Reviewing and installing updates 27

28 Table 1 View Firmware Details screen HP ProLiant servers SPP version NIC version Fiberware version Component versions Bundle version HP Integrity servers Bundle version ilo version Power Monitor firmware version System firmware version FPGA firmware version Bundle version NOTE: The bundle version is only displayed if all four firmware versions match a known bundle. If there is no known bundle, then HP SUM will display Unknown. ilo firmware version Power Monitor firmware version System firmware version FPGA firmware version Viewing firmware mismatch details (HP Integrity servers only) If you have a multi-blade server, you might encounter a situation where you have blades or partitions that are running different firmware versions. As part of the update procedures, HP SUM will notify you that there is a firmware mismatch by displaying either Mismatch Found or Mismatch Found Update Required. Click the message to go to the View Firmware Details screen, where you can view the mismatch details. HP SUM will resolve the firmware mismatch when it installs the new updates. Installation options CAUTION: The ability to force the installation of components is generally unnecessary and is not recommended. Incorrect use could result in data loss or system failure or both. If you set the installation options from the Review/Install Updates screen, you set these options for all the targets. If you want to set installation options for specific targets, click Select Bundles or Select Components for the target, and then click Installation Options for the target. 1. Click Installation Options. 2. Click Check here to enable force options. 3. Do one of the following: Click Downgrade or Rewrite, depending on whether you want to downgrade the firmware version, or overwrite the current firmware version. Force upgrade bundles, firmware, or software. Bundles Selects older PSP and firmware bundles. Firmware Selects older firmware components. Software Selects older PSP or software bundles. NOTE: You cannot use HP SUM to downgrade a Virtual Connect, Ethernet, or FibreChannel module 28 Using the HP SUM GUI

29 Reboot options If you set the reboot options on the Review/Install Updates screen, they are set for all the targets. If you want to set the reboot options for only specific targets, click Select Bundles or Select Components for the target, and then click Reboot Options for the target. NOTE: For Superdome 2 servers, the reboot options are set for each partition on the Select Devices screen. HP SUM does not support global reboot options for Superdome 2 servers. To set the reboot options: 1. Click Reboot Options. 2. Check Reboot System After Installation to set the reboot. 3. Check If Needed or Always. 4. Click OK. NOTE: Reboot Delay and Reboot Message do not apply for Integrity servers. Scheduling updates Use these steps to schedule a time to run the updates. 1. Click Schedule Update. 2. Click Create Schedule, type a schedule name, and then click OK. 3. Select the targets or groups from the Unscheduled Targets list, and then click Add. 4. Select a date and time to start the updates. Check UTC if you want to use Coordinated Universal Time, and not the time zone listed in the Time Zone field. 5. Click Save and Continue, click Done, and then click OK. If you click the X to close the window will not save the schedule. 6. The schedule details are updated in the Target Status. 7. The schedule is completed when you click Install on the Review/Install Updates screen. NOTE: If the Install button is grayed out, make sure you enter all required information on the Review/Install Updates screen. For more information, see Reviewing and installing updates (page 24). NOTE: Schedule settings might be lost if the HP SUM session is closed. HP recommends not to exit from an HP SUM session if a scheduled update has been set. Generating and viewing reports You can generate either an HTML or XML report file detailing the repository contents, target firmware, target installable details, and failed dependencies. You can view both files in a web browser, such as Microsoft Internet Explorer. The reports support JavaScript-enabled web browsers Internet Explorer 6.0 or Mozilla Firefox 3.5 and later. The XML reports also allow you to write programs to pull the report information and display it in other locations. NOTE: Not all reports are available on all screens. If a report is not available, HP SUM grays out the report. Generating a Report 1. Click Generate Report. 2. Click the Browse button and then select the directory where you want to save the report. Scheduling updates 29

30 3. Choose the topic you want to view in the report. Topics that are not valid are grayed out. The Report name will be displayed next to the report selected once it is checked. Inventory Selections Provides details of the contents in all selected repositories. Target Firmware Provides firmware versions for the selected targets. You can generate this report after you have entered the target credentials and HP SUM completes the discovery process on the Select Targets screen. Target Installable details Provides a list of updates available for the selected targets or devices. HP SUM will collect all the information available for this report on the Review/Install Update screen. Failed Dependencies Report Provides details on any failed dependencies that will prevent an update from succeeding. NOTE: The Failed Dependencies Report is automatically generated when you generate a Target Firmware details or Target Installable details report. 4. Choose the type of report to generate: HTML XML 5. HP SUM selects the View generated report box by default. If you do not want to view the report immediately, clear this box. 6. Click Generate. NOTE: HP SUM requires AMS to detect server IP addresses. Viewing a report 1. Click View Report. 2. Click the Browse button and then select the report you want to view, and then click View. 30 Using the HP SUM GUI

31 3 Using 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 [/h[elp]] [/?] [/f[orce]] [/f[orce]:bundle] [/f[orce]:rom] [/f[orce]:software] [/f[orce]:all ] [/g (/downgrade)] [/e (/rewrite) [/r[eboot]] [/reboot_message "reboot message"] [/reboot_delay timeout_in_seconds] [/reboot_always] [/s[ilent]] [/c[omponent] <component_to_install>] [/group "group_name"] [/b[undle] <bundle_to_install>] [/allow_update_to_bundle] [/allow_non_bundle_components] [/use_latest] [/use_location "file_share"] [/use_web] [/use_d[ownloaded]] [/tpmbypass] [/ignore_tpm] [/use_snmp] [/use_wmi] [/use_ams][/romonly] [/softwareonly] [/dryrun] [/continue_on_error <error>] [/override_existing_connection] [/express_install] [/user <username> or /username <username>] [/passwd <password>] [/current_credential] [/target "netaddress"] [/logdir "path"] [/v[erbose]] [/veryv[erbose]] [/report][/inventory_report] [/firmware_report] [/On_failed_dependency:<parameter>] [/oa_username <username>] [/oa_password <password>] [/use_proxy <proxy server>] [/proxy_script <proxy script>] [/proxy_user <username>] [/proxy_passwd <password>][/inputfile "filename"] [/c[omponent] <component_to_install>][<component1_to_install> <component2_to_install>...][<bundle1_to_install> <bundle2_to_install>...] The following commands are supported only by Superdome 2 servers: [/update_type<type>] [/device_list <device[,device] >] [/reboot_list <npar[,npar] >] HP SUM with OA requires a user ID and password to log in. The user ID must be an administrator equivalent ID and not an operator or user equivalent level ID. NOTE: All parameters and information enclosed in brackets are optional. The parameters may be prefixed with either a hypen (-) or slash (/) character. These examples show only the slash. On Windows operating systems, use a slash before each argument. On Linux operating systems, use a hyphen before each argument. If the /s[ilent] argument is not included on the command line, the HP SUM GUI appears. NOTE: Command-line syntax does not support double-byte character sets. Any messages entered through the command line via a double-byte character set will not be displayed correctly. 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. Command-line interface 31

32 The following table shows what updates occur if no switches are currently installed. Command no switches /use_ams /use_snmp /use_wmi /use_ams/use_snmp /use_ams/use_wmi /use_wmi/use_snmp /use_ams/use_wmi/use_snmp G7 and earlier servers SNMP N/A SNMP WBEM SNMP WBEM WBEM and SNMP WBEM and SNMP Gen8 servers AMS AMS SNMP WBEM AMS and SNMP AMS and WBEM WBEM and SNMP AMS, SNMP and WBEM The following table shows what updates occur if SNMP switches are currently installed. Command no switches /use_ams /use_snmp /use_wmi /use_ams/use_snmp /use_ams/use_wmi /use_wmi/use_snmp /use_ams/use_wmi/use_snmp G7 and earlier servers SNMP SNMP SNMP WBEM and SNMP SNMP WBEM and SNMP WBEM and SNMP WBEM and SNMP Gen8 servers SNMP SNMP and AMS SNMP WBEM and SNMP AMS and SNMP AMS, SNMP, and WBEM WBEM and SNMP AMS, SNMP, and WBEM The following table shows what updates occur if WBEM switches are currently installed. Command no switches /use_ams /use_snmp /use_wmi /use_ams/use_snmp /use_ams/use_wmi /use_wmi/use_snmp /use_ams/use_wmi/use_snmp G7 and earlier servers WBEM WBEM WBEM and SNMP WBEM WBEM and SNMP WBEM WBEM and SNMP WBEM and SNMP Gen8 servers WBEM WBEM and AMS WBEM and SNMP WBEM AMS, SNMP, and WBEM WBEM and AMS WBEM and SNMP AMS, SNMP, and WBEM The following table shows what updates occur if AMS switches are currently installed. Command no switches /use_ams G7 and earlier servers N/A N/A Gen8 servers AMS AMS 32 Using scripts to deploy updates

33 Command /use_snmp /use_wmi /use_ams/use_snmp /use_ams/use_wmi /use_wmi/use_snmp /use_ams/use_wmi/use_snmp G7 and earlier servers N/A N/A N/A N/A N/A N/A Gen8 servers AMS and SNMP AMS and WBEM AMS and SNMP AMS and WBEM AMS, SNMP, and WBEM AMS, SNMP, and WBEM NOTE: G7 and earlier servers do not support AMS. Command-line arguments HP SUM recognizes the following command-line arguments, which you can use to pre-populate the GUI on the Source Selection and Review/Install Updates screens. If you specify the target and credentials, use the /s[ilent] parameter to proceed with the installation. You cannot use some arguments, such as /romonly and /softwareonly, together. Help /h[elp] or /? Description Displays command line help information. Installation options /f[orce] /f[orce]:bundle /f[orce]:rom /f[orce]:software /f[orce]:all /g or /downgrade /e or /rewrite /s[ilent] Description Overrides or downgrades an existing component installation. This produces the same results as /f:software. Overrides or downgrades the existing installation of components in the selected bundle. Overrides or downgrades the existing installation of the selected firmware components (applies to firmware only). Overrides or downgrades the existing installation of the selected software components. Overrides or downgrades the existing installation of the selected software components, firmware components, and bundles. Downgrades to an earlier version of firmware for multi-target devices such as hard drives and array controllers (applies to firmware only). Downgrades to an earlier version of firmware for multi-target devices such as hard drives and array controllers (applies to firmware only). Causes the installation to run silently with no GUI or console output. All data writes to the log file. Any generated prompts use the default option and continue the installation without user input. If a component requires input before installation (such as configuration information), then the component installation fails, and an error message writes to the log file. Failed dependencies are not reported to the user when you are using the /s[ilent] argument. To check for failed dependencies, remove the /s[ilent] argument and reissue the command line. The HP SUM GUI appears. Command-line interface 33

34 Installation options /c[omponent]<component_to_install> or <component1_to_install> <component2_to_install> /group "group_name" /b[undle] <bundle_to_install> or <bundle1_to_install> <bu/use_latestndle2_to_install> /allow_update_to_bundle /allow_non_bundle_components /use_latest /use_location "file_share" Description Specifies which components to install. Components to install can be specified with or without the /c[omponent] argument. If you are using the /c[omponent] argument, then only one component can specified with the argument. However, multiple /c arguments and components can be specified on the same line. If you do not use the /c[omponent] argument, then multiple components can be specified at the same time, but the components must be separated by a blank and listed after all the arguments on the command line. The components are installed in the order provided unless dependencies between components require installation in a different order. If so, the utility changes the installation order based on the component dependencies to ensure the successful installation of as many components as possible. Multiple components and bundles can be specified on the same command line. When you are mixing components and bundles on the command line, the filter switches control what components and bundles are installed. This argument specifies an already defined group name in the HP SUM GUI. This argument specifies bundles to install. Bundles to install can be specified with or without the /b[undle] argument. If you are using the /b[undle] argument, only one bundle can specified with the argument. However, multiple /b arguments and bundles can be specified on the same line. If you do not use the /b[undle] argument, multiple bundles can be specified at the same time, but the bundles must be separated by a blank and listed after all the arguments on the command line. This argument is a filter switch. It enables you to install newer versions of components defined in a PSP, ISP, or firmware bundle. This argument enables these components to replace the older versions of the same component that might have shipped with the bundles. This argument is a filter switch. It enables you to install components that are not included in the bundle but reside in the directory with the components in the bundle. This argument is a filter switch for use with bundles. The argument enables the latest version of the bundle to be used when multiple versions of bundles are listed on the command line. If there are no bundles specified on the command line, and multiple bundles are in the directory, the /use_latest argument allows HP SUM to use the bundle that has the latest version for installation. Specifies a directory or file share that contains the PSP, ISP, and components for use with HP SUM. The file_share format must be a mapped file share and not in UNC format. If this argument is not specified, the directory that contains hpsum.exe or HP SUM is used by default. The logged-in account must have access to this location. 34 Using scripts to deploy updates

35 Installation options Description The /user and /passwd arguments do not have any effect when you are attempting to access the file share. Use those arguments only when you are connecting to a target system. /use_web /use_proxy <Proxy server> /proxy_script <Proxy script> /proxy_password<password> /use_d[ownloaded] /use_snmp /use_wmi /use_ams /romonly /softwareonly /express_install Specifies that the check box for Check ftp.hp.com on the Source Selection screen is selected. This enables components to be retrieved from ftp.hp.com and used in the list of possible updates. Enables the inclusion of a proxy server (and port number) to access ftp.hp.com. This parameter must be used with /use_web. For example, /use_web /use_proxy < :80>. Enables the inclusion of a proxy script to access ftp.hp.com. This parameter must be used with /use_web. For example, /use_web /proxy_script <autoproxy.com>. Sets the password to be used for an authenticating proxy server. Specifies that the check box for Use last downloaded repository from ftp.hp.com on the Source Selection screen in the GUI is selected. This enables the previously downloaded components to be included in the list of possible updates. Specifies that components that use SNMP protocol and the AMS components are available for installation by default. When the /use_snmp argument is used, the AMS components are required, but the WMI components are optional. Specifies that components that use the WMI protocol are available for installation. These components are optional and are not installed unless this argument is used. When the /use_wmi argument is used, and the /use_snmp & /use_ams arguments are not, the SNMP and AMS components are optional. This argument does not apply to HP Integrity servers. 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. This filter switch allows you to see only the firmware components needed for installation. When you are using this filter switch, you must exit and restart HP SUM if you want to return to an unfiltered state. Do not use the /romonly argument with the /softwareonly argument. (Applies to firmware only.) This filter switch allows you to see only the software components needed for installation. When you are using this filter switch, you must exit and restart HP SUM if you want to return to an unfiltered state. Do not use the /softwareonly argument with the /romonly argument. Starts an express installation (for the local host only). The HP SUM performs discovery, installation, or exit without user interaction. You can cancel or terminate HP SUM. An express installation will force install all components in the Command-line interface 35

36 Installation options Description default repository and may downgrade drivers and firmware to the versions in the default directory as part of the installation operation. The express installation feature allows you to set a baseline and enforce it regardless of the currently installed version of drivers and firmware on the local server. Overriding errors /tpmbypass or /ignore_tpm /ignore_warnings /continue_on_error <error> /override_existing_connection /On_failed_dependency: <parameter> /partition_only /oa_name and /oa_password Description Specifies that if a TPM is enabled, the warning message should be ignored and component installation can continue. For more information about TPM, see Trusted Platform Module (page 12). Allows the installation to proceed on a Superdome 2 target even when warnings are returned during analysis. Causes the installation to continue and ignore errors. Valid values are as follows: * <error>=servernotfound and * <error>=badpassword. * <error>=faileddependencies You can use the ServerNotFound option to bypass inactive or unavailable remote hosts when you are deploying firmware or software to multiple remote hosts at the same time. Defines the behavior when a remote target has an existing HP SUM session in progress. It overrides the session in progress and re-initializes the installation framework on the remote host. Provides HP SUM <parameter> the information on how to proceed when a component has a failed dependency. The supported parameters for this argument are Omit_Host (default), Omit_Component, and Force. Omit_Host causes the host to be put into a failure state, and no installation is attempted. Omit_Component deselects the affected components and proceeds with any updates that do not have dependency failures. Force attempts all updates, even if they have dependency failures. Use this argument to select a partition to update. Use these arguments if you do not use the /partition_only argument. If you do not enter the selections, then the update will display and error and exit. Reboot options /r[eboot] /reboot_message "reboot message" Description 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. Displays the specified reboot message on remote consoles connected to the server that you want to reboot. You must 36 Using scripts to deploy updates

37 Reboot options Description use this argument with the /reboot option, or the argument is ignored. /reboot_delay timeout_in_secs /reboot_always Delays the reboot of the server for the length of time that the timeout_in_seconds variable specifies. You must use this argument with the /reboot option, or the argument is ignored. Acceptable values are between 15 and The default timeout value is 15 seconds for Microsoft Windows operating systems and 60 seconds for Linux. For Linux, the reboot delay time is converted from seconds to minutes, and any value under a full minute (59 seconds or less) rounds to the next minute. If the following conditions are met, this argument forces the server to reboot: The /reboot_always option is selected or given as a command-line argument. All components selected for installation are successfully installed. Simulating HP SUM /dryrun Description Simulates the installation for a test run. Nothing is installed. Targets /user<username> or /username <username> /psswd <password> /target netaddress /current_credential /oa_username Description Use this argument to log in to the remote targets by using the user ID. For the OA target, use the /oa_username argument. Use this argument to use this password for the user ID specified in the /user parameter (except for the OA target). The password is used to log in to remote targets. For the OA target, use the /oa_password argument. This is the IP address or the DNS name of a remote host, which can be a remote server, remote ilo NIC port, Virtual Connect Ethernet or Fibre Channel Module for c-class BladeSystem, or BladeSystem OA. When two OAs are in an enclosure, this argument should be the active OA. When specifying the IP address, use either the IPv4 or IPv6 format. Enables the credential of the local host to be used as the credential to access the targets instead of providing the user name and password explicitly for each target. The assumption is that the current credential is valid for the targets being accessed. (Applies to Windows only) This argument provides the user name credential for OA associated with VC specified with the target command-line parameter. Only one set of OA credentials can be specified with command-line parameters. You can add multiple VC targets to command-line parameters with the target parameter only if the credentials of OAs associated with specified VCs are the same. The argument oa_username is not required if VC has the same credentials as the associated OA. You do not need to provide an OA network address associated with VC. HP SUM queries it from a specified VC target. Command-line interface 37

38 Targets Description To update multiple VCs with different user names and passwords, or VCs with OAs that have different credentials, use the corresponding input files OAUID and OAPWD. /_password Provides the password credential for OA associated with VC specified with the "target" command-line parameter. Only one set of OA credentials can be specified with command-line parameters. You can add multiple VC targets to command-line parameters with the "target" parameter only if the credentials of OAs associated with specified VCs are the same. The argument oa_password is not required if VC has the same credentials as the associated OA. You do not need to provide an OA network address associated with VC. HP SUM queries it from a specified VC target. To update multiple VCs with different user names and passwords, or VCs with OAs that have different credentials, use the corresponding input files OAUID and OAPWD. Log files /logdir path" /v[erbose] or /veryv[erbose] Description Redirects the output from HP SUM or the HP BladeSystem c-class OA flash utility to a different directory than the default location. For Windows components, the default location is %SYSTEMDRIVE%\CPQSYSTEM\hp\ log<netaddress> and the redirected location is <path>\hp\log\<netaddress>. For Linux components, the default location is /var/hp/ log/<netaddress> and the redirected location is <path>/hp/log/<netaddress>. Sets the verbosity level for the HP SUM execution log file, hpsum_execution_log_<date>_<time>.log. It increases the level of detail that is retained in the log file. The default value is normal verbosity. Generating reports /report /inventory_report Description Generates a report listing of the target summary and describes how the components in the repository affect the target; for example, whether each component applies to the target. The report is generated in HTML and XML with file name formats of HPSUM_Report_<date>_<time>.html and HPSUM_Report_<date>_<time>.xml. By default, the files are located in the present working directory where HP SUM is initiated. If that location is write-protected, you can find the files in the same directory as the HP SUM log files. 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_<date>_<time>.html and HPSUM_Inventory_Report_<date>_<time>.xml. By default, the report is located in the present working directory where HP SUM is initiated. If that location is 38 Using scripts to deploy updates

39 Generating reports Description write-protected, you can find the report in the same directory as the HP SUM log files. /firmware_report Generates a report listing of the firmware installed and details of the target. The report is generated in HTML and XML with file names of HPSUM_Firmware_Report.html and fwreport.xml in the directory named HPSUM_Firmware_Report_<date>_<time>. By default, the report is located in the present working directory where HP SUM is initiated. If that location is write-protected, you can find the report in the same directory as the HP SUM log files. Using input files /inputfile filename /deleteinputfile Description Enables you to script the deployment of firmware and software to multiple remote systems at one time. For more information, see Input files (page 43). Enables you to instruct HP SUM to delete the input file after it has been read. Superdome 2 server commands /update_type<type> /device_list <device[,device] > /reboot_list <npar[,npar] > Description Determines which Superdome 2 firmware is updated. You can choose ALL, COMPLEX, or PARTITIONS. The default selection is ALL. Example: /update_type PARTITIONS Use this argument when the /update_type argument is PARTITIONS. This argument specifies the subset of partitions or blades to update when you do not want to update all partitions or blades. Valid devices are: npar(number) and blade(enc)/(bay). Do not put any spaces between the parameters. Example: /device_list npar1,npar2,blade1/1,blade1/2 Use this argument when the /update_type is ALL or PARTITIONS. This argument specifies specific partitions to reboot after the partition firmware has been updated. Valid npar values are npar(number). Do not put any spaces between parameters. Example: /reboot_list npar1,npar2 Component configuration for Windows components only To configure components without using the HP SUM GUI, issue the command hpsum_config<component_to_configure>. This command presents the same configuration screens that appear in the HP SUM GUI. Run this command from a writeable media source. Configuration for a given component must be executed only one time. The configuration is stored within the component and is propagated to all target servers when it is deployed through the HP SUM GUI or a command line. To change the configuration, rerun hpsum_config against the component. If a component does not need configuration, the hpsum_config command returns to the console. To configure components to be deployed on all editions of Windows Server 2008 with the Server Core option, you must access the system as a remote host by using HP SUM running on a system with a supported Windows operating system, and then configure the components before deployment. Command-line interface 39

40 Command-line examples The following command-line parameter examples can be executed within these environments: Firmware: System ROM Smart Array controller Hard drives ilo Software later version of: HP Insight Diagnostics Online Edition for Windows Server 2003 (cp exe) HP System Management Homepage (HP SMH) for Windows (cp exe) HP SUM Defined groups: Management Servers three servers (Management Server1, Management Server2, Management Server3) Example 1: This command-line input deploys the latest PSP and firmware components: hpsum /use_latest /allow_non_bundle_components /silent Results: All software components and firmware components from the update bundle, which HP SUM determined must be installed, were installed. Example 2: Either of the following command-line inputs can deploy the previous version of the PSP only and force all the components to be installed: hpsum /f:bundle /softwareonly BP xml hpsum /b BP xml /f:bundle /softwareonly Results: All software components and firmware components from the update bundle, which HP SUM determined must be installed, were installed. No firmware was installed. Example 3: This command-line input deploys firmware: hpsum /romonly Results: All firmware components that must be installed, were installed. No software was installed. Example 4: Either of the following command-line inputs can deploy two software components: hpsum /f:software cp exe cp exe hpsum /c cp exe /c cp exe /f:software Results: The two components were installed. No firmware or other software was installed. Example 5: Either of the following command-line inputs can deploy the latest PSP, later versions of components in the bundle, and firmware to three remote hosts and force all components to be installed: hpsum /group "Management Servers" /current_credential /use_latest /allow_update_to_bundle /allow_non_bundle_components /force:all 40 Using scripts to deploy updates

41 Return codes /override_existing_connection /continue_on_error ServerNotFound /silent /logdir "Management_Server_Files" hpsum /target "Management Server1" /target "Management Server2" /target "Management Server3" /user administrator /passwd letmein /use_latest /allow_update_to_bundle /allow_non_bundle_components /force:all /override_existing_connection /continue_on_error ServerNotFound /silent /logdir "Management_Server_Files" Results: All software components and firmware components from the update bundle, cp exe, and cp exe were installed on Management Server1, Management Server2, and Management Server3. HP SUM has consolidated return codes from Linux and Windows smart components into a new, enhanced return-code mapping. These return codes determine the status of the component installation. You can also use return codes in a script to control the execution of the script and determine any required branching. In Linux, the negative return codes are reported. These return codes are determined by subtracting the negative value from 256. Return code Value Linux Windows Text SUCCESS_NO_REBOOT The installation was successful. SUCCESS_REBOOT The installation was successful, but a reboot is required. SUCCESS_NOT_REQUIRED The component was current or not required. FAILURE_GENERAL A general failure occurred. For details, see the error log. FAILURE_BAD_PARM A bad input parameter was encountered. FAILURE_COMPONENT_FAILED The installation of the component failed. Windows smart-component return codes Error level Meaning The smart component was not installed. For more information, see the log file. The smart component was installed successfully. The smart component was nstalled successfully, but the system must be restarted. The installation was not attempted because the required hardware is not present, the software is current, or there is nothing to install. Command-line interface 41

42 Linux smart-component return codes Single-target servers: Error level Meaning The smart component was installed successfully. The smart component was installed successfully, but the system must be restarted. The installation was not attempted because the required hardware is not present, the software is current, or there is nothing to install. The smart component was not installed. For more information, see the log file. Multi-target servers: Error level Meaning The installation of the deliverable was successful. No reboot is required. The installation of the deliverable was successful. Reboot is required for the deliverable to be enabled. The installation was not attempted because the version to be installed matches the version already installed. The installation was not attempted because of one of the following: The version to be installed is older than the version already installed. The supported hardware is not present, not enabled, or in a state that an installation could not be attempted. The smart component does not support the environment. There is nothing for the component to accomplish. If the component is being installed to a remote target, such as an OA or other network-based deployment, this return code indicates that the target cannot be found. A user canceled the installation before anything could be installed. The installer cannot run because of an un-met dependency or installation tool failure. The actual installation operation (not the installation tool) failed. Linux RPM return codes Error level 0 1 Meaning The Linux RPM installation was successful. The Linux RPM installation failed. 42 Using scripts to deploy updates

43 Input files HP SUM provides the ability to script the update of multiple, individual targets or groups of targets (HP ProLiant and Integrity servers and options) within a single operation through the input file functionality. To protect your credentials, use a secure server or a management console. To create an input file, use a text editor. All section headers and trailers must match. Failure to use the SILENT=YES option causes the GUI mode to be used, but the information provided enables you to skip screens where information has already been provided. 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 target. Remove the DRYRUN=YES option to perform the updates. For parameters that can take list values, list separators can be commas, semicolons, or spaces. NOTE: The credentials can be omitted from the file for greater security and passed on the command line to HP SUM. The only limitation that the user ID and credentials must be the same on all. When the file has been created, to use it with HP SUM, add it as the inputfile <filename> parameter to a HP SUM command line. For example, if the name of the input file is hpsum.in, the command-line syntax is hpsum -inputfile hpsum.in. Full paths can be added to the input file location if the file is not stored in the same location as the HP SUM executables. The <filename> field can be enclosed in double quotes to enable paths with spaces. Also, the input file itself might contain the same options on the command line. The usual command-line options can still be used with the -inputfile option and they take precedence over any given input file. Input file format and rules The input file is divided into two sections: Configuration The configuration section starts from the beginning of the file and proceeds until the first target section is encountered. This section consists of a number of settings and their values. Each configuration setting must appear on a fresh line in the file, along with its value. Comments start with a pound (#) character at the beginning of the line. Only one pound character is allowed on any line. Target You can provide remote host targets to HP SUM. This section can repeat any number of times in the input file, providing a way to organize targets in related sets. The section starts with the following special header enclosed in brackets: [TARGETS] The section ends with the following special string enclosed brackets: [END] The keyword TARGETS can be suffixed with an optional arbitrary string. This string enables you to tag the purpose of the TARGETS section. Other than the visible difference in the header, the contents of such a section are not treated any differently. For example: [TARGETS_WIN2003]... [END] Credentials: The TARGETS section allows the targets to be grouped according to the credentials needed for logging in remotely. Each TARGETS section must have a set of login credentials, which applies to all targets in that section. If you want to use the current host's login credentials to log in to one or more remote targets, you can do so by setting Input files 43

44 File encoding Error reporting the variable USECURRENTCREDENTIAL to YES. You can supply login credentials for one or more hosts by using the variables UID and PWD. If you want to provide the variables at the beginning of a TARGETS section, use both of them. If you want to provide the variables in the middle of a TARGETS section, use one or the other to override the selected variable and continue using the active value for the remaining variable. Remote target: You can specify a remote target by using the variable HOST. Possible values are a DNS name or an IP address. To allow for the inclusion of double-byte characters, the input file is in UTF-8 format. 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_<date>_<time>.raw. Input file parameters Parameter SILENT FORCEALL FORCEROM FORCESOFTWARE FORCEBUNDLE DOWNGRADE REWRITE REBOOTALLOWED REBOOTMESSAGE REBOOTDELAY Description This parameter causes the installation to run silently without GUI or console output. All data is written to the log file. Any generated prompts use the default option and continue the installation without user input. If a component requires input before installation (such as configuration information), the component installation fails (unless the IGNOREERRORS = "FailedDependencies" parameter is supplied), and an error message is written to the log file. Forces updates to both firmware and software components. Forces updates to firmware components. Forces updates to software components. Enables you to override or downgrade an existing installation of components in the selected bundle. Downgrade to an earlier version of firmware for multi-target devices such as hard drives and array controllers. (Applies to firmware only.) Rewrite the same version of firmware only for multi-target devices such as hard drives and array controllers. (Applies to firmware only.) Enables you to reboot, if required. Create a message to be displayed prior to rebooting. Delay before rebooting. Possible values YES, NO YES, NO YES, NO YES, NO YES, NO YES, NO YES, NO YES, NO Any string (not exceeding 256 characters) Time in seconds 44 Using scripts to deploy updates

45 Parameter COMPONENTSLIST BUNDLESLIST ALLOWUPDATEBUNDLE SKIPTARGET Description Limit the list of components to be updated. Limit the list of bundle xml files to be filtered. This is a filter switch and enables you to install newer versions of components defined in a PSP, ISP, or bundle. This parameter enables these components to replace the older versions of the same component that might have shipped with the bundles. Defines the behavior when a remote target has an existing HP SUM session in progress. Use this parameter to skip the host if an existing HP SUM session already exists. A value of NO overrides the session in progress and reinitializes the installation framework on the remote host. Possible values Component names with file extensions (.exe,.rpm, or.scexe) Bundle file names YES, NO YES, NO 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. ServerNotFound, BadPassword, FailedDependencies SOURCEPATH USELATEST DRYRUN OPTIONS Provide a single local repository path. This action creates an inventory from the given path instead of the local or default repository. This is a filter switch for use with bundles. The parameter enables you to use the latest version of the bundle when multiple versions of bundles are listed on the command line. If no bundles are specified on the command line, and multiple bundles are in the directory, this parameter enables HP SUM to use the bundle that has the latest version for installation. Simulates the installation for a test run. Nothing is installed. Specify the HP SUM CLI options inside the input file, which overrides the configuration settings. Parameters can be separated by a semi-colon, comma, or a space. This parameter replaces the LSPOPTIONS parameter that was previously supported with LDU. Directory path YES, NO YES, NO One or more CLI switch Input files 45

46 Parameter USESNMP USEWMI ROMONLY SOFTWAREONLY USECURRENTCREDENTIAL WEBUPDATENEEDED USEPROXYSERVER USEPROXYSCRIPT DELETEINPUTFILE ONFAILEDDEPENDENCY Description Specifies that components that use SNMP protocol, are available to be selected for installation. These components are available for selection by default. When the /usesnmp parameter is used, and the /usewmi parameter is not used, the WMI components are optional. This parameter does not apply to HP Integrity servers. Specifies that components that use WMI protocol are available to be selected for installation. These components are optional by default and are not installed unless this parameter is used. When the /usewmi parameter is used, and the /usesnmp parameter is not used, the SNMP components are optional. This parameter does not apply to HP Integrity servers. 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. This is a filter switch that allows you to view only the software components required for installation. Do not use the /softwareonly parameter with the /romonly parameter. Enables the credentials of the local host to be used as the credentials to access the targets instead of providing the user name and password explicitly for each target. The assumption is that the current credentials are valid for the targets that are being accessed. (Applies to Windows operating systems only.) Instructs HP SUM to include the components from the HP FTP site (ftp:// ftp.hp.com) in the list of possible updates. Use a proxy server (and port number) to access the HP FTP site (ftp://ftp.hp.com). Include a proxy script to access the HP FTP site (ftp://ftp.hp.com). Instructs HP SUM to delete the input file after it has been read. This parameter instructs HP SUM how to proceed when a component has a failed dependency. The default of OmitHost causes the host to be put in a failure state, and no installation is attempted on it. Possible values YES, NO YES, NO YES, NO YES, NO YES, NO YES, NO String value For example, :80 Web URL (for example, autoproxy.com) YES, NO (default) OmitHost (default), OmitComponent, Force 46 Using scripts to deploy updates

47 Parameter HOST UID PWD LOGFILENAME = "path" CMALOCALHOSTRWCOMMSTR CMALOCALHOSTROCOMMSTR CMAMGMTSTATIONRWIPORDNS CMAMGMTSTATIONRWCOMMSTR CMAMGMTSTATIONROIPORDNS Description OmitComponent clears the affected components and proceeds with any updates that do not have dependency failures. Force attempts all updates, even if they have dependency failures. This parameter is the IP address or the DNS name of a remote server, remote ilo NIC port, Virtual Connect Ethernet or Fibre Channel Module for c-class BladeSystem, or BladeSystem OA. When two OAs are in an enclosure, this parameter is the active OA. When specifying the IP address, you can use either the IPv4 or IPv6 format. This parameter specifies an already defined group name in the HP SUM GUI. Logs in to the target hosts with your user ID. Uses the password for the user ID specified in the UID. The password is used to log in to target hosts. Redirects the output from HP SUM or the HP BladeSystem c-class OA flash utility to a different directory than the default location. * For Windows components, the default location is %SYSTEMDRIVE%\ CPQSYSTEM\hp\log<netAddress> and the redirected location is <path>\ hp\log\<netaddress>. * For Linux components, the default location is /var/hp/log/ <netaddress> and the redirected location is <path>/hp/log/ <netaddress>. Specifies an SNMP read/write community string for local host access. (Applies to Linux PSP only.) Specifies an SNMP read-only community string for local host access. (Applies to Linux PSP only.) Specifies the IP address or DNS host name of a system with read/write access to serve as a management station. You can specify multiple locations separated by a space. (Applies to Linux PSP only.) Specifies an SNMP read/write community string for a system with read/write access that serves as a management station. You can specify multiple strings separated by a space. (Applies to Linux PSP only.) Specifies the IP address or DNS host name of a system with read-only access to serve as a management station. You can specify Possible values IP address, DNS name <username> <password> Log file name SNMP read/write community string SNMP read-only community string IP address, DNS name SNMP read/write community string IP address, DNS name Input files 47

48 Parameter CMAMGMTSTATIONROCOMMSTR CMADEFTRAPCOMMSTR CMATRAPDESTINATIONCOMMSTR CMATRAPDESTINATIONIPORDNS CMASYSCONTACT CMASYSLOCATION Description multiple locations separated by a space. (Applies to Linux PSP only.) Specifies an SNMP read/write community string for a system with read-only access that serves as a management station. You can specify multiple strings separated by a space. (Applies to Linux PSP only.) Sets a default SNMP community string for traps. (Applies to Linux PSP only.) Specifies the SNMP destination trap community string. (Applies to Linux PSP only.) Specifies the IP address or DNS host name of a server as a destination for SNMP traps, such as Systems Insight Manager. (Applies to Linux PSP only.) Specifies a person or phone number for administration of this system. (Applies to Linux PSP only.) Designates the location of this system. (Applies to Linux PSP only.) Possible values SNMP read/write community string SNMP community string SNMP trap destination IP address, DNS name String value String value CMASTARTWEBAGENT Determines whether the HP Systems Insight YES (start the web agent) Manager Web Agent is started when the health application loads. (Applies to Linux NO (do not start the web agent) PSP only.) CMASTARTSTORAGEAGENT Determines whether the HP Systems Insight YES (start the storage agent) Manager Storage Agent is started when the health application loads. (Applies to NO (do not start the storage agent) Linux PSP only.) CMASTARTNICAGENT Determines whether the HP Systems Insight YES (start the web agent) Manager NIC agent is started. (Applies to Linux PSP only). NO (do not start the web agent) CMANOTAINTEDKERNEL Determines whether the HP Lights-Out YES (start the HP Lights-Out management driver is started when the management driver) health application loads. (Applies to Linux PSP only.) NO (do not start the HP Lights-Out management driver) HPVCAVCRMSERVER HPVCAVCRMLOGINID HPVCAVCRMLOGINPASSWD FORCE-OVERWRITE Informs the VCA of the name of the VCRM to use as a software distribution repository. (Applies to Linux PSP only.) This parameter is the login ID that the VCA uses to communicate with the VCRM. (Applies to Linux PSP only.) This parameter is the password for the login ID specified in the HPVCAVCRMLOGIN parameter. (Applies to Linux PSP only.) HP Systems Management Homepage (hpsmh) uses this parameter to force overwrite the SMH settings of an existing configuration file. VCRM name VCA login ID VCA login password YES, NO (default) 48 Using scripts to deploy updates

49 Parameter ADMIN-GROUP USER-GROUP OPERATOR-GROUP ANONYMOUS-ACCESS IP-BINDING IP-BINDING-LIST IP-RESTRICTED-LOGINS Description HP Systems Management Homepage (hpsmh) uses this parameter to set up security for the web server. (Applies to Linux PSP only.) HP Systems Management Homepage uses this parameter to set up security for the web server. (Applies to Linux PSP only.) HP Systems Management Homepage uses this parameter to set up security for the web server. (Applies to Linux PSP only.) Determines whether an anonymous user can access HP Systems Management Homepage. (Applies to Linux PSP only.) HP Systems Management Homepage uses this parameter to determine whether HP SMH can use all available NICs and detect subnets for its web services. (Applies to Linux PSP only.) HP Systems Management Homepage uses this parameter to restrict the NICs and subnets to use for its web servers. The IP-BINDING parameter must be set to yes for this parameter to be used during installation. (Applies to Linux PSP only.) HP Systems Management Homepage uses this parameter to restrict login access. (Applies to Linux PSP only.) Possible values Up to five Linux groups, separated by spaces or semicolons, to enable administrative access to the web services. Up to five Linux groups, separated by spaces or semicolons, to enable user-level access to the web servers. Up to five Linux groups, separated by spaces or semicolons, to enable operator-level access to the web servers. YES, NO (default) YES, NO (default) IP address pairs separated by semicolons (for example, / ; / ) YES, NO (default) To enable restrictions on who can log in to the web server, this parameter must be set to yes, and values must be provided to the IP-RESTRICTED-EXCLUDE or IP-RESTRICTED-INCLUDE parameters. IP-RESTRICTED-EXCLUDE IP-RESTRICTED-INCLUDE HP Systems Management Homepage uses this parameter to exclude specific IP address/netmask pairs from logging into the web services. (Applies to Linux PSP only.) This parameter is ignored unless the IP-RESTRICTED-LOGINS parameter is set to yes. HP Systems Management Homepage uses this parameter to enable login only from the IP address/netmask pairs specified. (Applies to Linux PSP only.) This parameter is ignored unless the IP-RESTRICTED-LOGINS parameter is set to yes. List of IP address ranges separated by semicolons (for example, ; ) List of IP address ranges separated by semicolons (for example, ; ) LOCALACCESS-ENABLED HP Systems Management Homepage uses YES (default to include anonymous this parameter to determine whether to access) enable local anonymous access to the web services. (Applies to Linux PSP only.) NO LOCALACCESS-TYPE HP Systems Management Homepage uses Anonymous (default) this parameter to determine the type of Administrator CAUTION: Selecting local access with administrator privileges as the login Input files 49

50 Parameter Description access granted to local users. (Applies to Linux PSP only.) Possible values provides full access to any user who has access to the local console, without prompting for a user name or password. TRUSTMODE HP Systems Management Homepage uses TrustByCert If you use this value, you this parameter to set up the trust must define the CERTLIST parameter to enable access to the server. relationship mode. (Applies to Linux PSP only.) 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. Failure to do so prevents the trust relationship from being set up properly during installation and might affect access to the web server. CERTLIST XENAMELIST Enables you to provide a list of certificate files or servers where certificates can be obtained for trust relationships for the HP Systems Management Homepage. (Applies to Linux PSP only.) Enables you to provide a list of servers, separated by semicolons, for trust relationships for the HP Systems Management Homepage. (Applies to Linux PSP only.) This parameter is valid only if the TRUSTMODE parameter is set to TrustByName. (Applies to Linux PSP only.) Certificate file name or Server DNS name Server DNS name HPQLA2X00FO The hp_qla2x00 QLogic Fibre Channel SinglePath Driver uses this parameter to determine the failover mode to use. (Applies to Linux SecurePath PSP only.) QLogicFailure NOTE: No default value HPQLA2X00FORCE OAUID OAPWD The hp_qla2x00 QLogic Fibre Channel Driver uses this parameter to determine whether to skip detection of third-party storage. (Applies to Linux PSP only.) Provides the user name credentials for the OA associated with VC. You must define a value of these variables before the HOST variable in the [TARGETS] section. This parameter applies only for VC firmware. You can also use OAUSER or OAUSERNAME. Provides the password credentials for the OA associated with VC. You must define a value of these variables before the HOST variable in the [TARGETS] section. This parameter applies only for VC firmware. You can also use OAPASSWORD. Y, N (default) User can define the OAUID variable multiple times before each HOST variable. User can define OAPWD variable multiple times before each HOST variable. 50 Using scripts to deploy updates

51 Parameter IGNOREWARNINGS UPDATETYPE DEVICELIST REBOOTLIST Description Allows the installation to proceed on a Superdome 2 target even when warnings are returned during analysis. This argument determines which Superdome 2 firmware is updated. Use this argument when the UPDATETYPE=PARTITIONS. This argument specifies the subset of partitions or blades to update when you do not want to update all partitions. Valid devices are: npar(number) and blade(enc)/(bay). Use this argument when the UPDATETYPE= ALL or UPDATETYPE= PARTITIONS. This argument specifies specific partitions to reboot after the partition firmware has been updated. Valid npar values are npar(number). Possible values YES, NO Superdome 2 servers only ALL, COMPLEX, PARTITIONS Superdome 2 servers only For example: DEVICELIST = npar1, blade1/1 Superdome 2 servers only For example: REBOOTLIST = npar1, npar2 Superdome 2 servers only Examples of the HP SUM input file include the following: REBOOTALLOWED = YES REBOOTREQUIRED = NO REBOOTMESSAGE = "Server is going down for a reboot" REBOOTDELAY = 15 COMPONENTSLIST = cp exe, cp exe BUNDLESLIST = bp xml ALLOWUPDATEBUNDLE = YES SKIPTARGET = NO IGNOREERRORS = ServerNotFound, FailedDependencies SOURCEPATH = c:\pkgsource1 USELATEST = YES SILENT = YES OPTIONS = /f:rom [TARGETS] HOST = schinta1 HOST = schinta2 UID = root PWD = root123 HOST = [END] USAGE: hpsum /inputfile <path:\inputfile.txt> Examples of inputfile.txt file: Example: The two targets are passed to be updated. The targets do not necessarily have to be OAs. They can be any target that HP SUM supports. DRYRUN = YES Input files 51

52 SILENT = YES [TARGETS] HOST = BL465C-01 HOST = [END] Example A host DNS is passed along with the user ID and password to use for the hosts in the group. DRYRUN = YES SILENT = YES [TARGETS] HOST = BL685cG6 UID = Bigboss2 PWD = password [END] Example SILENT = YES IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies SKIPTARGET = NO SOURCEPATH = C:\fwcd\firmware \hp\swpackages [GROUPS] HOST=winserver UID=Userid PWD=password [END] Example SILENT = YES IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies SKIPTARGET = NO SOURCEPATH = C:\ fwcd\firmware \hp\swpackages FORCEALL = YES REBOOTALLOWED = YES REBOOTDELAY = 30 REBOOTMESSAGE = Install complete, server will reboot in 30 seconds [TARGETS] HOST= UID=Userid PWD=password [END] [TARGETS] HOST= UID=Userid PWD=password 52 Using scripts to deploy updates

53 Reports [END] [TARGETS] HOST= UID=Userid PWD=password [END] [TARGETS] HOST= UID=Userid PWD=password [END] Example: Superdome 2 input files: IGNOREWARNINGS = TRUE [TARGET] HOST = UID = Userid PWD = password UPDATETYPE = PARTITIONS DEVICELIST = npar1, npar2, blade1/4, blade 1/5 REBOOTLIST = npar1, npar2 [END] HP SUM generates three types of reports about the specified system or repository. HP SUM generates these reports by using the command-line arguments. If no additional arguments are specified on the command line, HP SUM uses the local host and default repository locations (the directory where HP SUM was initiated). You can specify a target if you provide the appropriate credentials. You can specific a repository by using other command-line parameters to generate reports. For specific commands, see Command-line interface (page 31). Report type /report /inventory_report /firmware_report Description This argument generates a report listing, a target summary, and description of how the components in the repository affect the target. For example, whether each component applies to the target. Usage: hpsum /report This argument generates a report listing of the components in the specified repository. Usage: hpsum /inventory_report This argument generates a report listing of the firmware in the specified repository. Usage: hpsum /firmware_report Report file information* The following report files are generated: hpsum_report_<date>.html hpsum_report_<date>.xml The following report files are generated: hpsum_inventory_report_<date>.html hpsum_inventory_report_<date>.xml The following report files are generated: HPSUM_Firmware_Report_<date> fwreport.xml is placed in a folder named HPSUM_Firmware_Report_<date> Reports 53

54 Report type /dependency_report /installed_report Description This argument generates a report that lists failed dependencies for all targets. This argument generates a report that lists all installed firmware, software, and driver versions installed on targets. Report file information* The following report file is generated: HPSUM_FailedDependency_Reports_<datatime>.xml or.html The following report file is generated: HPSUM_Installed_Report_<datatime>.xml or.html HP SUM generates the reports as an XML or HTML files that you can view in a JavaScript-enabled web browser. The supported browsers for viewing the report files are Microsoft Internet Explorer 6.0 and Mozilla Firefox 3.5 and later. By default, the reports are located in the current working directory from where HP SUM was initiated. If that current location is write-protected, the reports are located in the same directory as the HP SUM log files. The HP SUM log files are located in these folders: On Windows operating systems: C:\cpqsystem\hp\log On Linux operating systems: /var/hp/log 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. 54 Using scripts to deploy updates

55 4 Advanced topics Configuring IPv6 networks You can deploy to remote targets in IPv6-based networks for Windows and Linux target servers. Using HP SUM with IPv6 networks presents challenges for IT administrators. For Windows-based servers, to communicate with remote target 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. After HP SUM connects to the admin$ share, it copies a small service to the target server for the duration of the installation. After this service starts, HP SUM uses this service to communicate between the local and remote target server. During this process, HP SUM opens ports in the Windows firewall to enable HP SUM to use SOAP calls over SSL to pass data among local and remote systems. For more information about the ports used, see Network ports used by HP SUM (page 57). After the installation is completed or canceled, HP SUM stops the remote service, removes it from the target server, closes the port on the Windows firewall, and then releases the share to the target server admin$ share. For Linux-based servers, to communicate to remote target servers, HP SUM starts by using the user-provided user name and password to create a SSH connection to the target server. After the it connects, HP SUM copies a small service to the target server for the duration of the installation. After this service starts, HP SUM uses this service to communicate between the local and remote target server. During this process, HP SUM opens ports in the iptables firewall to enable HP SUM to use SOAP calls over SSL to pass data between the local and remote systems. For more information about the ports used, see Network ports used by HP SUM (page 57). When the installation is completed or canceled, HP SUM stops the remote service, removes it from the target server, closes the port in the iptables firewall, and then closes the SSH connection to the target server. NOTE: Windows XP clients are not supported in IPv6 networks for HP SUM deployment. Configuring IPv6 for Windows Server 2003 For information on setting up a Windows Server 2003 operating system within an IPv6 network, see the online Microsoft TechNet article Step-by-Step Guide for Setting Up IPv6 in a Test Lab. Windows Server 2003 requires site-local addresses to provide the necessary file-sharing capabilities needed by HP SUM. This means that link-local and global IPv6 addresses are not supported as remote targets with HP SUM. Before using HP SUM to deploy software and firmware updates to remote Windows Server 2003 servers, you must add a registry entry to enable file sharing connections over IPv6 networks. To make the registry entry: 1. Open the Registry Editor (Regedit32.exe). 2. Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters 3. On the Edit menu, click Add Value. 4. Add the following registry value: Value name: DisableStrictNameChecking Data type: REG_DWORD Radix: Decimal Value: 1 5. Close the Registry Editor. For more information about these steps, see the Microsoft Knowledge Base Item on the Microsoft website. Configuring IPv6 networks 55

56 IPv6 addresses can be passed to HP SUM in command line arguments or using the HP SUM user interface. In the HP SUM user interface, you can add a remote host on an IPv6 network by either entering the DNS name of the IPv6 target server or by selecting the IPv6 address button and entering the IPv6 address. HP SUM supports both the short-name and full IPv6 notation. You do not need to add the optional interface number when you enter the address. If you cannot connect to the target server or receive a Discovery failed message when executing HP SUM in an IPv6 environment, see Troubleshooting (page 59). After you connect to the target server, all other HP SUM functions work identically. Log files for IPv6 hosts are stored with all other HP SUM files in the \CPQSYSTEM\hp\log\<ip_address> directory. Configuring IPv6 for Windows Server 2008 HP SUM provides the most robust support for remote deployment when using Windows Vista as a client to Windows Server 2008-based servers. Using HP SUM in this environment enables you to use all the capabilities of IPv6 including link-local, site-local, and global IP addresses for both local and remote target servers. Windows Vista, when used as a client to run HP SUM to remote Windows Server 2008 operating systems or as a target operating system on HP Workstation server blades, provides the infrastructure that supports full IPv6 deployment of software and firmware updates from HP SUM. NOTE: Windows XP clients are not supported in IPv6 networks for HP SUM deployment. IPv6 addresses can be passed to HP SUM in command line arguments or using the HP SUM user interface. In the HP SUM user interface, you can add a remote host on an IPv6 network by either entering the DNS name of the IPv6 target server or by selecting the IPv6 address button and entering the IPv6 address. HP SUM supports both the short-name and full IPv6 notation. You do not need to add the optional interface number when you enter the address. If you cannot connect to the target server or receive a Discovery failed message when executing HP SUM in an IPv6 environment, see Troubleshooting (page 59). After you connect to the target server, all other HP SUM functions work identically. Log files for IPv6 hosts are stored with all other HP SUM files in the \CPQSYSTEM\hp\log\<ip_address> directory. Configuring IPv6 for Linux HP SUM leverages the IPv6 capabilities of Linux as provided by the Red Hat Enterprise Linux and Novell SUSE Linux Enterprise Server products. Using HP SUM in this environment enables you to use all the capabilities of IPv6 including link-local, site-local, and global IP addresses for both local and remote target servers. Remote target servers must have the iptables-ipv6 RPM installed before targeting them from HP SUM. Failure to install the iptables-ipv6 RPM prevents HP SUM from opening the communications port needed to send data to the initiating Linux workstation. You can disable the Linux firewall to allow HP SUM to work, but the Linux server becomes vulnerable to attack. For information on how to setup IPv6 in a Linux environment, please see the Linux IPv6 How To website at Linux IPv6 How-To. IPv6 addresses can be passed to HP SUM in command line arguments or using the HP SUM user interface. In the HP SUM user interface, HP SUM automatically detects whether to use IPv4 or IPv6 on the Add Target screen. On the Find Targets screen if you choose to select to IP address range, select IPv4 or IPv6. HP SUM supports both the short-name and full IPv6 notation. You do not need to add the optional interface number when you enter the address. If you cannot connect to the target server or receive a Discovery failed message when executing HP SUM in an IPv6 environment, see Troubleshooting (page 59). After you connect to the target server, all other HP SUM functions work identically. Log files for IPv6 hosts are stored with all other HP SUM files in the /var/hp/log/<ip_address> directories. 56 Advanced topics

57 The only current limitation of HP SUM in a Linux IPv6 environment is that all remote target Linux-based servers must have the iptables-ipv6 RPM file installed. You can find the file on the distribution media for both Red Hat Enterprise Linux and Novell SUSE Linux Enterprise Server operating systems. HP SUM uses this file to open a port in the IPv6 firewall to communicate with the Linux system that runs HP SUM. Failure to install iptables-ipv6 results in HP SUM reporting a discovery failure unless you disable the firewall. Network ports used by HP SUM HP SUM requires that certain network ports are available for proper operation. If you lock down network ports, remember to ensure that the ports listed in the network port tables are open so that HP SUM works correctly when connecting to remote target servers and hosts. If you are unable to unlock these network ports, the only option is to run HP SUM locally and update network-based hosts, such as the OA, ilo, and VC, through their web interfaces. The SOAP server that HP SUM launches uses ports 443 or You can define your own ports by modifying the hpsum.ini file. 1. Open hpsum.ini in a text editor. You can find the file in the same folder as the HP SUM application. 2. Look for the following lines: Port=443 AlternatePort= Change the AlternatePort to a port free of another web service. NOTE: HP does not recommend changing the main port from port 443. Table 2 HP SUM Windows network ports Ports Port 443 Ports 445 and 137/138/139 (Port 137 is used only if you are using NetBIOS naming service.) Port Ports 80 or Description A secure data port used to transfer information. Connects to the remote ADMIN$ share on target 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 target server, then you have the right ports open. Default for some internal communications. This port listens on the remote side if there is no conflict. If a conflict occurs, the next available port is used. Logs are passed to the target and retrieved through an internal secure web server that uses port 80 if it is available. If it is not available, the Web server uses first available port in the range of This support allows updates of the ilo and VC firmware without the need to access the host server. It also allows the servers to run VMware or other virtualization platforms to update the ilo firmware without requiring a server reboot or a migration of the virtual machines to other servers. NOTE: HP SUM attempts to determine if a server running HP SUM also hosts a web server. In some cases, HP SUM cannot detect an existing web server and attempts to use port 80. If this occurs, installations that are using HP SUM will fail. If failure occurs, you can move HP SUM to another server or workstation that is not already running a web server. You can also disable the web server until HP SUM installations are complete. Network ports used by HP SUM 57

58 Table 3 HP SUM Linux network ports Ports Port Port Ports 80 or Description Establishes a connection to the remote Linux server via SSH. For Integrity servers, HP SUM uses this port to discover target settings. A secure data port used to transfer information. Default for some internal communications. It listens on the remote side if there is no conflict. If a conflict occurs, the next available port is used. Updates are passed to the target and retrieved through an internal secure web server that uses port 80 if it is available or port 63006, if it is not. This support allows ilo and VC firmware updates without having to access the host server. It also allows servers running VMware or other virtualization platforms to update their ilo without having to reboot their server or to migrate their virtual machines to other servers. NOTE: HP SUM attempts to determine if a server running HP SUM also hosts a web server.in some cases, HP SUM cannot detect an existing web server and attempts to use port 80. If this occurs, installations that use HP SUM will fail. If failure occurs, move HP SUM to another server or workstation that is not already running a web server. You can also disable the web server until HP SUM installations are complete. 58 Advanced topics

59 5 Troubleshooting Recovering from an installation failure Collecting trace directories HP SUM generates a set of debug trace logs located in the %TEMP%\hp_sum directory on Windows systems. These files contain internal process and debug information, which can be useful in determining HP SUM failures. The debug trace files can be located under %temp%\hp_sum for windows. The log files can be located under C:\cpqsystem\hp\log. These files provide the following information and are appended in each HP SUM session. HP SUM has a utility named GatherLogs.exe (Windows) or GatherLogs.sh (Linux) to create a compressed file (Windows:.zip; Linux: tar.z) with all the logs. If you need to review the log files, you can run this utility to gather all the logs in one file. NOTE: Exit HP SUM before running the GatherLogs utility. Debug Trace Files Opman.trace InventoryResults.xml Settings.xml SourceClient.trace Hpsumiserver\Hpsumiserver.log Function Contains operations manager trace data of the overall installation process, details of repository/ components added/removed and general errors if any. Contains details of the component inventory from the repositories. Includes general settings information of HP SUM such as Force downgrade or upgrade. Includes trace data of repository manager and general errors if any. Contains trace data for HP SUM SOAP server sessions. Hpsumiserver\HpsumserverW32.log Hpsumiserver\localhpsumsoapserver.log Sesssion.log RepositoryManager <target>\discoverymanager.log <target>\installmanager.log <target>\<target name>_log.txt <target>\settings.xml Contains information of the HP SUM SOAP server. Contains the data and time for each session has started. This file is saved in separate directory named with the date. Provides the repository and component information This directory can be excluded in the trace data when collecting the trace files. Provides the details of interaction between the Operations Manager and the remote discovery client. If a discovery tool fails, it is reported to this trace file and surfaced as a Discovery Failed message. This log is target specific. Provides the interaction between the Operations Manager and the remote discovery client. If a discovery tool fails, it is reported to this trace file and surfaced as a Discovery Failed message. This log is target specific. Provides the trace data from operations manager for specific target. Provides general settings information of HP SUM such as Force downgrade or upgrade for specific target. Recovering from an installation failure 59

60 Log Files <target>\hpsum_log.txt Note: <Target> is the name of the target in the source selections screen. Hpsum_detail_log.txt hpsum_execution_log_<date>_<time>.log hpsum.ini Function Contains information of HP SUM discovery, installation status and errors if any. Contains the log data of the components. Provides detailed information of execution of HP SUM Stores persistent data on the user's system. It is possible to look in the OpMan.trace file and see which component was winnowed from the installation set and which ones were added. Normally, components are winnowed if: They do not support installation on the given operating system The hardware they are designed for is not discovered to be present in the server The component is not for the type of target selected The component does not report itself capable of being deployed to a given target The component cannot be deployed in either the online or offline environment The following is an example of the output trace in the OpMan.trace on how to determine if a component was prevented from being shown on the Select Items to Install screen or being deployed from the silent console mode. In the example, the binary image files 0.bin and 1.bin (which represented ilo firmware files), components cp exe and cp exe, and the HP SPP represented by bundle file bp xml were added to the installation set. All the other components were removed for various reasons. InstallSet.cpp[212]: Winnow--Adding FileName 0.bin InstallSet.cpp[212]: Winnow--Adding FileName 1.bin InstallSet.cpp[222]: Winnow--Removing FileName 2.bin InstallSet.cpp[212]: Winnow--Adding FileName cp exe InstallSet.cpp[222]: Winnow--Removing FileName cp exe InstallSet.cpp[222]: Winnow--Removing FileName cp exe InstallSet.cpp[222]: Winnow--Removing FileName cp exe InstallSet.cpp[212]: Winnow--Adding FileName cp exe InstallSet.cpp[222]: Winnow--Removing FileName cp exe InstallSet.cpp[222]: Winnow--Removing FileName cp exe InstallSet.cpp[222]: Winnow--Removing FileName cp exe InstallSet.cpp[222]: Winnow--Removing FileName cp exe InstallSet.cpp[242]: Target 0: Added Bundle bp xml Recovering from a discovery failure Troubleshooting connection errors If you receive HP SUM Connection Error or Discovery Failed messages, follow these troubleshooting tips: Ensure your workstation does not have an existing connection to the ADMIN$ share on the target IP address. If it does, it prevents HP SUM from connecting to the remote server s share because Windows only allows one connection from a client to a server s share. This can be 60 Troubleshooting

61 verified by entering net use at a command prompt. If a share to the target IP address \admin$ share exists, delete it, and then attempt the installation again. Ensure that the target IP address server s admin$ share is accessible. Validate the target server can be accessed by entering net use x: \\<ip_address_or_dns_name>\admin$ for the target server IP address or DNS name. When the connection is validated, ensure that it is deleted by entering net use x: /d at the command prompt. Ensure the user ID being used to connect to the target IP address server is part of the administrator s or Linux root equivalent group. If it is not, HP SUM blocks installation to the target. Ensure WMI is enabled and running on all Windows target servers. For Windows target servers, enter the user name in DOMAIN\USER format, where <user> is the administrative user name, and <domain> is either the NETBIOS computer name or the Active Directory domain name for this user account. For Linux, ensure the SSH port is not blocked by a firewall. For Linux, ensure that the target server can be contacted through SSH and that the scp command is available to securely send files to the target server. Ensure the firewall ports on any routers in the network. For more information, see Network ports used by HP SUM (page 57). The Symantec Endpoint Protection product blocks HP SUM ability to communicate with remote targets if the Network Threat Analysis feature is enabled. Disable this feature while HP SUM is in use on the workstation. Examine the trace directories for connection problems. For more information, see Collecting trace directories (page 59). Ensure the server has a valid serial number. HP SUM hangs during discovery If a system hang is observed during HP SUM discovery and the system is connected to external storage, in most cases disconnecting the external storage should resolve the issue. If discovering an ESXi 5 server, make sure you have installed the CIM providers from HP. You may download this within the "Offline Bundle Utilities" on ESXi 5 server downloads from the HP support website at or they come already bundled in the HP custom ESXi image HP SUM hangs during boot If the system hangs while booting, check that the IP address is not being used on your network. If this IP address is being used on the network, you might have to disconnect the server from the network to perform updates. Recovering from a loss of Linux remote functionality Configuring firewall settings When the Unable to Access Host message appears, the target firewall is enabled. By default, the target firewall is enabled in Linux. To recover remote Linux functionality, the target and host firewall must be disabled or reconfigured to allow IP traffic through the ports needed by HP SUM to deploy firmware. For more information about ports, see Network ports used by HP SUM (page 57). HP SUM hangs during boot 61

62 Recovering from a blocked program on Microsoft Windows Configuring Windows firewall settings The Windows Security Alert popup appears when a program is blocked from accepting connections from the Internet or a network. To set the rules for the Windows Firewall and Security Policy, click Unblock, and then set your firewall settings to the following: 1. Click Start Control Panel Administrative Tools Windows Firewall with Advanced Security Inbound Rules Remote Administration (NP-IN). 2. Select Enabled, and then select Allow the connections. For Direct to ilo support, you must enable ping. Recovering from operating system limitations when using a Japanese character set Displaying the user-specified reboot message using a Japanese character set when running on a Linux operating system You might specify a message to appear before the system shuts down during a reboot operation. When using a Japanese character set and running on a Japanese version of a Linux operating system, the message does not appear properly. Rebooting with the user-specified reboot message using a Japanese character set when running on a Windows operating system You might specify a message to appear before the system shuts down during a reboot operation. When using a Japanese character set and running on a Japanese version of a Windows operating system, the message causes the reboot not to occur automatically. For a successful reboot, you must click Exit. When the message is entered using CLI, the reboot message looks corrupted because the Japanese character set is not supported in CLI. Running in a directory path containing multi-byte characters HP SUM hangs when it is run in a directory path that contains multi-bye characters. 62 Troubleshooting

63 Do not run HP SUM in directories containing multi-byte characters in the path name. Recovering a lost HP SUM connection HP Smart Update Firmware DVD and SPP mounted using ilo virtual media When either ilo or NIC firmware are updated, the HP SUM connection might be lost. If this happens, it prevents the installation of components from continuing. You cannot boot into Offline Interactive mode while using the ilo Virtual Media. When you update the firmware, the connection to the ilo Virtual Media will be disconnected. Troubleshooting HP SUM in IPv6 networks If HP SUM cannot connect to the remote server, you might receive a Discovery Failed error. Discovery failures can be caused by third-party storage, failure to access the remote target server, and an inability to access system resources. For IPv6 networks, host discovery failures can be caused by the incorrect configuration of the IPv6 network. Troubleshooting HP SUM in IPv6 Windows Server 2003 environment To validate that the IPv6 network is configured correctly for HP SUM support, you must verify the following based on your operating system version. Validate that the addresses are site-local. Site-local addresses normally start with "FEC0:". Global and link-local IPv6 addresses are not supported when the remote target is Windows Server Validate that you can ping the remote target server. With Windows operating systems, you can still use the ping command to ping IPv6 addresses: ping <ipv6 address>. Ensure you can ping the IPv6 loopback address: ping ::1 Use the DNS hostname instead of IPv6 address to ensure the address is correct. Ensure you have installed the IPv6 protocol. It is not installed by default in Windows Server Be sure to reboot the server after installing the protocol to ensure addresses are properly obtained. Verify that you can connect to the admin$ share using the credentials within HP SUM by issuing the following command at a console prompt: net use * \\<ipv6-address>.ipv6-literal.net\admin$ /user:<username> net use * \\fec0::2.ipv6-literal.net\admin$ /user:administrator You might need to provide the password if you are using a user name that is not the same as you used to log in to the local system. All network shares require the use of the.ipv6-literal.net name string to be properly configured by Windows. NOTE: You do not need to use the.ipv6-literal.net suffix when entering IPv6 address into the HP SUM user interface or when passing IPv6 address using command line parameters to HP SUM. After you validate that you can access the admin$ share on the remote target server, HP SUM works unless other network or hardware issues exist. Ensure you have made the registry change on remote target servers. For more information, see Configuring IPv6 for Windows Server 2003 (page 55). Move back to an IPv4 network address to ensure HP SUM properly finds the remote target server without any issues. Recovering a lost HP SUM connection 63

64 You can always copy HP SUM to the target servers and execute using the local installation method. Troubleshooting HP SUM in IPv6 Windows Server 2008 environment To validate that the IPv6 network is configured correctly for HP SUM support, you must verify the following based on your operating system version. Validate that you can ping the remote target server. With Windows operating systems, you can use the ping command to ping IPv6 addresses: ping <ipv6 address> Ensure you can ping the IPv6 loopback address: ping ::1 Use the DNS hostname instead of IPv6 address to ensure the address is correct. Verify that you can connect to the admin$ share using the credentials within HP SUM by issuing the following command at a console prompt: net use * \\<ipv6-address>.ipv6-literal.net\admin$ /user:<username> net use * \\fec0::2.ipv6-literal.net\admin$ /user:administrator You might need to provide the password if you use a user name that is different from the one you used to log in to the local system. All network shares require the use of the.ipv6-literal.net name string to be properly configured by Windows. After you validate you can access the admin$ share on the remote target server, HP SUM works unless there are other network or hardware issues. Troubleshooting HP SUM in IPv6 Red Hat and Novell SUSE-based Linux environments Verify that you can establish an SSH connection to the remote target server using the credentials within HP SUM by issuing the following command at a console prompt: ssh <ipv6 address> SSh 2101:db8:0:1::9 You must enter the root password for the target Linux server at the console to complete the IPv6 connection. Validate that you can ping the remote target server. In Linux, you need to use the ping6 command to ping IPv6 addresses: ping6 <ipv6 address>. Ensure you can ping the IPv6 loopback address: ping6 ::1 Use the DNS hostname instead of IPv6 address to ensure the address is correct. Use ipconfig to validate you have IPv6 addresses assigned to your NICs. For more information about troubleshooting your configuration, see the Linux IPv6 How-To. For more information about setting up and troubleshooting IPv6 networks, see Getting Around IPv6 by Carla Schroder. Move back to an IPv4 network address to ensure HP SUM properly finds the remote target server without any issues. HP SUM can always be copied to the target servers and executed using the local installation method. For more information, see Deployment modes (page 11). 64 Troubleshooting

65 Microsoft Windows displays a Found new hardware message During the discovery progress, HP SUM might display the following message: Found New Hardware. This message appears because one of the self-discovery components is loading a new driver and the Windows operating systems discovers it as a new piece of hardware. Non-matching systems error reported when building source Linux RPMs or installing Linux RPMs built from source If HP SUM reports non-matching systems errors when trying to build source Linux RPMs or installing Linux RPMs built from source, the operating system on the target server does not match the operating system from which you are running HP SUM in one of the following ways: The distribution of the operating system does not match. For example, RHEL 6.0 and RHEL 6.1 would be a mismatch. The architecture of the two operating systems does not match. For example, one server might be running an operating system with x86 architecture and the other with x86_64 architecture. The kernel version running on the two systems does not match. Resolution options: 1. Run HP SUM on the target server itself instead of remotely deploying HP SUM. 2. Build the driver RPM locally and take the resulting RPM file from the standard location (for example, /usr/src/redhat/rpms/i686/<driver>.rpm) and then copy it back into the HP SUM repository. HP SUM will pick up the pre-built RPM and enable you to deploy it anywhere you choose. Linux component version discrepancy for source RPMs You might observe differences in the RPM component name which might appear to be a version mismatch for the component on the Select Item to be Installed screen and the Installation Results screen. This is caused by the RPM build phase. The resulting component is actually the same version. The RPM build adds information, so it is technically the same component. For example, if you select the component HP NC Series Mellanox 10GBE Driver for Linux on the Select Items to be Installed screen, it appears as hp-minx-en src.rpm and on the Installation Results screen, it appears as hp-minx-en-kmp-default _ _5-1.x86_64.rpm. HP SUM displays No components found in the selected repository(ies) message The No components found in the selected repository(ies)error appears when at least one space is in the path name of the repository containing the components to be installed. To resolve this issue, make sure no spaces are in the path name. Installation of components failed with 'Update returned an error' when installing Linux RPMs When installing any component, if the installation fails, HP SUM displays Update returned an error message. To determine the installation failure, review the associated component log. However, when installing RPMs using HP SUM you might see this error when the RPMs for more than one Linux distribution are present in a single repository and a SPP bundle from the Select Bundle screen is not selected. In this scenario, when multiple versions of source RPMs exist, the RPMs that are not the latest are not installed and Update not needed or Not Updated-already current messages are Microsoft Windows displays a Found new hardware message 65

66 returned. HP SUM cannot determine which source RPMs go with which distribution because the RPMs do not contain any operating system information. To resolve this issue, ensure that you select the bundle for the operating system distribution on the Select Bundle screen for installation or remove the RPMs from the directory that are not applicable to the Linux distribution you are using. HP SUM fails on Windows hosts due to McAfee firewalls This is a known issue with McAfee that McAfee firewalls block HP SUM traffic. To resolve this issue, enable the port traffic associated with the HP SUM application by performing the following steps: 1. From the system tray, click the McAfee icon. 2. Select Manage Features. 3. Select McAfee Host Intrusion Prevention. 4. Select the Activity Log tab. As displayed in the following image, in the Message column, notice the entry similar to the following: Blocked Incoming TCP from the HOST ( ) during execution of HP SUM. 5. From the menu, select Task Unlock Interface. 6. Enter the password of the McAfee user interface. 7. Select the Firewall Policy tab. 8. On the bottom of the screen, click Add (Add new rule). 9. From the screen image, use the following settings for the new firewall rules on your system. 66 Troubleshooting

67 10. Click OK to ensure new firewall rules have been implemented. 11. Restart HP SUM. Performing these steps allows HP SUM to function, although after a period of time (ranging from minutes to hours), McAfee disables HP SUM access. HP SUM prevents an upgrade of Virtual Connect firmware if the VC health is invalid or bad health state. Virtual Connect firmware can be upgraded using HP SUM only if the health state of the VC is in a good state. If the health state is invalid or bad, HP SUM does not upgrade the VC firmware. HP SUM prevents an upgrade of Virtual Connect firmware if the VC health is invalid or bad health state. 67