HP Smart Update Firmware DVD User Guide Abstract This guide is intended for individuals who are familiar with the configuration and operation of Microsoft Windows operating systems, smart components, and the deployment of firmware and software to systems and options. Because of the risk of data loss, only individuals experienced with using firmware and software should implement the procedures in this guide.
© Copyright 2007, 2012 Hewlett-Packard Development Company, L.P. Notices 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 1 Introduction...............................................................................................5 HP Smart Update Firmware DVD overview...................................................................................5 Supported firmware..................................................................................................................5 Obtaining the Smart Update Firmware DVD.................................................................................
Recovering from an installation failure.......................................................................................28 Collecting trace directories..................................................................................................28 Recovering from a discovery failure...........................................................................................30 Troubleshooting connection errors........................................................................................
1 Introduction HP Smart Update Firmware DVD overview IMPORTANT: The HP Smart Update Firmware DVD is not shipped with ProLiant Gen8 servers and will be discontinued. Smart Update Firmware DVD 10.10 is the last version. Instead, use HP SPP. SPP is a comprehensive systems software and firmware solution delivered as a single ISO used to update HP ProLiant and BladeSystem servers and enclosures. You can download SPP from the HP website at www.hp.com/go/spp/download.
Firmware type Supported by Smart Update Firmware DVD iLO 4 firmware Yes, local and remote Lights-Out 100 firmware Yes, online with Linux, and Windows 2008, but not Windows 2003.
Support limitations • Booting the Smart Update Firmware DVD from iLO virtual media is only supported in the offline Automatic Firmware Update mode. Users attempting to boot in this manner, might experience issues from connection timeouts, difficulties updating iLO firmware, and mouse syncing issues. • Workstation blades are only supported for offline firmware updates. • Virtual OS is not supported for online firmware updating but is supported for offline firmware updates.
2 Smart Update Firmware DVD contents Release sets and bundles A release set is an enhanced, solutions-oriented collection of ProLiant BladeSystem firmware released on a regular basis. The full collection is tested against HP software, drivers, and PSPs to drive standardization of components to HP customers. The release set can only be applied in interactive mode and by selecting the blade system bundle. HP recommends that you not deviate from the release set firmware contents.
• Simultaneous firmware and software deployment • Improved deployment performance • Local or remote (one-to-many) online deployment • Local offline deployments with the HP Smart Update Firmware DVD • Remote offline deployment when used with the Scripting Toolkit, the iLO 2 Virtual Media applet, or the iLO 3 and iLO 4 Integrated Remote Console • GUI or CLI/scriptable with extensive logging • Remote command-line deployment Smart Update Firmware DVD powered by HP SUM 9
3 Deployment options Host types You can run the Smart Update Firmware DVD either online or offline. When performing an online deployment, you must boot the server from the operating system that is already installed and running.
Deploying components online 1. Choose one of the following options: • Insert the Smart Update Firmware DVD. The Smart Update Firmware DVD interface opens. • Insert the USB drive key. Manually start the interface, and open a CLI.
2. Select the HP USB Key Utility shortcut in the HP System Tools folder. Follow the onscreen instructions. The HP USB Key Creator formats the USB key. Therefore, files on the key are deleted. Ensure that you are using a USB key that is at least 2 Gb in size, and does not contain valuable files. Existing data on the key is deleted. For Linux, the USB key can be created manually: 1. Obtain SYSLINUX 3.xx RPM from the Syslinux Project website at http://syslinux.zytor.
12. Remove the USB key and DVD. NOTE: To remove a DVD image from your USB drive key, delete the subfolder containing the CD image, and edit the syslinux.cfg file at the root of the USB drive key, deleting the section referencing that subfolder name. Using a hard drive to deploy the components 1. 2. 3. 4. Copy the contents of the \hp\swpackages directory from the DVD or ISO image to a directory on the hard drive where HP SUM will be executed.
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.
Scenario Result switch is not given, and any firmware updated must be applied to the server. Because the installation is silent, the installation is terminated and cannot continue. If TPM is detected and enabled, the installation is silent, The installation occurs. and the /tpmbypass switch is supplied. The installation occurs. Booting a Smart Update Firmware DVD over a network Prerequisites The following is required before proceeding with the configuration: • Knowledge of PXE and TFTP.
2. 3. Replace the lines kernel hpvoot_v.c32 with kernel vmlinuz. Remove vmlinuz from the append line. NOTE: The paths to files on the TFTP server are vmlinuz and initrd.img. You must modify them to include any directories or naming conventions you may have on your TFTP server. Specifying the ISO Image Path For the PXE booted server to find the ISO Image, you must add the ISO Image path to the append line in the PXELINUX configuration file. Add the following arguments: iso1=nfs://192.168.0.
Windows operating systems with login credentials: iso1=smbfs://user:password@192.168.0.99/share/path/to/fwdvd/image/FW910.iso iso1mnt=/mnt/bootdevice Deploying firmware and software simultaneously HP SUM 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.
4 Smart Update Firmware DVD Automatic Deployment Mode Overview HP Smart Update DVD, in conjunction with Release Sets, provide a collection of firmware smart components that have been tested together in complex industry-like scenarios to ensure compatibility across varying firmware and software stacks. The tool is designed for users who do not have an installed operating system on their blades or who want an unattended, automated method of deploying firmware in an offline environment.
Updating an individual server locally To update an individual server using Automatic Mode, use the c-Class SUV cable. This cable connects to the front of a blade and enables a USB CD or DVD drive to connect to a server. In this local installation, the Automatic Mode ISO image must be burned to a physical CD and placed in the USB CD or DVD drive. After you place the physical CD in the USB CD or DVD drive, you can boot the server, and Automatic Mode flashes all firmware on the server.
reboots to Automatic mode, and restarts the firmware update process. If you need to update more than eight servers in an enclosure, you must execute multiple batches to complete the process. You can use Automatic mode to update firmware for multiple servers at once within an enclosure by using the USB port on the OA to host the Automatic mode ISO image through the iLO Virtual Media (or the IRC) interface to multiple servers.
5. Install the following: • • For Windows operating systems: ◦ iLO Advanced Pack license ◦ OpenSSH, which you can download from the OpenSSH for Windows website at http://sourceforge.net/project/showfiles.php?group_id=103886& package_id=111688. Any SSH alternative can be used. ◦ The HP Lights-Out Configuration Utility (cpqlocfg.exe), which you can download from the HP Software and Transitions website.
echo " BB1.sh " } if [ "$4" = "" ] then usage exit fi host=$1 user=$2 passwd=$3 script=$4 hostfile="hostlist.txt" # If you want to use a pre-made/modified list, just comment out the if statement # and the "show server list" line as well.
Determining the success of an Automatic Mode deployment When you boot to Automatic Mode, the UID light provides all feedback. UID light status Meaning Blinking Either a remote console is active, or the Automatic Mode is flashing firmware. Off The firmware update was successful. On At least one of the needed firmware updates failed. The remote console to the server searches for the cause of the error.
5 Advanced topics Server virtualization detection and support HP SUM supports server virtualization that runs on a Windows host. However, HP SUM does not run on a VMware host or on a guest operating system environment regardless of what host hypervisor you use. HP SUM does not support server virtualization that runs on a Windows or Linux host and blocks attempts to install firmware from a guest or child virtual machine.
4. Add the following registry value: Value name: DisableStrictNameChecking Data type: REG_DWORD Radix: Decimal Value: 1 5. Close the Registry Editor. For more information about these steps, see the Microsoft Knowledge Base Item 281308 on the Microsoft website. IPv6 addresses can be passed to HP SUM in command line arguments or using the HP SUM user interface.
IPv6 addresses can be passed to HP SUM in command line arguments or using the HP SUM user interface. In the HP SUM user interface, HP SUM automatically detects whether to use IPv4 or IPv6 on the Add Target screen. On the Find Targets screen if you choose to select to IP address range, select IPv4 or IPv6. HP SUM supports both the short-name and full IPv6 notation. You do not need to add the optional interface number when you enter the address.
6 Troubleshooting 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. This feature protects the existing ROM version, even if you experience a power failure while flashing the ROM.
Array controller ROMs Array controllers support Recovery ROM, which is a redundancy feature that ensures continuous system availability by providing a backup ROM. During the flash process, a new version of the firmware can be flashed to the ROM while the controller maintains the last known version of the firmware. If the firmware becomes corrupt, the controller reverts back to the redundant version of the firmware and continues operating.
Trace files Function \Settings.xml Provides general settings information of HP SUM such as Force downgrade or upgrade for a specific target. SourceClient.trace Provides trace data of repository manager and general errors if any. Hpsumiserver\ Hpsumiserver.log This log contains trace data for HP SUM SOAP server sessions. Hpsumiserver\ HpsumserverW32.log This log contains trace data for HP SUM SOAP server sessions. Hpsumiserver\ localhpsumsoapserver.
InstallSet.cpp[212]: InstallSet.cpp[222]: InstallSet.cpp[222]: InstallSet.cpp[222]: InstallSet.cpp[222]: InstallSet.cpp[242]: Winnow--Adding FileName cp011500.exe Winnow--Removing FileName cp011504.exe Winnow--Removing FileName cp011505.exe Winnow--Removing FileName cp011550.exe Winnow--Removing FileName cp011560.exe Target 0: Added Bundle bp000648.
Recovering from a loss of Linux remote functionality by configuring firewall settings When the Unable to Access Host message appears, the target firewall is enabled. By default, the target firewall is enabled in Linux. To recover remote Linux functionality, the target and host firewall must be disabled or reconfigured to allow IP traffic through the ports needed by HP SUM to deploy firmware. For a list of the ports that need to be configured in the firewall, see “Enabling ports in HP SUM” (page 33).
The SOAP server that HP SUM launches uses ports 443 or 63006. You can define your own ports by modifying the hpsum.ini file. 1. Open hpsum.ini in a text editor. You can find the file in the same folder as the HP SUM application. 2. Look for the following lines: Port=443 AlternatePort=63006 3. Change the AlternatePort to a port free of another web service. NOTE: HP does not recommend changing the main port from port 443.
Enabling ports in HP SUM The ports that HP SUM uses cannot be configured by the end user. When HP SUM port initiates communications to remote targets, it uses several well-known ports depending on the operating system. For Windows, it uses ports 138 and 445 to connect to remote targets (equivalent to remote and file print share functionality). For Linux, HP SUM uses port 22 (SSH) to start the communications with the remote target.
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 can 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 SUM in IPv6 Windows Server 2003 environment To validate that the IPv6 network is configured correctly for HP SUM support, you must verify the following based on your operating system version. • Validate that the addresses are site-local. Site-local addresses normally start with "FEC0:". Global and link-local IPv6 addresses are not supported when the remote target is Windows Server 2003. • Validate that you can ping the remote target server.
Troubleshooting HP SUM in IPv6 Red Hat and Novell SUSE-based Linux environments • Verify that you can establish an SSH connection to the remote target server using the credentials within HP SUM by issuing the following command at a console prompt: ssh SSh 2101:db8:0:1::9 You must enter the root password for the target Linux server at the console to complete the IPv6 connection. • Validate that you can ping the remote target server.
Linux component version discrepancy for source RPMs You might observe differences in the RPM component name which might appear to be a version mismatch for the component on the Select Item to be Installed screen and the Installation Results screen. This is caused by the RPM build phase. The resulting component is actually the same version. The RPM build adds information, so it is technically the same component.
5. 6. 7. 8. 9. From the menu, select TaskUnlock Interface. Enter the password of the McAfee user interface. Select the Firewall Policy tab. On the bottom of the screen, click Add (Add new rule). 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. Virtual Connect firmware upgrade using HP SUM fails if VC reports an invalid or bad health state Virtual Connect firmware can be upgraded using HP SUM only if the health state of the VC is in a good state. If the health state is invalid or bad, HP SUM does not upgrade the VC firmware.
To resolve these issues, you must use the VCSU to upgrade the firmware. Performing a Health check HP SUM 5.0 can deploy VC firmware, however, it is necessary to perform a health check before updating with HP SUM. NOTE: Use VCSU instead of HP SUM in the following cases: • Updating enclosures that are not part of a domain • Unhealthy VC domains • If you need to specify activation order 1. 2. Download VCSU. Run VCSU with the "healthcheck" parameter.
7 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP Use the following methods to contact HP technical support: • See the Contact HP worldwide website: http://www.hp.
• For information about support for updating SATA hard drives in a Modular Smart Array storage enclosure connected to a ProLiant server using a Smart Array controller, see the HP StorageWorks Modular Smart Arrays website for the support matrix at http://www.hp.com/ go/msa. • For information about operating systems supported by ProLiant servers, see the ProLiant support matrix at http://www.hp.com/go/foundation.
sent to your authorized HP Channel Partner for on-site service, if configured and available in your country. The software is available in two variants: • HP Insight Remote Support Standard: This software supports server and storage devices and is optimized for environments with 1–50 servers. Ideal for customers who can benefit from proactive notification but do not need proactive service delivery and integration with a management platform.
8 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Acronyms and abbreviations HBA host bus adapter HDD hard drive HP SUM HP Smart Update Manager I/O input/output iLO HP Integrated Lights-Out LO100 HP Lights-Out 100 NIC network interface controller POST Power-On Self Test PSP HP ProLiant Support Pack RBSU HP ROM-Based Setup Utility RIBCL Remote Insight Board Command Language RILOE II HP Remote Insight Lights-Out Edition II SAN storage area network SAS serial attached SCSI SCSI small computer system interface SEP Semantic Endpoi
Index Symbols 100 series servers, 7 A advanced topics, 24 audience assumptions HP Smart Update Firmware DVD overview, 5 Overview, 18 B BladeSystem firmware, 5 blocked HP Smart Update Manager, recovering from, 31 booting over a network, 15 C configuring firewall settings Configuring firewall settings, 31 Configuring Windows firewall settings, 31 contacting HP, 41 conventions document, 42 text symbols, 42 D deploying components, 13 deploying firmware and software simultaneously, 17 deployment, offline, 11
recovering from a failed system ROM upgrade, 27 Recovering from an installation failure, 28 redundant ROM, 27 related documentation, 41 release sets and bundles, 8 remote functionality, recovering, 31 ROM recovery, redundant, 27 ROM recovery, server not booting from redundant ROM, 27 ROM redundancy, 27 ROM redundancy, server not booting, 27 ROM upgrade, recovering from failed option, 27 ROM upgrade, recovering from failed system, 27 ROM, array controller, 28 ROM, Lights-Out management, 28 ROM, storage, 28