HP Smart Update Manager User Guide Abstract This guide is intended for individuals familiar with the configuration and operation of Microsoft Windows, Windows Server 2003 and 2008, 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.
© Copyright 2011 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.
Contents Introduction .................................................................................................................................. 6 HP SUM overview ........................................................................................................................................ 6 Using this guide ........................................................................................................................................... 7 New features of HP SUM ....................
Generate a Report............................................................................................................................ 30 View a Report .................................................................................................................................. 30 Scripted deployment ................................................................................................................... 31 Command-line interface ........................................................
Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2003 environment ........................ 70 Troubleshooting HP Smart Update Manager in IPv6 Windows Server 2008 environment ........................ 71 Troubleshooting HP Smart Update Manager in IPv6 Red Hat and Novell SUSE-based Linux environments . 71 HP SUM found new hardware message........................................................................................................
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 HP servers and network-based targets such as iLOs, OAs, and VC Ethernet and Fibre Channel modules.
• Support for updating firmware on network-based targets such as the OA, iLO 2/iLO 3 through Network Management Port, and VC Ethernet and Fibre Channel modules on HP ProLiant servers NOTE: HP SUM does not support third-party controllers. This includes flashing hard drives behind these controllers. Using this guide HP SUM is included with many different deliverables.
manner, you must have the user name and password available for each remote server available. Alternatively, you can use a domain account on the local administrative system that has administrator privileges on the target servers. • The beginning and ending IP addresses entered for the range of targets must both be on the same subnet. NOTE: HP Smart Update Manager requires the user to be logged in using Administrator credentials.
o • • e2fsprogs-32bit For SLES 11 x86 servers: o libstdc++33-3.3.3-11.9.i586 or later o libnl (required for QLogic and Emulex drivers) For SLES 11 AMD64/EM64T servers: o libstdc++33-32bit-3.3.3-11.9 or later o libnl (required for QLogic and Emulex drivers) Minimum requirements for Red Hat Enterprise Linux 6 servers NOTE: The following versions listed are needed as a minimum. Later versions of these might be used as well. NOTE: Ensure that each NIC has an IP address assigned.
o libxcb-1.5-1.el6.i686.rpm o libXau-1.0.5-1.el6.i686.rpm o libXrender-0.9.5-1.el6.i686.rpm o libXrandr-1.3.0-4.el6.i686.rpm o libXfixes-4.0.4-1.el6.i686.rpm o libXcursor-1.1.10-2.el6.i686.rpm o fontconfig-2.8.0-3.el6.i686.rpm o expat-2.0.1-9.1.el6.i686.rpm o expect-5.44.1.15-2.el6..rpm o zlib-1.2.3-25.el6.i686.rpm o libstdc++-4.4.4-13.el6.i686.rpm o net-snmp-5.5-27.el6..
HP SUM version Delivered with Support and limitations • packs 8.50 HP ProLiant Support Pack for Linux 8.50 4.0.2 • HP Smart Update Firmware DVD 9.10 4.1.0 • HP ProLiant Support Pack for Windows No support for Integrity server firmware or support packs 8.60 HP ProLiant Support Pack for Linux 8.60 • No support for Integrity server firmware or support packs 4.2.0 • • HP ProLiant Support Pack for Linux 8.
Scenario Description HP SUM command • • Do not require scripting Want to select the components to be installed Scripted deployment on a Use this scenario when you: • Windows: hpsum -s local host (Run HP SUM • Are familiar with from a network share on a command line tools • Linux: local server.) • Are deploying .
Scenario Description (use the HP Smart Update Firmware DVD with embedded HP SUM to • deploy firmware updates to one or more blades) • • Update an existing enclosure manually For more information, see the HP website (http://www.hp.com/go /matrixcompatibility).
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. If you use OA version 2.51 or later, click the Rack Firmware link on the main OA website for a list of all major firmware versions deployed in your enclosure. HP supports the current and two previous versions of the HP Smart Update Firmware DVD.
Firmware Types Supported by HP SUM HP StorageWorks MDS Yes 600 enclosure firmware No MSA 2000 firmware (P2x00 firmware) D2600/D2700 firmware Yes when attached through a Smart Array controller 3Gb/s SAS BL switch Yes, online only FCoE/CNAs Yes, in offline mode only because of FCoE/CNA firmware limitations 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.
HP SUM User Interface Deployment scenarios HP SUM deploys firmware and software on a local host or one or more remote hosts. Except for Integrity servers, the remote hosts must be online and running the same operating system as the system running HP SUM. For example, when the remote hosts are running Linux, HP SUM must also be running on a Linux operating system. However, this is not true for Integrity servers.
Source selections Use the Source Selections screen to: • Select repositories that contain updates • Add repositories • Edit repositories • Configure repository components • Select whether to pull updates from the HP FTP site • Select whether to display firmware-only, software-only, or both types of updates in each repository Repositories are the directories that contain the bundles, also called release sets, and individual smart components HP SUM uses to update targets.
• • Name—This field displays the repository name. Select the repositories you want to use by checking the box next to the repository name. If you want to edit a repository, highlight the entire line to activate the Edit and Remove buttons. o HP SUM automatically creates a repository named Default. This repository is the folder that holds the HP SUM application. o The HP FTP site (ftp://ftp.hp.com) contains the latest versions of the firmware and software components available from HP.
4. Enter the User ID (if necessary). 5. Enter the Password (if necessary). 6. 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: • If a component is located in more than one repository, HP SUM will use the version that is in the repository that is listed highest on the Current Repositories table.
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. Edit Repository You can edit a repository to change its name or location, or to filter the repository’s updates.
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.
Select targets The Select Targets screen, allows you to do the following: • Select targets (for example, servers or enclosures) • Add targets • Edit targets • Remove targets • Generate and view reports • Manage groups • Enter credentials for 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.
The table displays the following target information: • Check box—Targets with selected checkboxes are updated. Click the checkbox 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 "Enter Target Credentials (on page 24).
Target types Supported target types include: • Server–a local host or a remote server. • iLO • Onboard Administrator • Virtual Connect Find and discover targets To search for multiple targets on a network: 1. Click Find Targets. 2. Select IP Address Range, Port Address, or LDAP Scan for Remote Targets, and then click OK. o IP Address–This option enables you to search a range of IP addresses in IPv4 or IPv6 format.
6. Click OK to save and close the dialog box. 7. Click Done. 8. In the Select Targets screen table, the Status field will display progress messages as HP SUM verifies the credentials you entered. Edit Target Use the following steps to edit a target: 1. Highlight a target, and then click Edit Target. 2. Type a brief description of the target (optional). 3. Enter the root or administrator username and password. 4. Click OK after entering the information to exit this page.
• Schedule updates • Select bundles to install on bundles and/or targets • Select components to install to bundles and/or targets • Generate and view reports • Abort an installation 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.
Abort installation Click Abort Installation to complete the installation of the current component and then abort the installation of the remaining components. View failed dependencies If a failed dependency occurs, then you must resolve it by ensuring the prerequisite libraries or the appropriate software or firmware components are available before proceeding with the installation. Click on the Failed Dependencies to see what changes you need to make.
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 failed dependency. 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. 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.
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. 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 and/or system failure.
1. Click Schedule Update. 2. Click Create Schedule, type a schedule description, 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.
Scripted deployment Command-line interface The HP SUM command-line interface enables you to script custom installations.
Command-line arguments HP SUM 5.0.0 recognizes the following command-line arguments. These arguments can be used to pre-populate the GUI in the Source Selection and Review/Install Updates screens. If you specify the target and credentials, then the /s[ilent] parameter is required to proceed with the installation. You cannot use some arguments, such as /romonly and /softwareonly together. Help Description /h[elp] or /? This argument displays command line help information.
Installation options Description "group_name" Manager graphical user interface. /b[undle] or This argument specifies bundles to install. Bundles to install can be specified with or without the /b[undle] argument. • • If using the /b[undle] argument, then only one bundle can specified with the argument. However, multiple /b arguments and bundles can be specified on the same line.
Installation options Description used, the AMS components are required, but the WMI components are optional. /use_wmi This argument specifies that components that use 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.
Reboot options Description • • All components selected for installation are successfully installed. At least one of the installed components requires a reboot to complete its installation. /reboot_message "reboot message" This argument displays the specified reboot message on remote consoles connected to the server you want to reboot. You must use this argument with the /reboot option or the argument is ignored.
Targets Description /oa_password This argument provides the password credential for OA associated with VC specified with "target" command-line parameter. Only one set of OA credentials can be specified with command-line parameters. You can only add multiple VC targets to command-line parameters with "target" parameter 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.
Using input files Description /inputfile “filename” This argument enables you to script the deployment of firmware and software to multiple remote systems at one time. For details of the file format and commands, see "Input files (on page 41)." /deleteinputfile This argument enables you to instruct HP SUM to delete the input file after it has been read in. Superdome 2 server commands Description /update_type This argument determines which Superdome 2 firmware is updated.
Command G7 and earlier /use_ams/use_wmi WBEM and SNMP /use_wmi/use_snmp WBEM and SNMP /use_ams/use_wmi/us WBEM and SNMP e_snmp The following table shows what updates if WBEM switches are currently installed: Command G7 and earlier no switches WBEM /use_ams WBEM /use_snmp WBEM and SNMP /use_wmi WBEM /use_ams/use_snmp WBEM and SNMP /use_ams/use_wmi WBEM /use_wmi/use_snmp WBEM and SNMP /use_ams/use_wmi/us WBEM and SNMP e_snmp Component configuration for Windows components only To config
o • HP System Management Homepage for Windows (cp008257.exe) HP Smart Update Manager o 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 from the 7.90 PSP and firmware components, which HP SUM determined are required to be installed, were installed.
Return codes 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.
Error level Meaning 1 The installation of the deliverable is successful. Reboot is required for the deliverable to be enabled. 2 The installation was not attempted because the version to be installed matches the version already installed. 3 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.
Command-line usage of input file The form for the HP SUM command line using an input file is hpsum -inputfile . The input file itself can contain the same flags on the command line. The usual command line flags can still be used with the -inputfile flag, and takes precedence over any given input file. The field can be enclosed in double quotes to enable paths with spaces.
Error reporting If errors are encountered in the input file, HP Smart Update Manager exits with a return value of -2 (bad parameter). The details of the location and nature of the error are recorded in hpsum_execution_log__
Parameter Description Possible values SKIPTARGET This parameter defines the behavior when a remote target has an existing HP SUM session in progress. This parameter enables you to skip the host if an existing HP SUM session already exists. A NO overrides the session in progress and reinitializes the installation framework on the remote host. This parameter causes the installation to continue and ignore errors.
Parameter SOFTWAREONLY USECURRENTCREDENTIAL WEBUPDATENEEDED USEPROXYSERVER Description installation. Do not use the /romonly parameter with the /softwareonly parameter. This parameter is a filter switch and allows the user to view only the software components required for installation. Do not use the /softwareonly parameter with the /romonly parameter.
Parameter CMALOCALHOSTRWCOMMSTR CMALOCALHOSTROCOMMSTR CMAMGMTSTATIONRWIPORD NS CMAMGMTSTATIONRWCOMMS TR CMAMGMTSTATIONROIPORD NS CMAMGMTSTATIONROCOMMS TR CMADEFTRAPCOMMSTR CMATRAPDESTINATIONCOM MSTR CMATRAPDESTINATIONIPO RDNS CMASYSCONTACT CMASYSLOCATION CMASTARTWEBAGENT Description location.
Parameter Description CMASTARTSTORAGEAGENT This parameter determines whether the HP Insight • Systems Manager Storage Agent is started when the health application loads. (Applies to Linux PSP • only.) YES (start the storage agent) NO (do not start the storage agent) CMASTARTNICAGENT This parameter determines whether the HP Insight • Systems Manager NIC agent is started. (Applies to Linux PSP only).
Parameter IP-RESTRICTED-LOGINS Description Possible values 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.) (for example, 10.1.1.1/255.255.255.0 ;10.2.2.2/255.255.255. 0) This parameter is used by the HP Systems Management Homepage to restrict login access. (Applies to Linux PSP only.
Parameter Description Possible values • 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.
COMPONENTSLIST = cp001234.exe, cp001235.exe BUNDLESLIST = bp001234.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 = 234.567.765.432 [END] USAGE: hpsum /inputfile Examples of inputfile.txt file: Example 1: The two targets are passed to be updated. The targets do not necessarily have to be OAs.
SKIPTARGET = NO SOURCEPATH = C:\fwcd\firmware-8.70-0\hp\swpackages [GROUPS] HOST=winserver UID=Userid PWD=password [END] Example 4 SILENT = YES IGNOREERRORS = ServerNotFound,BadPassword, FailedDepedencies SKIPTARGET = NO SOURCEPATH = C:\ fwcd\firmware-8.70-0\hp\swpackages FORCEALL = YES REBOOTALLOWED = YES REBOOTDELAY = 30 REBOOTMESSAGE = “Install complete, server will reboot in 30 seconds” [TARGETS] HOST=16.83.62.141 UID=Userid PWD=password [END] [TARGETS] HOST=16.83.61.
Report type Description Report file information* /report This argument generates a report listing, a target summary, and how the components in the repository affect the target. Ffor 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 The report files generated are: /inventory_report /firmware_report • • hpsum_Report_.html hpsum_Report_.
The following figure illustrates the HP SUM report in HTML format.
The following figure illustrates the HP SUM Inventory report in HTML format.
The following figure illustrates the HP SUM Firmware report in HTML format.
Advanced topics Configuring IPv6 networks with HP Smart Update Manager Starting with HP Smart Update Manager version 3.2.0, you can deploy to remote targets in IPv6-based networks for Windows® and Linux target servers. Using HP Smart Update Manager with IPv6 networks presents challenges for IT administrators. For Windows®-based servers, to communicate with remote target servers, HP Smart Update Manager uses either existing credentials or user-provided user name and password to connect to the admin$ share.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Para meters 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. Quit the Registry Editor. For more information about these steps, see the Microsoft® Knowledge Base Item 281308 on the Microsoft® website (http://www.microsoft.com).
After you connect to the target server, all other HP Smart Update Manager functions work identically. Log files for IPv6 hosts are stored with all other HP Smart Update Manager files in the \CPQSYSTEM\hp\log\ directory. Limitations of IPv6 for Windows Server 2003 and Windows Server 2008 Windows Server® 2003 requires site-local addresses to provide the necessary file-sharing capabilities needed by HP Smart Update Manager.
IPv6 addresses can be passed to HP Smart Update Manager in command line arguments or using the HP Smart Update Manager user interface. In the HP Smart Update Manager 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 Smart Update Manager supports both the short-name and full IPv6 notation.
Limitations of IPv6 for Linux The only current limitation of HP Smart Update Manager 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 Smart Update Manager uses this file to open a port in the IPv6 firewall to communicate with the Linux system that runs HP Smart Update Manager.
Troubleshooting Recovering from a failed ROM upgrade Recovering from a failed system ROM upgrade Use redundant ROM or ROMPaq to recover from a system ROM upgrade failure. Redundant ROM recovery When you flash the system ROM, ROMPaq writes over the backup ROM and saves the current ROM as a backup, enabling you to switch easily to the alternate ROM version if the new ROM becomes corrupted for any reason.
6. Power up the server. The server generates one long beep and two short beeps to indicate that it is in disaster recovery mode. If the disk is not in the correct drive, then the system continues to beep until a valid ROMPaq disk is inserted. The ROMPaq disk flashes both system ROM images. If successful, a sequence of ascending audible beeps is generated. If unsuccessful, a sequence of descending audible beeps is generated, and you must repeat the disaster recovery process. 7. Power down the server. 8.
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 Smart Update Manager 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.
Log Files Function screen. Hpsum_detail_log.txt This file contains the log data of the components. hpsum_execution_log_ _
• 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 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.
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 Smart Update Manager to deploy firmware.
Enabling ports in HP Smart Update Manager The ports that HP SUM uses cannot be configured. When HP SUM initiates communications to remote targets, it uses several well-known ports, depending on the operating system. For Windows, ports 138 and 445 are used to connect to remote targets (equivalent to remote and file print share functionality). For Linux, port 22 (SSH) is used to start the communications with the remote target.
Ports 80 or 63000-63005 For Integrity servers and c-Class OA, port 80 must be opened on the local system for the remote system to be able to pull the firmware file from the HP SUM HTTP server. The logs are passed to the target and retrieved using an internal, secure web server that uses port 80 if it is available or a random port between 63000 and 63005 if port 80 is not available.
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.
Troubleshooting HP Smart Update Manager in IPv6 networks If HP Smart Update Manager 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 Smart Update Manager in IPv6 Windows Server 2008 environment To validate that the IPv6 network is configured correctly for HP Smart Update Manager 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 . • Ensure you can ping the IPv6 loopback address: ping ::1.
HP SUM found new hardware message During the discovery progress, HP SUM might display the following pop-up 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. Similar pop-up messages might occur with Windows® 2008 operating systems when the Allow Non-bundle version option on the Select Bundle Filter screen is selected.
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.
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 (15.255.101.110) 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. 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. Downgrade of ProLiant G6 Server ROM from 2010.03.30 or later to 2010.03.01 or earlier using HP SUM is not supported When HP SUM is launched, all the available versions of ROM components in the repository are listed under Updates to be installed section of the Select Items to be Installed screen. If ROM downgrade is attempted from 2010.03.30 or later to 2010.03.
Technical support Reference documentation • To download the ProLiant Firmware Maintenance CD, Smart Update Firmware DVD, SmartStart, and other CD/DVDs, see the SmartStart download website (http://www.hp.com/go/ssdownloads). • For information about firmware support, see the ProLiant Firmware Maintenance CD/DVD Matrix (http://www.hp.com/servers/smartstart/supportmatrices). • For information about SmartStart support, see the SmartStart support matrices (http://www.hp.
• SUSE Linux (http://www.novell.com/linux) HP contact information For United States and worldwide contact information, see the Contact HP website (http://www.hp.com/go/assistance). In the United States: • To contact HP by phone, call 1-800-334-5144. For continuous quality improvement, calls may be recorded or monitored. • If you have purchased a Care Pack (service upgrade), see the Support & Drivers website (http://www8.hp.com/us/en/support-drivers.html).
Acronyms and abbreviations AMS agentless management services CLI Command Line Interface DNS domain name system FPGA Field Programmable Gate Array GUI graphical user interface HP SUM HP Smart Update Manager iLO Integrated Lights-Out iLO 3 Integrated Lights-Out 3 ISP Integrity Support Pack MP Monarch (primary) NIC network interface controller OA Onboard Administrator Acronyms and abbreviations 79
POST Power-On Self Test PSP HP ProLiant Support Pack RBSU ROM-Based Setup Utility RILOE II Remote Insight Lights-Out Edition II SEP Symantec Endpoint Protection SNMP Simple Network Management Protocol SOAP Simple Object Access Protocol SSH Secure Shell SSL Secure Sockets Layer UNC Universal Naming Convention WBEM Web-Based Enterprise Management WMI Windows Management Instrumentation Acronyms and abbreviations 80
Index A advanced topics 56 arguments 32 authorized reseller 77, 78 B blocked HP Smart Update Manager, recovering from 66 bundle filter options 19, 20, 27 C CLI (Command Line Interface) 31, 32, 38 command line arguments 32 command line examples 38 command line interface, using 31 command line syntax 31 command-line usage of input file 42 component configuration 20 component configuration, Windows 38 components 28, 73 configuring components 20 configuring firewall settings 66 creating input files 41 credent
M maximizing a window to single display 73 minimum requirements 7 minimum requirements for Linux servers 8 minimum requirements for Windows servers 7 mounting virtual media 69 N non-matching system error 72 O operating system problems 69 operating systems 69, 77 overview, HP Smart Update Manager 6 P parameters 43 proxy settings 18 selecting bundles to filter, first time 27 selecting components to install 28 server virtualization detection and support 60 source selections 17 support 77 T target interfac
