HP ProLiant Firmware Maintenance CD User Guide Part Number 447788-009 December 2009 (9th Edition)
© Copyright 2007, 2009 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 .................................................................................................................................. 5 HP ProLiant Firmware Maintenance CD overview ............................................................................................ 5 Minimum requirements .................................................................................................................................. 5 New features ..................................................
Configuring IPv6 networks with HP Smart Update Manager............................................................................ 62 Configuring IPv6 for Windows Server 2003 ....................................................................................... 62 Configuring IPv6 for Windows Server 2008 ....................................................................................... 65 Configuring IPv6 for Linux .......................................................................................
Introduction HP ProLiant Firmware Maintenance CD overview The HP ProLiant Firmware Maintenance CD provides a collection of HP Smart Update Manager and firmware in an ISO image that can be used either in an offline, interactive mode, or online in either a scripted or interactive mode. The Firmware Maintenance CD provides firmware for supported HP servers and options. The Firmware CD contains all the firmware for the BladeSystem enclosures with the exception of the Virtual Connect firmware.
• Sufficient hard-drive space of at least twice the file size of the components to be deployed • WMI enabled NOTE: When attempting to use the remote deployment functionality of HP Smart Update Manager on any edition of Windows Server® 2008, you must ensure that the File and Print Services feature is enabled and that the File and Print Services exception has been enabled in the Windows® firewall. Failure to do so prevents HP Smart Update Manager from deploying remote Windows® target servers.
• o /report generates a target summary and how the components in the repository affect the target (For example, whether each component applies to the target or not.) o /inventory_report generates a report of the components in the specified repository. Accepts command line parameters from an input file Supported firmware The Firmware Maintenance CD provides the means to update the following firmware.
***The HP 3Gb SAS BL Switch firmware can only be updated by uploading a bin file through the Virtual Storage Manager (VSM) product. This firmware is currently delivered as a binary image file on the HP website and must be downloaded and manually upgraded. Because firmware might be able to update only in online or offline mode for some components, you might need to execute the HP Firmware Maintenance CD both online and offline to update all the firmware in an enclosure.
Online deployment To deploy components online: 1. Choose one of the following options: o Insert the Firmware Maintenance CD. The Firmware Maintenance CD interface opens. NOTE: In Linux, if the autostart is not enabled, you must manually start the Firmware Maintenance CD. o Insert the USB drive key. Manually start the interface and open a CLI.
For Windows® operating systems, the HP USB Key Creator for Windows utility must be downloaded from the HP website (http://www.hp.com) and installed on a workstation. After installation, the utility places a shortcut in the HP System Tools folder in the Programs start menu. To create your bootable drive key and copy the contents of the CD: 1. Place your HP USB drive key in an available USB port. 2. Select the HP USB Key Utility shortcut in the HP System Tools folder. 3.
Using a hard drive 1. Copy the contents of the \compaq\swpackages directory from the CD or ISO image to a directory on the hard drive where HP Smart Update Manager will be executed. 2. Ensure that execute privileges are available in Linux by using the chmod 700 * command. By default, the files are copied off the CD in Linux as read-only with no execution privileges. 3. Copy any updated files into the same directory where the files were copied in step 1. 4.
If HP Smart Update Manager detects a TPM, a pop-up 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.
6. Close all the windows, and then start the firmware update. To enable advanced startup options, use the following command: cscript manage-bde.wsf -protectors -disable c: When the firmware update process is completed, the BitLocker Drive Encryption support can be reenabled 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. cscript manage-bde.
If the TPM is detected and enabled with Option ROM Measuring, the installation is not silent, and a system ROM must be updated. A pop-up warning message appears. After OK is selected, you can continue. The installation is not canceled. If the TPM is detected and enabled with Option ROM Measuring, the installation is silent; the /tpmbypass switch is not given, and any firmware updated must be applied to the server. No pop-up warning appears.
Firmware Maintenance CD powered by HP Smart Update Manager Deployment scenarios HP Smart Update Manager deploys smart firmware components on a local host or one or more remote hosts. The remote hosts must be online and running the same operating system as the system running HP Smart Update Manager. For example, when the remote hosts are running Linux, the HP Smart Update Manager must also be running on a Linux operating system.
Scenario Description more host systems. Graphical deployment on a local host To deploy components to a single local host, use the HP Smart Update Manager GUI. 1. Ensure all minimum requirements are met as described in "Minimum requirements (on page 5)." 2. Ensure that the components to be deployed are accessible to the local host. For information about performing the deployment using the GUI, see "Local host installations using the GUI (on page 17).
For more information about performing the deployment using the graphical interface, see "Multiple-host installations using the GUI (on page 32)." To deploy components to multiple remote hosts using the CLI: 1. Ensure that all minimum requirements are met as described in "Minimum requirements (on page 5)." 2. Ensure that the components to be deployed are accessible to the administrative system. 3. Create a script to customize the deployment. For more information, see "Scripted deployment (on page 46).
The Source Selections screen allows you to specify where to get components for updating the targets by using one or more of the following methods: • Directory—This option enables you to select the directory where the components you want to deploy are located. It can be located on a locally accessible file system. The default location is the directory from where HP Smart Update Manager is executed. To change the directory value, click the Browse button to launch a select-directory menu.
o Proxy Details—Enter the proxy information in the Proxy Details group box to be used to access the HP FTP site. To auto-detect the proxy information, click the Detect Proxy button. If you use a proxy server in accessing the HP FTP site, the proxy information is saved and prepopulated on the next deployment. NOTE: HP Smart Update Manager does not support FTP over HTTP proxy. FTP downloaded from HTTP proxy fails.
The Download Permission screen lists the available updates found on the HP FTP site. You can select or clear the updates you are allowing to download. The Download Permission screen includes the following buttons: • Select All—Selects all available components for download. • Clear All—Clears all components selected for download. • Cancel—Exits the Download Permission screen and returns to the Source Selections screen. • OK—Downloads all selected components.
The following columns are included in the Select Installation Host(s) screen: • Host Name—Displays the host IP address or DNS name. • Type—Categorizes the system as a host or group. • Last Used—Enables you to sort the list by the most recently used hosts. • Description—Displays the user-defined description given to a host. When the Remote Host or Group option in the Select Installation Host(s) screen is selected, you can sort your view of the host list by selecting Only Hosts, Only Groups, or Both.
Selecting components to install When the discovery process ("Selecting an installation host" on page 20) is complete, the Select Items to be Installed screen appears. The Select Items to be Installed screen displays information about which components are available for installation on your system and enables you to select or deselect components to install. The Select Items to be Installed screen includes the following sections: • Product—Lists the system on which the selected items are installed.
The Select Items to be Installed screen also includes the following buttons: • Select All—Selects all available components for installation. • Deselect All—Clears all components selected for installation. • Default—Restores the selections in the product installation pane to the default view, which is based on the existing configuration of the local system. • Exit—Exits HP Smart Update Manager. • Install—Installs all selected components.
• Updates to be Installed—The components in this section can be installed on your system. • Optional Updates—The components in this section are not selected for installation by default, even if the product is not already installed or is installed but not up-to-date. To include the component in the installation set, you must select the component.
Icon Text Description x Critical Action X components are not ready for installation due to failed dependencies, where x is the number of components. The installation cannot proceed until the dependencies are met or the component is deselected for installation. Reboot section The reboot section of the Select Items to be Installed screen enables you to specify preferred reboot behavior. To instruct the system to reboot after updates are installed: 1. Click Reboot System After Installation. 2.
Component selection pane The component selection pane of the Select Items to be Installed screen displays (by component number order, unless a dependency causes the installation order to change) all components available for installation based on your server and hardware options. The HP Smart Update Manager checks each component for dependencies, if the component is already installed on the system, or if it requires a reboot after installation. Items available for installation are selected by default.
If a failed dependency occurs, you must resolve it before proceeding with the installation. Depending on the issue, you must locate software or firmware components in the Firmware Maintenance CD or HP website (http://www.hp.com). The following figure shows the Failed Dependencies screen.
Installation options You can specify firmware upgrade behavior for installable components by selecting one or more options from the Additional Options field. Depending on the component type, one of the following screens appears. The first screen applies to firmware and software components and the second screen applies only to firmware. CAUTION: Updating the firmware while a shared device is in use can lead to data loss.
• Select Allow Rewrites to enable HP Smart Update Manager to overwrite the current firmware version with the same version. • Select Allow Shared Devices to upgrade firmware in a shared storage environment. NOTE: HP Smart Update Manager does not support Allow Downgrades or Allow Rewrites for the HP Virtual Connect Ethernet and Fibre Channel Modules for c-Class BladeSystem firmware component.
Viewing the installation results When the installation is complete, the Installation Results screen appears. The Installation Results screen is divided into the following columns: • Product—Specifies the name of the installed component. To see the component version history, click the version number. • Status—Specifies the installation status of the component. The following icons may appear in the Status column. Icon • Icon Text Description Success The component was installed successfully.
To see additional details, click View Installation Log. The Installation Results screen also includes the following buttons: • Reboot Now—Reboots the server. (This button is available for local installations only.) • Exit—Exits the HP Smart Update Manager. NOTE: After updating hard drives in external enclosures such as MSA20, you must power cycle the external enclosures. The Reboot button in HP Smart Update Manager only reboots the server but never power cycles an external enclosure.
• For Linux operating systems, these files are located in subdirectories named according to the IP address of each host in the /var/hp/log subdirectory of the local host. The directory containing the local host information is named localhost instead of being named after the IP address. There is a new file that contains detailed information on the execution of HP Smart Update Manager. • For Windows® operating systems, the filename is C:\cpqsystem\hp\log\hpsum_execution_log__
To add hosts, see "Managing hosts (on page 33)." To add groups, see "Managing groups (on page 37)." To continue with the deployment process: 1. Select one or more hosts or groups. 2. To continue, click Next. 3. Enter the credentials for the host ("Entering credentials for hosts" on page 40). 4. Click OK to proceed, as described in Selecting components to install on multiple hosts (on page 42). 5.
To add a host: Firmware Maintenance CD powered by HP Smart Update Manager 34
1. Click Add Host. The New Host dialog box appears. 2. Select the method to add a host from the following: o Enter the DNS name of the host you want to add. o Enter the IP address of the host you want to add. o Enter the IP address range of the hosts you want to add. The starting and ending IP addresses must both be on the same subnet. When using the IPv6 format, the last field in the ending address is limited to 32 targets.
1. On the Manage Hosts screen, click the Edit Host button. The Edit Host dialog box appears. 2. Edit the Host Name and Description. 3. Click OK. To delete a host: 1. On the Manage Hosts screen, click the Delete Host button. 2. When the confirmation screen appears, click Yes.
Managing groups To add, edit, or delete groups, click the Manage Groups button. The Manage Groups screen appears.
1. Click Add Group. The Edit Group dialog box appears. 2. Enter a group name. 3. Enter an optional user-defined description given to the group to be added. 4. Select the hosts to be added to the group from the Available Hosts pane. You can add new hosts from this screen by clicking the New Host button. For more information on adding hosts, see "Managing hosts (on page 33)." 5. Click the Enter button to move the selected hosts to the new group. 6. Click OK.
1. Select the group, and then on the Manage Groups screen, click the Edit Group button. The Edit Group dialog box appears. 2. Edit the group name as needed. 3. Edit the optional user-defined description given to the host as needed. 4. Click the Enter and Remove buttons to add or remove hosts as needed. 5. Click OK. To delete a group: 1. Select the group on the Manage Groups screen, and then click the Delete Group button. 2. When the confirmation screen appears, click Yes.
Entering credentials for hosts When you select a single remote host, the Enter Credentials for Host screen appears. You must enter your username and password as the credentials for the host. To enter the credentials for the host, choose one of the following: • Select Enter Username and Password, and then enter the username and password. • Select Use Current Credentials to use the currently logged-in user's credentials.
When you select a group or multiple hosts, the Enter Credentials for Group screen appears. The screen separates the remaining hosts that still require credentials from the completed hosts. Each pane is divided into the following columns: • Name—Specifies the name of the host. • Status—Specifies the credentials status of the host. Icon • Text Description Entered The credentials for the host have been entered. Needs Credentials The credentials for the host have not been entered.
NOTE: If a TPM is detected and enabled, an HP Smart Update Manager pop-up warning message appears after the Discovery Progress screen. You must read the message and determine how to proceed. For more information, see Trusted Platform Module (on page 11). Selecting components to install on multiple hosts The Select Items to be Installed screen displays the server hosts and their status information.
Icon Text Description Nothing to Install The host is already up-to-date. Host Skipped Due to Existing HPSUM Session The host is skipped due to an existing HP Smart Update Manager session. Action Required The host is not ready for installation. Click View Host for additional information. Discovery Failed The host is not ready for installation. The detection of installed hardware, software, and firmware has failed.
Viewing the installation results for multiple hosts When the installation is complete, the Installation Results screen appears. The Installation Results screen is divided into the following columns: • Host—Specifies the IP address or DNS name of the host. • Status—Specifies the overall installation status of the components on the remote host. Icon Text Description Success The host was updated successfully. Nothing to install The host is already up-to-date.
To view single-host installation results, double-click the host or select the host, and click View Host. Proceed as described in "Viewing the installation results (on page 30).
Scripted deployment Command line interface The HP Smart Update Manager command line interface enables you to script custom installations.
Command line argument Description /h[elp] or /? This argument displays command line Help information. /f[orce] This argument enables you to override or downgrade an existing component installation. This argument produces the same results as /f:software. /f[orce]:bundle This argument enables you to override or downgrade the existing installation of components in the selected bundle.
Command line argument Description /s[ilent] This argument 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.
Command line argument Description must be a mapped file share and not in Universal Naming Convention (UNC) format. If you do not specify this argument, the directory containing hpsum.exe or HP Smart Update Manager is used by default. This populates the Directory box on the Source Selection screen. The logged-in account must have access to this location. The /user and /passwd arguments do not have any effect when attempting to access the file share.
Command line argument Description can cancel or terminate HP Smart Update Manager. /user or /username This argument enables you to log in to HP BladeSystem c-Class Onboard Administrator with your user ID. /psswd This argument enables you to use the password for the user ID specified in the /user parameter. The password is used to log in to remote hosts and HP BladeSystem c-Class Onboard Administrators.
Component configuration for Windows components only To configure components without using the HP Smart Update Manager GUI, issue the command, hpsum_config . This command presents the same configuration screens seen in the HP Smart Update Manager GUI. You must run this command from a CD or other read-only media, or the component cannot be configured. Configuration for a given component only needs to be executed once.
• hpsum /b BP000315.xml /f:bundle /softwareonly Results: All the software components from the 7.80 PSP, which HP Smart Update Manager determined needed to be installed, were installed. No firmware was installed. Example 3: This command line input deploys firmware: hpsum /romonly Results: All the firmware components, which HP Smart Update Manager determined needed to be installed, were installed. No software was installed.
Return code Value Linux Window s Text SUCCESS_REBOOT 1 1 1 The installation was successful, but a reboot is required. SUCCESS_NOT_REQUIRED 3 3 3 The component was current or not required. FAILURE_GENERAL -1 255 255 A general failure occurred. See the error log for details. FAILURE_BAD_PARM -2 254 254 A bad input parameter was encountered. FAILURE_COMPONENT_FAILED -3 253 253 The installation of the component failed.
Error level Meaning 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 smart component does not support the environment. The supported hardware is not present, not enabled, or in a state that an installation could not be attempted. There is nothing for the component to accomplish.
[TARGETS] HOST = schinta1 HOST = schinta2 UID = root PWD = root123 HOST = 234.567.765.432 [END] Example 1: The two targets are passed to be updated. The targets do not necessarily have to be OAs. They can be any target supported by HP Smart Update Manager. DRYRUN = YES SILENT = YES [TARGETS] HOST = BL465C-01 HOST = 192.168.1.2 [END] Example 2: A host is passed along with the user ID and password to use.
• 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 parameters and their values. Each configuration setting must appear on a fresh line in the file along with its value. Comments start with a # character at the beginning of the line. Only one # is allowed on any line. • Target You can provide remote host targets to HP Smart Update Manager.
Parameter Description Possible Values 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 (unless the IGNOREERRORS = "Failedependencies" parameter is supplied), and an error message is written to the log file. /forceall This argument forces both firmware and software components.
Parameter Description Possible Values files to be filtered on. /allowupdatebundle This argument is a filter switch and enables you to install newer versions of components defined in a PSP or firmware bundle. This argument enables these components to replace the older versions of the same component that might have shipped with the bundles. YES, NO /skiptarget This argument defines the behavior when a remote target has an existing HP Smart Update Manager session in progress.
Parameter Description Possible Values the command line, and multiple bundles are in the directory, this parameter allows HP Smart Update Manager to use the bundle with the latest version for installation. /dryrun This argument simulates the installation for a test run. Nothing is installed. YES, NO /options This parameter can be used to specify the HP Smart Update Manager CLI options inside the input file and this will override the configuration settings.
Parameter Description Possible Values see only the software components needed for installation. Do not use the /softwareonly argument with the /romonly argument. /usecurrentcredentia l This argument enables the credentials of the local host to be used as the credentials to access the targets instead of providing the username and password explicitly for each target. The assumption is that the current credentials are valid for the targets being accessed. (Applies to Windows® operating systems only.
Advanced topics Deploying firmware and software simultaneously HP Smart Update Manager utility enables you to deploy firmware and software components simultaneously. Only Windows® online deployments support deploying firmware and software components from Windows® PSPs and HP BladeSystem online bundles simultaneously. The latest Microsoft® Windows® PSP, bundles, and firmware components must be in the same directory and the cp*.exe file added to the repository to deploy simultaneously.
Server virtualization detection and support HP Smart Update Manager, running in the context of a Windows® PSP, supports server virtualization that runs on a Windows® host. However, HP Smart Update Manager, running in the context of a Windows® PSP, does not run on a VMware host or on a guest operating system environment regardless of what host hypervisor you use.
Before using HP Smart Update Manager 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. Start the Registry Editor (Regedt32.exe). 2. Locate and click the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Para meters 3. On the Edit menu, click Add Value. 4.
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.
Configuring IPv6 for Windows Server 2008 HP Smart Update Manager provides the most robust support for remote deployment when using Windows Vista® as a client to Windows Server® 2008-based servers. Using HP Smart Update Manager 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.
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 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. This means that link-local and global IPv6 addresses are not supported as remote targets with HP Smart Update Manager. Windows Server® 2008 or Windows® environments do not have any known limitations to using 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 Smart Update Manager generates a set of debug trace logs located in the %TEMP%\hp_sum directory on Windows systems and \tmp\hp_sum on Linux systems. These files contain internal process and debug information, which can be useful in determining HP Smart Update Manager failures. NOTE: To break out to a Linux console while booted to the Firmware Maintenance CD, press Ctrl Alt d b x. Each key (d, b, x) is hit in succession.
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 cp011301.exe and cp011500.exe, and the HP BladeSystem Firmware Update Bundle for Windows represented by bundle file bp000648.xml were added to the installation set.
• 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 as documented in the Enabling ports in HP Smart Update Manager section of this document. • The Symantec End Point Protection product (SEP) blocks HP Smart Update Manager ability to communicate with remote targets if the Network Threat Analysis feature is enabled.
Recovering from a blocked program on Microsoft Windows Configuring Windows firewall settings The Windows® Security Alert 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.
scanning software from denying service to the application. The SOAP server is deployed on the remote target using the initial ports described above (ports 138, 445, and 22) and then allocates another independent port as documented below for its communications back to the workstation where HP Smart Update Manager is running. During shutdown of HP Smart Update Manager, the SOAP server is shutdown and removed from the target server, leaving the log files.
Ports 60000-60007 Random ports are used in this range to pass messages back and forth between the local and remote systems via SSL. These ports are used on the system running HP Smart Update Manager to send data to the target server. Several internal processes within HP Smart Update Manager automatically use the port from 60000 when no other application uses it. If there is a port conflict, the manager uses the next available one.
system, the message causes the reboot not to occur automatically. For a successful reboot, you must select the Exit button. Recovering from Fatal Error - application will exit message Running in a directory path containing double-byte characters When running in a directory path containing double-byte characters, the HP Smart Update Manager encounters a fatal error while trying to initialize. The HP Smart Update Manager cannot be run in directories containing double-byte characters in the path name.
Recovering a lost HP Smart Update Manager connection Mounting the Firmware Maintenance CD on virtual media When either iLO and NIC firmware are updated, the HP Smart Update Manager connection is lost and cannot install components. If an access error exists, HP Smart Update Manager cancels the installation. 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.
• Ensure you have made the registry change on remote target servers as mentioned in the HP Smart Update Manager Usage in a Windows Server® 2003 IPv6 environment ("Configuring IPv6 for Windows Server 2003" on page 62). • Move back to an IPv4 network address to ensure HP Smart Update Manager properly finds the remote target server without any issues. You can always copy HP Smart Update Manager to the target servers and execute using the local installation method.
• 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 (http://www.linux.org/docs/ldp/howto/Linux+IPv6-HOWTO/index.html). • For more information about setting up and troubleshooting IPv6 networks, see Getting Around IPv6 by Carla Schroder (http://www.enterprisenetworkingplanet.com/netsp/article.php/3634596).
Technical support Reference documentation To download the ProLiant Firmware Maintenance and other CDs, see the SmartStart download website (http://www.hp.com/go/ssdownloads). For general information on management products, refer to the ProLiant Essentials website (http://www.hp.com/servers/proliantessentials).
Acronyms and abbreviations GUI graphical user interface HBA host bus adapter HPSUM HP Smart Update Manager I/O input/output iLO Integrated Lights-Out iLO 2 Integrated Lights-Out 2 NIC network interface controller POST Power-On Self Test PSP ProLiant Support Pack RBSU ROM-Based Setup Utility RILOE II Remote Insight Lights-Out Edition II SAN storage area network Acronyms and abbreviations 83
SAS serial attached SCSI SCSI small computer system interface SOAP Simple Object Access Protocol SSH Secure Shell SSL Secure Sockets Layer WMI Windows Management Instrumentation Acronyms and abbreviations 84
Index A adding groups 37 adding hosts 33 advanced topics 61 Allow Downgrades 28 Allow Rewrites 28 Allow Shared Devices 28 arguments 46 array controllers 8, 22 audience assumptions 5 authorized reseller 82 B BladeSystem firmware 7 blocked HP Smart Update Manager, recovering from 75 C command line arguments 46 command line examples 51 command line interface, using 46 command line syntax 46 command line tools 15 command syntax 46 component configuration, Windows 51 component selection pane 25 component statu
hard drives 11 host field 22, 42 hosts 32, 33, 40 HP Onboard Administrator for HP c-Class BladeSystem 8 HP Smart Update Manager GUI 17 HP Smart Update Manager overview 5 HP website 8, 11, 17, 82 hpsum_detail_log.txt log 30 hpsum_log.
ROM, array controller 71 ROM, Lights-Out management 8, 71 ROM, storage 71 ROMPaq Disaster Recovery 70 WMI (Windows Management Instrumentation) 5 S SAS hard drive 8 scenarios, deployment 15 scripted deployment 16, 46 selecting an installation host 20 selecting components to install 22, 42 selections for single host 42, 44 server host pane 42 server virtualization detection and support 62 settings, reboot 25 shared storage, updating ROMs for 28 SLES (SUSE Linux Enterprise Server) 78 software and firmware de
