HP Smart Update Manager User Guide Part Number 613175-001 April 2010 (First Edition)
© Copyright 2010 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 Smart Update Manager overview ........................................................................................................... 6 New features of HP SUM 4.0.0 .................................................................................................................. 7 Minimum requirements ...............................................
Command-line usage of input file ..................................................................................................... 67 Input file format and rules ............................................................................................................... 67 File encoding ................................................................................................................................ 68 Error reporting .....................................................................
Reference documentation ....................................................................................................................... 103 Operating system information ................................................................................................................. 103 HP contact information ........................................................................................................................... 103 Acronyms and abbreviations ......................................
Introduction HP Smart Update Manager overview 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. • Deployment of software for single or one-to-many HP ProLiant servers that is supported in both Windows® and Linux environments.
New features of HP SUM 4.0.0 • Added the ability to deploy native Linux RPMs (Support for downloading RPMs directly from the HP website will be in a future release.
NOTE: When attempting to use the remote deployment functionality of HP SUM on any edition of Windows Server® 2008 or Windows Vista®, 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 SUM from deploying remote Windows® target servers. NOTE: For a current list of supported operating systems, see the PSP website (http://www.hp.com/servers/psp).
• • • • • o perl (needed to provide the libperl.so) o libnl (needed for QLogic and Emulex drivers) For Red Hat Enterprise Linux 5 AMD64/EM64T servers: o compat-libstdc++-296-2.96-132.7.2.i386 or later o Im sensors-2.8.7-2x86 64 or later o net-snmp-5.3.1-14.el5.x86- 64 or later o perl (needed to provide the libperl.so) o libnl (needed for QLogic and Emulex drivers) For SLES 10 x86 servers: o compat-2006.1.25-11.2.i586 or later o compat-libstdc++-5.0.7-22.2.
o kernel-devel (This RPM is needed to build RPMs from source, especially for Red Hat Enterprise server 5.3 and 5.4. Make sure you install the kernel-devel in addition to any kernel specific devel package such as kernel-xen-devel or kernel-PAE-devel.) o RPM build tools In addition, components that are compiled from source code (such as NIC drivers) require the presence of the following build tools: • gcc-2.96-108.1 or later • cpp-2.96-108.1 or later • binutils-2.11.90.0.
• Silent—For firmware and software deployments HP SUM provides scripted deployments in silent mode. HP SUM also enables you to use any mode to handle both local and remote deployments. HP SUM can run in both standard Windows® and Linux operating systems in online mode and in offline mode through special boot environments based on Linux boot kernels as long as the prerequisites are met. Use the following table to determine the correct execution mode for the server use case.
Scenario Description • Use this scenario when you: (Run HP SUM from a workstation and update a remote host over the network using scripts.
Deploying PSP for Microsoft Windows Beginning with the PSP for Microsoft® Windows® version 7.90 or later, the HP SUM utility enables you to deploy Windows PSP software and firmware components from a single, easy-to-use interface. This utility enables legacy support of existing software and firmware components while simplifying the overall deployment process. You do not have to run the SETUP executable files SETUPC.EXE, SETUPEX.EXE, and SETUP.EXE, because the HP SUM utility now provides this functionality.
CAUTION: The HP Smart Update Firmware DVD and its contents must be used only by individuals who are experienced and knowledgeable with HP SUM. Before using HP SUM to update firmware, back up the target server, and take all other necessary precautions so that mission-critical systems are not disrupted if a failure occurs. 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.
Component Supported by HP SUM Virtual Connect firmware* Yes, online only HP StorageWorks 600 Modular Disk System (MDS600)** Yes, offline only HP 3Gb SAS BL Switch firmware*** No Onboard Administrator Firmware**** Yes, online only HP Workstation Blade ROM Yes, offline only HP ProLiant Blade Servers ROM Yes HP ProLiant 100 Series Servers ROM Yes *Virtual Connect firmware components can also be downloaded from the HP website and they can be added to the HP Smart Update Firmware DVD by creating
4. The HP USB Key Creator formats the USB key. Ensure that you are using a USB key that is at least 1GB in size and does not contain any valuable files. For Linux, the USB key can be created manually: 1. Obtain SYSLINUX 3.75 or higher from http://www.syslinux.zytor.com (http://syslinux.zytor.com), and download it to a Linux workstation. 2. Install the SYSLINUX RPM obtained in step 1. 3. If a directory does not already exist, create one for the USB key mount point, for example, mkdir /usbkey. 4.
Deploying components not on Smart Update Firmware DVD If you have components that are not on the HP Smart Update Firmware DVD that you want to deploy, you can include other smart components to the HP SUM environment. To deploy software and firmware components that are not on the HP Smart Update Firmware DVD: 1. Obtain the components from the HP website (http://www.hp.com). 2. Create a bootable USB key, or copy the \hp\swpackages directory to the hard drive, and then remove the read-only bit. 3.
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 the /tpmbypass parameter for HP Smart Update Manager or the firmware update is blocked.
TPM scenarios The following table discusses the TPM detection scenarios that you might encounter. Scenario Result If the TPM is detected and enabled, 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, 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.
HP SUM User Interface Deployment scenarios HP SUM deploys firmware and software smart components and Linux RPMs 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 SUM. For example, when the remote hosts are running Linux, HP SUM must also be running on a Linux operating system. The following table describes typical HP SUM deployment scenarios.
4. Execute the script. Deployment to multiple remote hosts NOTE: A remote host can be the IP address or DNS name of a remote server, remote iLO NIC port, Virtual Connect Ethernet or Fibre Channel Module for c-Class BladeSystem, or BladeSystem Onboard Administrator. To deploy components to multiple remote hosts using the GUI: 1. Ensure that all minimum requirements are met as described in "Minimum requirements (on page 7)." 2.
Local host installations HP Smart Update Manager can deploy smart components on a local host or on one or more remote hosts. You can deploy components on a local host by using the HP Smart Update Manager GUI. To access the HP Smart Update Manager, see Deployment Options. Selecting the location to check for updates The Source Selections screen enables you to select components from a directory and the HP FTP site (ftp://ftp.hp.com) as a location for obtaining updates to your systems.
icon) are available for selection on the Select Items to be Installed screen. When using this method, both firmware and software components are available for selection depending on the options set on the Set Bundle Filter screen when PSPs or bundles are included in the components to be deployed. To limit only the appearance of available firmware components, use the /romonly command-line argument and use the /softwareonly command line argument for software components.
Download Permission Before starting any discovery, HP SUM searches the web digest for self-discovery components that must be downloaded for the discovery process. Self-discovered components are components including but not limited to NIC firmware and tape firmware that HP SUM uses to discover the hardware in the system. If the Check.ftp.hp.
Selecting an installation host To continue with the deployment process using a local host, select a host from the Select Installation Host(s) screen, and then click Next. The Select Installation Host(s) screen enables you to choose a host for component installation. By default, the first time you run HP SUM on a particular system, the only host available is the local host. However, you can also select remote hosts as your targets.
• Manage Groups—Enables you to add, edit, and delete groups. • Edit—Enables you to edit the selected host. • Next—Proceeds to the next step in the installation process where the local or remote system checks for already installed items. • Exit—Exits HP SUM. NOTE: When running on a Linux system and the expect-5.x package is not installed, HP SUM displays a pop up error message reporting that the package is missing and you are not able to deploy to remote systems.
The Select Bundle Filter screen is divided into two sections. The upper part of the screen includes the product and status information: • Product—Displays the product name of the predefined bundles found on the system. It also provides information about available versions. To view the bundle version history, click the version number in the Product column. To view the bundle contents, click View Contents. • Status—Indicates whether the installation is ready to proceed.
To proceed with the deployment process, click OK. NOTE: If a PSP or bundle that supports the target's operating system is not present in the repository, HP SUM might display a message box indicating that a supported bundle is not present in the repository. Selecting components to install When the discovery process is complete and the desired bundle has been selected, the Select Items to be Installed screen appears.
The following image illustrates the HP SUM Select Items to be Installed screen when installing Linux RPMs. The Select Items to be Installed screen includes the following sections: • Host—Lists the system on which the selected items are installed. • Status—Indicates if the installation is ready. • Reboot section—Enables you to specify reboot settings and determine when reboots occur. • Component selection pane—Enables you to specify which components to install.
• 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 SUM. • Install—Installs all selected components. • Import Configuration (Linux RPMs only)—Provides the option to import the configuration file. • Save Configuration (Linux RPMs only)—Provides the option to save the configuration file on the local system.
• 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) components available for installation based on your server and hardware options. HP SUM 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.
• Additional—Shows additional information for the components if needed. Examples include links to installation options, buildable source RPMs, non-bundle products, and so on. NOTE: For Linux source RPMs, if the source packages are not installed, then the source RPMs are not available for selection. To deploy any Linux source RPMs, ensure that the appropriate source packages are installed before starting HP SUM.
If a failed dependency occurs, then you must resolve it before proceeding with the installation. Depending on the issue, you must locate software or firmware components in the HP Smart Update Firmware DVD, bundles, HP ProLiant Support Packs, or the HP website (http://www.hp.com). The following figure displays the Failed Dependencies screen.
If a component displays as build failed, you must resolve the issue before proceeding with the installation.
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. CAUTION: Updating the firmware while a shared device is in use can lead to data loss. Before enabling the Allow Shared Devices option, be sure any other servers sharing the selected devices are offline.
• 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 view the component version history, click the version number. • Status—Specifies the installation status of the component. The following icons might appear in the Status column. Icon • Icon Text Description Success The component was installed successfully.
NOTE: Some of the Linux RPMs require the target server to be rebooted after the RPM is installed. However, the Reboot Needed message does not appear on the Installation Results screen for Linux RPMs since that information is not available to HP SUM. HP recommends that you reboot the target server after installation of any Linux RPMs. To view the list of RPMs which require a reboot, see the download page of the HP ProLiant Support Pack for Linux on the PSP website (http://www.hp.com/servers/psp).
• hpsum_detail_log.txt log—Contains all of the installation details, including errors, for each component installed The log files can be found in the following locations: • For Windows® operating systems, these files are located in subdirectories named according to the IP address of each host in the \CPQSYSTEM\hp\log subdirectory on the boot partition of the local host. The directory containing the local host information is named localhost instead of being named after the IP address.
NOTE: Local hosts cannot be included in a list with remote hosts or in a group. When selecting an iLO or iLO2 as a host, only the iLO firmware can be updated. The server host must also be selected to update all other firmware and software components on the same physical server. The iLO firmware can be updated by either selecting the iLO or the server host. To add hosts, see "Managing hosts." To add groups, see "Managing groups (on page 46)." To continue with the deployment process: 1.
NOTE: Local hosts cannot be included in a list with remote hosts or in a group. When selecting an iLO, iLO2, OA, or VC as a host, only the firmware component for that hardware can be updated. The server host must be selected to update all other firmware and software components. The iLO firmware can be updated by either selecting the iLO or the server host.
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 Edit Host. 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 Delete Host. 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." 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 credentials of the user currently logged in.
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.
To enter the credentials for the host, perform the following steps: 1. In the left pane, select the host from the list of hosts requiring credentials. If all credentials are the same, to select all the hosts on the list, click Select All. 2. To enter the required credentials and move the selected host to the Completed Hosts pane, click Enter. 3. To continue, click Next.
HP SUM User Interface 52
Selecting bundles to filter on multiple hosts If the system discovery finds one or more predefined bundles, the Select Bundle Filter screen appears. If you specify a bundle on the command line when starting HP SUM, this screen does not appear. For more information about the screen, see "Selecting bundles to filter (on page 26)." To proceed with the installation process, click OK.
Selecting components to install on multiple hosts The Select Items to be Installed screen displays the server hosts and the status information. The Select Items to be Installed screen includes the following buttons: • View Host—Enables you to view additional information about a host after you select it. • Install—Installs all selected components on all remote hosts. The Install button is grayed out when a dependency failure occurs. • Exit—Exits HP SUM.
Icon Text Description 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. NOTE: The default reboot behavior after updates are installed might also appear in the Status column.
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 then click View Host. Proceed as described in "Viewing the installation results (on page 39).
Scripted deployment Command line interface The HP Smart Update Manager command line interface enables you to script custom installations.
Command-line argument Description Help /h[elp] or /? This argument displays command line Help information. Installation Options /f[orce] /f[orce]:bundle This argument enables you to override or downgrade an existing component installation. This argument produces the same results as /f:software. This argument enables you to override or downgrade the existing installation of components in the selected bundle. /f[orce]:rom (Applies to firmware only.
Command-line argument Description /allow_update_to_bu ndle This argument is a filter switch and enables the user 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.
Command-line argument Description /use_latest This argument is a filter switch for use with bundles. The argument enables you to use the latest version of the bundle 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 enables HP SUM to use the bundle with the latest version for installation.
Command-line argument Description 15 and 3600. /reboot_always • 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, then this argument forces the server to reboot: The /reboot_always option is selected or given as a commandline argument.
Command-line argument Description components in the repository affect the target (For example, whether each component applies to the target or not). The report name is of the format, HPSUM_ Report__
o • • • ProLiant Support Pack for Microsoft® Windows Server™ 2003 v7.80 (BP000315.xml) Firmware: o System ROM o Smart Array controller o Hard drives o iLO Software—later version of: o HP Insight Diagnostics Online Edition for Windows Server™ 2003 (cp008097.exe) o HP System Management Homepage for Windows® (cp008257.
• hpsum /group "Management Servers" /current_credential /use_latest /allow_update_to_bundle /allow_non_bundle_components /force:all /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
Linux smart component return codes Single target servers: Error level Meaning 0 The smart component installed successfully. 1 The smart component installed successfully, but the system must be restarted. 2 The installation was not attempted because the required hardware is not present, the software is current, or there is nothing to install. 3 The smart component failed to install. For more details, see the log file.
be used to do dry runs of installations to ensure the scripts are working without deploying the firmware updates that might be needed on each target. Remove the “DRYRUN=YES” option to perform the updates. For parameters that can take list values, list separator can be commas, semicolons, or spaces. NOTE: The credentials can be left out of the file for greater security and passed on the command line to HP Smart Update Manager.
which applies to all targets in that section. If you want to use the current host's login credentials to log into one or more remote targets, you can do so by setting the variable USECURRENTCREDENTIAL to YES. Login credentials for one or more hosts can be supplied using the variables UID and PWD. If given at the beginning of a TARGETS section, both variables must be used.
Parameter Description Possible values hard drives and array controllers. REBOOTALLOWED This argument enables you to reboot if required. YES, NO REBOOTMESSAGE This argument enables you to create a message to be displayed prior to rebooting. Any string (not exceeding 256 characters) REBOOTDELAY This argument enables you to delay before rebooting. Time in seconds COMPONENTSLIST This argument enables you to limit the list of components to be updated. Component names with file extensions (.exe, .
Parameter Description Possible values run. Nothing is installed. OPTIONS This parameter can be used to 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. One or more CLI switch USESNMP This argument specifies that components, which use SNMP protocol, are available to be selected for installation. YES, NO These components are available for selection by default.
Parameter Description Possible values when a component has a failed dependency. OmitComponent, Force The default of OmitHost causes the host to be put in a failure state and no install is attempted on it. OmitComponent 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.
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. They can be any target supported by HP SUM. DRYRUN = YES SILENT = YES [TARGETS] HOST = BL465C-01 HOST = 192.168.1.2 [END] Example 2: A host DNS is passed along with the user ID and password to use for the hosts in the group.
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.48 UID=Userid PWD=password [END] [TARGETS] HOST=16.83.62.196 UID=Userid PWD=password [END] [TARGETS] HOST=16.83.61.24 UID=Userid PWD=password [END] Reports HP SUM can generate three types of reports about the specified system or repository.
Report type Description Report file information* /firmware_report This argument generates a report listing of the firmware in the specified repository. The report files generated are hpsum_Report_.html and fwreport.xml is placed in a folder named HPSUM_Firmware_Report_ Usage: hpsum /firmware_report The reports are generated as an XML and HTML file which can be viewed in a web browser. The supported browsers for viewing the report files are Microsoft® Internet Explorer 6.
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 Component configuration 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 software installed by the component. 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.
Deploying firmware and software simultaneously HP SUM utility enables you to deploy firmware and software components simultaneously. The latest firmware and software components must be located in the same directory. To deploy firmware and software components simultaneously, select the location where the firmware and software components are located in the Source Selections screen. On the Select Bundle Filter screen, select the bundle, and then select the ALLOW NON-BUNDLE PRODUCTS option.
Windows® firewall to enable HP Smart Update Manager to use SOAP calls over SSL to pass data among local and remote systems. These ports are defined in Allowing ports in HP Smart Update Manager ("Enabling ports in HP Smart Update Manager" on page 91). After the installation is completed or canceled, HP Smart Update Manager 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.
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 HP Smart Update Firmware DVD, 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 SEP 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.
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.
For a successful reboot, you must click Exit. When the message is entered using CLI, the reboot message looks corrupted since the Japanese character set is not supported in CLI. 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.
Recovering a lost HP Smart Update Manager connection HP Smart Update Firmware DVD mounted using iLO virtual media When either iLO and NIC firmware are updated, the HP SUM connection is lost and cannot install components. If an access error exists, HP SUM 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.
After you validate that you can access the admin$ share on the remote target server, HP Smart Update Manager works unless other network or hardware issues exist. • 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 79).
• 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).
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-1.4.3.1-1.src.rpm and on the Installation Results screen, it appears as hp-minx-en-kmp-default-1.4.3.1_2.6.27.19_51.x86_64.rpm.
• No bundles listed on the Select Bundle Filter screen. If you specify a bundle when starting HP SUM, then the Select Bundle Filter screen is not shown and the Select Items to be Installed screen appears with the specified bundle listed as the filter. This is expected, as a bundle was preselected.
Troubleshooting 100
If you then select the Select Bundle Filter link, then the Select Bundle Filter screen appears with no bundles available for selection. This issue occurs because HP SUM only recognizes the specified bundle and no others, even if other bundles are present in the repository. Even though this issue occurs, HP SUM is working as designed. • No bundle being used as a filter on the Select Items to be Installed screen.
If you experience the first issue and then select OK on the Select Bundle Filter screen to return to the Select Items to be Installed screen, the bundle you originally specified is no longer listed as the filter. To use your bundle as the filter, you must exit and restart HP SUM. This error will be fixed in the future release of HP SUM. If this issue occurs, from the GUI run HP SUM.
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.
• o Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. o If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website (http://www.hp.com/hps). In other locations, see the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/en/wwcontact.html).
Acronyms and abbreviations GUI graphical user interface HBA host bus adapter HP SUM HP Smart Update Manager I/O input/output iLO Integrated Lights-Out iLO 2 Integrated Lights-Out 2 NIC network interface controller OA Onboard Administrator POST Power-On Self Test PSP HP ProLiant Support Pack RBSU ROM-Based Setup Utility RDP Rapid Deployment Pack Acronyms and abbreviations 105
RILOE II Remote Insight Lights-Out Edition II SAN storage area network SAS serial attached SCSI SCSI small computer system interface SEP Symantec Endpoint Protection SOAP Simple Object Access Protocol SSH Secure Shell SSL Secure Sockets Layer VC Virtual Connect VCA Version Control Agent VCRM Version Control Repository Manager WMI Windows Management Instrumentation Acronyms and abbreviations 106
Index A adding groups 46 advanced topics 77 Allow Downgrades 37 Allow Rewrites 37 Allow Shared Devices 37 authorized reseller 103 B blocked HP Smart Update Manager, recovering from 91 bundle filter options 26, 53 C CLI (Command Line Interface) 98 command line arguments 58 command line arguments, component 58 command line examples 63 command line interface, using 58 command line syntax 58 command-line usage of input file 67 component configuration 77 component configuration, Windows 63 component selection
I non-matching system error 97 iLO (Integrated Lights-Out) 95 input file parameters 67, 68 input file, command-line age 67 installation host 25 installation issues 88, 98 installation options 37 Installation Progress 37 installation results 39 installation status 39 installation, multiple hosts 41 introduction 6 IPv6 network configurations 78 IPv6, troubleshooting 95, 96 O K keyboard support 21 L Lights-Out Management ROMs 87 limitations, Linux IPv6 environment 85 limitations, Windows Server IPv6 envir
S scenarios, deployment 20 scenarios, overview 20 scripted deployment 20, 21, 58 selecting an installation host 25 selecting bundles to filter for the first time 26 selecting components to install for the first time 28 server virtualization detection and support 78 settings, reboot 32 shared storage, updating ROMs for 37 SLES (SUSE Linux Enterprise Server) 94 software and firmware deployment, simultaneous 78 support 103 SUSE Linux Enterprise Server (SLES) 94 syntax 58 system status field 31 T technical sup