TITLE: HP Smart Update Firmware - HP Integrity BL860c/BL870c/BL890c i2 Servers Bundle for Windows
VERSION:
HP Smart Update Windows Firmware Bundle
Bundle Version : 2011.05
System Firmware Version : 1.72
FGPA Firmware Version : 2.00
iLO-3 Firmware Version : 01.40.42
Power Monitor Firmware Version: 03.04
Onboard Administrator (OA)
OA Firmware Version : 3.30
HP Smart Update Manager (HP SUM)
HP SUM Version : 4.9.5
Note: All blade firmware components should be updated in the same HPSUM update session.
DESCRIPTION:
This bundle contains the HP Smart Update Manager (HP SUM) Windows x86 application, the firmware for HP Integrity BL860c/BL870c/BL890c i2 Servers (System firmware (SFW), FPGA firmware, iLO-3 MP firmware & Power Monitor firmware) and the Onboard Administrator (OA) firmware. This bundle can be used to update the firmware using the HP SUM application from a Windows x86 system.
Note: Any update to the information below will be available on the release notes for HP Smart Update Windows Firmware Bundle for HP Integrity BL860c/BL870c/BL890c i2 Servers, available on www.hp.com
For more information on HP SUM, review the HP Smart Update Manager User Guide which is available on hp.com at:
More information about firmware update methods can be obtained from the following document
UPDATE RECOMMENDATION: Critical
This update is CRITICAL for HP Integrity BL870c i2 and BL890c i2 Blade Servers in a Virtual Connect environment.
This update is NOT considered critical for the following configurations:
- systems with HP Integrity BL860c i2 blade servers only
- systems that do not use Virtual Connect
- NonStop systems
For these systems, the update is Recommended or Optional, depending on their exposure to the fixes listed below.
[X] Critical (see important notes below for usage restriction)
[ ] Panic, [ ] Hang, [ ] Abort,
[ ] Corruption, [ ] Memory Leak,
[X] Other: Risk to mission critical environments Security
[ ] Hardware Enablement, [ ] Software Enablement
[ ] Recommended
[ ] Optional
[ ] Hardware Enablement, [ ] Software Enablement, [ ] non-critical
[ ] Initial Customer Release
Important:
The update to Onboard Administrator version 3.30 is required to resolve a critical issue where HP Integrity BL870 i2 and BL890 i2 Blade Servers experience a Virtual Connect network outage shortly after performing a reset of the Server Blade's MP/iLO. This outage will affect all Virtual Connect LAN and SAN connections on the specific blade in which the MP/iLO was reset. The outage time can vary from 30 seconds to 2 minutes depending on system and enclosure configurations and will cause loss of communication between systems in clustered environments such as with Service Guard and OpenVMS.
Note: The update to OA firmware should NOT be performed in a production environment as there is a risk that an OA reset may cause a similar outage in the HP BL870c i2 and BL890c i2 blades in the enclosure.
SUPERSEDES:
HP Smart Update Windows Firmware Bundle
Bundle Version : 21.08
System Firmware Version : 1.24
FGPA Firmware Version : 1.14
iLO-3 Firmware Version : 01.30.30
Power Monitor Firmware Version: 03.04
Onboard Administrator (OA)
OA Firmware Version : 3.21
HP Smart Update Manager (HP SUM)
HP SUM Version : 3.7.1
PRODUCT MODEL(S):
HP Integrity BL860c i2 Server
HP Integrity BL870c i2 Server
HP Integrity BL890c i2 Server
OPERATING SYSTEMS:
HP-UX 11i v3 OE Update Release for March 2010 (and later OE Releases)
Microsoft Windows server 2008 R2
Open VMS 8.4
NonStop Operating System
NOTE: HP Smart Update Manager (HP SUM) for Windows is supported on following Windows Operating Systems:
- Microsoft Windows Server 2008 R2
- Microsoft Windows Server 2008 R2 Foundation Edition
- Microsoft Windows Server 2008 x64 - All Editions
- Microsoft Windows Server 2008 x64 - Server Edition
- Microsoft Windows Server 2008 x64 - Server Core Edition
- Microsoft Windows Server 2008 Essential Business
- Microsoft Windows Server 2008 Foundation Edition
- Microsoft Windows Server 2008 Small Business
- Microsoft Windows Server 2008 W32 - All Editions
- Microsoft Windows Server 2008 W32 - Server Edition
- Microsoft Windows Server 2008 W32 - Server Core Edition
- Microsoft Windows Server 2003 x64 Edition (Including R2 & Base Edition)
- Microsoft Windows Server 2003 - All Editions (Including R2 & Base Edition)
- Microsoft Windows XP Professional
LANGUAGES:
International English
ENHANCEMENTS:
- Support for power management from iLO and OS including Advanced Power Capping and Power Regulation
SFW
- Added migration support for VC profile boot option
- Added boot options for VC primary/secondary boot targets that don't already have one
- System now generates event for USB over-current condition at EFI
- Improved the analysis of MCA logs in case of uncorrectable errors by extending data reporting
- Improved internal tracking of correctable memory errors count on x8 DRAMs
iLO
- Viewing the forward progress log is now supported in the iLO GUI
- Support for BladeSystem Matrix is now enabled with HP BL860c i2, BL870c i2, and BL890c i2 blades
- Improved the processing time to load the system health page in the iLO GUI, in particular on HP BL870c i2 and BL890c i2 blades
- Availability and usability have been enhanced.
FIXES:
The following issues have now been resolved:
SFW
- EFI shell extended characters were forced to an off state when entering the boot manager and restored to their previous state when returning to the shell
- The level 5 IODISC_RP_LINK_TRAIN_ERR event could be erroneously displayed and cause HP-UX to fail to discover the IPMI device
- Certain events were not sent while in virtual mode during system OS shutdown
- A failed DIMM would no longer show as de-allocated after reboot
- The SM BUS speed was set too high during an MCA, potentially leading to nested MCAs
- Corrected memory interleaving problem causing MCA in HP BL860c i2 blades with 8x16GB and 4x4GB DIMMs
iLO
- An invalid blade slot number was displayed in the system event log generated when DIMM quads were being de-allocated.
- A rare issue occurred in which disconnecting Web SSL users from the Web interface on the "Active Users" tab of the "Status Summary Page" could disallow subsequent web connections. This could be remedied by resetting iLO from the TUI(Terminal User Interface) .
- The iLO reset command could be performed from the CLI(Command Line Interface) (xd –r) or the GUI while a FW update was in progress.
- During a FW upgrade, an iLO reset from the iLO GUI was reported to be successful at resetting the iLO although the reset was not successful
- Repeated power on, hard power off cycles from OA CLI(Command Line Interface) could create a failure to power off
- The iLO command prompt could hang from invalid or missing parameters. This could be remedied by resetting from iLO GUI or using SSH exec "xd -r"
- Under very particular conditions, a conjoined system could display one or more of the following symptoms:
- Fail to gracefully shutdown
- CPU temperatures may go unmonitored
- BLADE_FAILED_BOOT may be logged in the SEL despite a normal boot
- iLO health monitoring may inappropriately represent the LEDs in the Virtual Front Panel and iLO GUI
- iLO GUI "system health" page may not load completely on a fully loaded system.
- Issues occurred with command line LDAP usage
- A mismatched CPU on one blade of a HP BL870c i2 or BL890c i2 blade could display as a mismatched CPU on each successive blade in the system
- A dropped LAN connection during firmware update could cause a firmware update command or HP SUM command to cease operation. iLO now detects the dropped connection, and reports the error.
- HP SUM failed to successfully update HP BL870c i2 and BL890c i2 blades with mixed Firmware versions.
- iLO TUI(Terminal User Interface) PR command and "power & reset" GUI page would fail if firmware upgrade was in process.
OA
- General
- Utility Ready Blade feature would be inactive after restarting the OA if URB ENABLED command is set to anything other than HTTP.
- Onboard Administrator could reboot if an invalid character was logged to a remote syslog.
- Onboard Administrator terminated following many back-to-back blade power on/off cycles.
- Onboard Administrator would report spurious blade "power release" messages when a blade e-fuse was reset.
- OA incorrectly reported SAS Storage Mezzanine ports connected to Ethernet devices as port mismatches. This condition is not an error as the SAS Mezzanine ports are dynamically enabled / disabled.
- Onboard Administrator occasionally did not clear all state information after a blade was removed.
- An error message ,'NVRAM unformatted/corrupted', was falsely displayed when downgrading from an OA 3.xx version to an OA 2.xx version.
- OA was not initializing interconnect power states at initial OA startup.
- OA improperly initialized identification strings for ServerNet type switches to OA CLI.
- Interconnect modules and server blades may not receive an EBIPA IP address but may receive an IP from an external DHCP server after an OA restart when OA VLAN is enabled.
- OA would reboot when executing a "SHOW SERVER BOOT" CLI command on server blade that has more than 8 IPL Boot Order devices.
- Upgraded from OpenSSH 5.1p1 to OpenSSH-5.6p1.
- Integrity Blades
- OA would display the CPU max core frequency instead of the core base frequency for HP Integrity BL8x0c i2 server blades.
- Rebooting the OA in an enclosure with only one power rail powered-up could cause HP Integrity BL8x0c i2 server blades to go into a low power performance state.
- HP Integrity BL8x0c i2 server blades would remain in low power mode after AC redundant power loss and OA restart.
- KVM
- OA-KVM feature appears to hang with the message "Header Received" when connecting to a HP ProLiant G7 blade with ILO3.
- IPv6
- An error message, "cannot create tmp-.conf", would be displayed if an operator attempted to change IPv6 settings.
- An IPv4 connection would be lost after modifying IPv6 settings.
- LCD
- Someone logged in with "Operator" privileges could set LCD Pin Protection Number through the OA browser.
- The LCD Health Summary continued to report "missing server" on a full-height blade with an adjacent storage blade installed in an incorrect bay - after the storage blade had been removed.
- Virtual Connect (VC)
- HP BL870 i2 and BL890 i2 Blades would experience a Virtual Connect network outage shortly after performing a reset of the Server Blade's MP/iLO. This would affect all Virtual Connect LAN and SAN connections on the specific blade in which the MP/iLO was reset. The outage time could vary from 30 seconds to 2 minutes depending on system and enclosure configurations and would cause loss of communication between systems in clustered environments such as with Service Guard and OpenVMS.
OA would improperly report a VC Interconnect module’s status if the modules E-fuse were tripped.
- VC 24-Port FC Interconnect Firmware Version information sometimes didn't appear in Onboard Administrator GUI or CLI output.
PREREQUISITES:
- OA firmware for HP Bladesystem c3000/c7000 enclosures with HP BL8x0c i2 blades: minimum OA version required is 3.11 or 3.21 to support HP BL8x0c i2 blade upgrades. However version 3.30, which is included in the bundle, is the recommended version.
- VC firmware: minimum VC version required is 3.15. However VC version 3.17 or later is recommended.
Note: VCSU 1.5.0 or later is required to install the VC firmware update. This utility is not included in this bundle but is available from the HP Support & Drivers web site.
- OA and iLO3 MP(s) must be on the network (reachable from local system) and have static IP or be configured with DHCP.
- An http daemon, service or IDS (Intrusion Detection System) running in the local system may interfere with HP SUM connecting to remote hosts, hence these services may need to be disabled when HP SUM is running.
- Please see the HP Smart Update Manager User Guide for any prerequisites required for HPSUM.
For latest dependencies on OA and VC, refer to this matrix:
www.hp.com
INSTALLATION INSTRUCTIONS:
Please review all instructions and the "Hewlett-Packard Support Tool License Terms" or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and limitation of liability and warranties, before installing this package. It is important that you read and understand these instructions completely before you begin. This can determine your success in completing the firmware update.
NOTE: Should you have McAfee firewall installed, refer "KNOWN INSTALLATION ISSUES" mentioned below in this Release Note.
A. Extracting and Running HPSUM
- Download the binary "bl8x0ci2_fw_bndl_win.exe" to a new folder on your Windows system.
- Double click the file, bl8x0ci2_fw_bndl_win.exe, to run it.
- Click the "Extract" button.
- When asked, browse and select or create a new folder to extract bundle contents. HPSUM and firmware components must reside in the same folder. After extraction completes click "OK" and then "Close" button.
- Execute "hpsum.exe" as Administrator (with superuser privilege). Executing hpsum.exe will bring up a graphical user interface of the HP Smart Update Manager (HPSUM). HPSUM provides an easy-to-use graphical interface that enables you to deploy and maintain firmware components.
NOTE: HPSUM 4.9.5 requires a workaround to run in Japanese. Please see ‘Workaround for running HPSUM 4.9.5 in Japanese’ instructions below.
NOTE: HPSUM also provides a Command Line Interface (CLI) that allows user to perform scripted installations in silent mode. For more information please refer to the HPSUM User Guide or the "CLIHelp.txt" file in the extracted folder.
B. Installing the Firmware Components using HPSUM - Graphical User Mode
- Once started, a page displays with HPSUM introduction content on it. The introduction describes HPSUM, its usage, enhancements (if any), and EVA bundle information.
- Choose - Define Repositories that you want to be considered for updating
- The Source Selections screen allows you to choose directories where smart components are located. The directory to which the bundle is extracted is the default location.
- You can optionally have HPSUM check www.hp.com for additional metadata needed for the utility to discover devices.
- HPSUM will build an inventory of firmware bundles - packages that can be used to update firmware.
- The Inventory Progress screen displays while HPSUM builds an inventory of available updates.
- Click the "Next" button to move on to the next step.
- Define - Select Targets: i.e., servers you want to update
- The "Select Targets" screen enables you to choose one or more targets for component installation.
NOTE: "Local Host" is not applicable for installing the firmware updates included in this bundle.
- The target for installation can be managed in two ways:
- Manage individual target by selecting "Add Single Target"
- Manage a collection of Targets as a group by selecting "Manage Groups". Each group can contain one or more targets.
Managing Target Individually
Click "Add New Target". Fill in this page by providing the following details of the target:
- Enter the DNS name or IP address of the target.
- Choose the Target type from the drop down.
- Enter the description of the target entry to identify the host for future use.
- Finally, provide the user name and password of the selected target. HPSUM will try to connect to the remote host and validate the login credentials.
Managing a Collection of Targets as a Group
- To manage any group, first the individual targets should be added. For that, follow the instructions of "Managing Target Individually".
- Once the targets are added, click "Manage groups".
- Enter a name for the Group and the description.
- Select the available targets to add it in the group.
- To update OA firmware, enter the OA IP address or DNS name. Do not enter the Blade IP address.
- HPSUM contacts the host to validate the credential details one at a time for each host.
- HPSUM runs a discovery routine that determines which Firmware Components are already installed on the remote host.
- Select what you want to install.
- HPSUM displays firmware item to be installed on the hosts.
- For more details and component level granularity, select the item and click the "Select Components" link.
IMPORTANT: Both iLO and SFW components must be installed together as a pair on the system.
NOTE: If firmware is latest or already up-to-date version, HPSUM displays the message "Nothing-to-Install". You can override and choose to perform force reinstallation or downgrade the firmware by clicking the "Installation Option" and checking “Force Install” option.
NOTE: System Firmware update supports delayed activation - where the new firmware gets downloaded to the iLO but is programmed only when you power down the system at a convenient time. Delayed activation is the default setting for SFW update. This setting can be changed by doing the following actions:
- Click "Configure Now"
- Select the "Upload and Activate" checkbox.
If "Upload and Activate" is selected, HPSUM will do the following actions:
- Send a graceful shutdown and power off request to the system as part of the update
- Then power up the system after the System Firmware has been programmed.
If you choose to do the power off manually, the programming will take approximately 8 minutes to complete the programming operation before power can be turned on again.
- Repeat the above 2 steps for all targets listed, until HPSUM displays "Ready" against each listed items to be installed.
- Launch the update - Install
- Proceed with installation of the selected firmware on the selected hosts by clicking the "Install" button on the bottom-right corner of the screen.
- HPSUM displays the progress of the firmware update on the target.
- Do not interrupt HPSUM until it completes the firmware installations on all remote hosts.
- When the update completes, HPSUM displays success message (or failure message in case of firmware update failure) for each host.
- HPSUM Debug Logs are located in "\tmp\hp_sum" folder on the local system.
Workaround for running HPSUM 4.9.5 in Japanese:
When running HPSUM on Windows:
- Create a new text file using Notepad, or other text editor
- Enter (or cut and paste) the following lines
@Echo off
:: HPSUM workaround for Japanese support
echo REBOOTALLOWED = YES > patch_ja.txt
hpsum.exe -inputfile=patch_ja.txt %*
del patch_ja.txt
- Save the file as hpsum_ja.cmd in the same directory where hpsum.exe exists
- Start HPSUM by double clicking hpsum_ja.cmd
Continue to use this command file whenever running HPSUM (i.e., there is no need to redo steps 1-3 if this command file exists)
C. Using HPSUM Command Line Interface (CLI) Mode
Please refer to the HPSUM User Guide or the "CLIHelp.txt" file in the extracted folder.
HPSUM User Guides will be available in the following URLs shortly:
COMPATIBILITY/INTEROPERABILITY:
- WARNING: Do not disconnect power supply to HP Integrity Server during the firmware upgrade process or else the ROM will be corrupted.
DETERMINING CURRENT VERSION:
HP SUM displays the current version of the firmware on the host. However user can also
log in to the iLO-3 MP and use the following procedure to find out the current firmware versions.
- Establish a telnet session with the iLO-3 MP.
- Logon to the iLO-3 MP using the Administrator password.
- Type "CM" to enter the Command Menu.
- Type "SYSREV" to display system revision information.
The following should be displayed if the current firmware is installed.
SYSREV
Revisions Active Pending
-------------------------------------
iLO FW : 01.40.42
System FW : 1.72
MHW FPGA : 01.14
Power Mon FW : 03.04
Front Panel HW : 02.00
PRS HW : 02.06
IOH HW : 01.02
To determine the currently installed OA version, please refer to the instruction in OA user guides:
- The user guide for the Onboard Administrator is located here.
- The user guide for the Onboard Administrator command line interface is located here.
KNOWN FIRMWARE ISSUES:
iLO
- If a system is reset while there is a pending system firmware update, it will cease to function. The system power should be cycled.
- Secondary group LDAP users may fail to login.
- iLO GUI, System Health screen has a limit of 25 Temperature Sensors. Some temperatures sensors will not be visible, though they will be monitored and acted upon by firmware.
SFW
- System may MCA during boot if the memory configuration is invalid. This may happen for instance in case some DIMMs are mis-loaded or de-allocated due to errors.
Other
- OA reset performed in a production environment may cause loss of communication between systems in clustered environments such as with Service Guard and OpenVMS, resulting in potential outages for the HP BL870c i2 and BL890c i2 blades in the enclosure. Note that an OA update will cause an OA reset to be performed.
KNOWN INSTALLATION ISSUES:
- An attempt to run HPSUM 4.9.5 on a system set for Japanese language will immediately abort. See installation instructions under ‘Workaround for running HPSUM 4.9.5 in Japanese’ for details on using HPSUM in Japanese language mode.
- Passwords for Blade iLO and Onboard Administrators must not contain "-" or "=", otherwise HPSUM 4.9.5 will fail to log in. The password must be changed before running HPSUM in order for the update to work.
- If you receive the message "Could not add the following requested repositories:" after selecting a directory to use with HPSUM, the HPSUM temporary directory %temp%/hp_sum must be deleted.
- Delete the folder %temp% /tmp/hp_sum
- Restart HPSUM
- When using HPSUM CLI mode with InputFile, both OA and blade systems should be updated at separate times. When run in the same session, blade System Firmware will not be updated.
- When using HPSUM CLI mode, "/s" must be one of the parameters, otherwise HPSUM will stop after target discovery phase.
- If you receive the message "Connected to unknown SOAP server" while connecting to targets, please exit HPSUM and log out and log back in to clear any background processes that may be blocking HPSUM.
DISCLAIMER:
The information in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be reproduced, photocopied, or translated to another language without the prior written consent of Hewlett-Packard Company.
(C) Copyright 1994-2011 Hewlett-Packard Development Company, L.P.
SUPERSEDES HISTORY:
Bundle Version : 21.08
ENHANCEMENTS:
- Memory Patrol scrubber
- 16 GB DIMM support
- EFI boot options for directed LAN boot
- Multiple connections to the live event viewer are now allowed
FIXES:
- Fixed an issue where the “String buffer too small” error message could be displayed during a network installation of the blade, eventually leading to a system panic.
- Fixed an issue where the MCA errdump log file might not have included MCA information for all the blades.
- Improved boot stability by fixing several potential occurrences of MCAs during boot.
- Health state does not return to 'OK' when temperature goes from Critical to OK. In order to clear this error a system power cycle was required.
- iLO/Integrity blade information is now shown correctly in OA.
- Fixed an issue where some blades would not power on and generate a POWERON_DENIED_BUSY_ERROR message upon enclosure power on.
- Fixed an issue in which the DIMM Slot location for DIMM errors was being reported as decimal numbers when it should have been reported as hexadecimal numbers.
- An issue in which the iLO Web GUI 'System Health Page' could inaccurately display a Mezzanine card as 'not installed' has been fixed.
- An issue in which LDAP did not expect the format user@domain.com has been fixed in the iLO web GUI. The problem still exists in the iLO CLI. The work around is to configure the LDAP server to use an alternative format.
- An issue in which rapid execution of multiple power commands could cause CM menu to become unresponsive has been fixed. A reset from the GUI could clear this condition.
- A rare issue in which an internal file system could crash causing defaulting of iLO user configuration data, or potential iLO unresponsiveness has been fixed.
- The System Health Page in the iLO Web GUI now displays temperatures appropriately.
- An issue in which vMedia connections could experience failures has been resolved.
- Thermal and fan control behavior has been fixed.
- The DC command now sets Asset Tag to default values properly.
- An issue with an unexpected close of network sessions has been addressed.
- An issue in which the VMEDIA connections event was logged without an IP address has been fixed.
- IP address is now logged appropriately in the IEL event for VMEDIA connections.
- Fixed an issue in which the factory default password could have been set to Admin.
- Multiple connections to the live event viewer are now allowed.
- An issue with highlighting the wrong tab in the system health page on BL870c and BL890c systems has been fixed.
- An issue with the rare loss of an EFI configuration change has been addressed.
- An issue where fatal events (i.e. non-recoverable temperatures) may not shut down the system has been fixed.
- Fixed an issue where the system was failing to boot due to temperatures being misread and fans speeding up incorrectly while CPUs were still resetting.
- Fixed an issue where fan speed would not increase after the FAN_BLOWOUT_ENTER event was logged.
- Empty DIMM slots are now properly reported in SMBIOS.
- Fixed an issue where a DVD drive may be intermittently missing.
- BIOS release date has been included in SMBIOS.
- Memory test is now properly disabled with boottest mem off.
- vMedia performance and reliability has been improved.
- Debugging information for Traps/Interrupts has been improved.
- Error handling/containment/logging has been improved.
- Improved help text output for EFI commands.
INITIAL RELEASE:
HP Smart Update Windows Firmware Bundle
Bundle Version : 15.04
System Firmware Version : 01.07
FGPA Firmware Version : 01.12
iLO-3 Firmware Version : 01.01.02
Power Monitor Firmware Version: 03.04
Onboard Administrator (OA)
OA Firmware Version : 3.00
HP Smart Update Manager (HP SUM)
HP SUM Version : 3.7.1
FEEDBACK
As we are continuing to improve the firmware management process we welcome
your feedback on this document and on the firmware update process.
TEAM-FWupdateFeedback@external.groups.hp.com