TITLE: HP Integrity BL860c/BL870c/BL890c i4 Servers Firmware and IO Bundle - for HP Smart Update Manager

VERSION:
HP Smart Update Firmware Bundle
Bundle Version: 44.01

System Firmware Version: 02.61
FGPA Firmware Version: 02.02
iLO-3 Firmware Version: 01.62.05
Power Monitor Firmware Version: 03.04
Front Panel HW: 04.00
PRS HW: 02.08
IOH HW: 02.02

I/O components for HP Integrity Servers:
Firmware Flash Component for BL8x0c i4 iocxgbe (LOM): 4.2.401.2212
Firmware Flash Component for BL8x0c i4 p410i SAS: FW 6.22, EFI 3.54
Firmware Flash Component for Add-in Smart Array Adapters : 2013.02.18
p711m: FW  6.22, EFI 3.54
Firmware Flash Component for Qlogic Fibre Channel Host Bus Adapters: 2012.11.30
451871-B21 QMH2562: FW 5.03.15, EFI 2.22
Firmware Flash Component for InfiniBand Adapters: 2012.11.30
592519-B21: FW 2.9.1000
Firmware Flash Component for Emulex Adapters: 2013.05.02
456972-B21 LPe1205: FW 2.02x2, EFI 4.01a5
NC552m: FW 4.2.401.2212, LAN EFI 2.22a1
NC551m, NC553m: FW 4.2.401.2212, LAN EFI 2.22a1, FCoE EFI 5.10.a7
Firmware Flash Component for Intel and Broadcom Adapters: 2012.11.30(c)
      Intel NC360m, NC364m: EFI 4.3.01
   Note: Use this component for Broadcom NC532m only if IEXGBE-DRV revision is lower than B.11.31.1303:
NC532m: FW 6.2.25, EFI 5.2.59

Firmware Flash Component for Broadcom NIC HP-UX: 2013.06.05
   Note: Use this component for Broadcom NC532m only if IEXGBE-DRV version is B.11.31.1303 or later:
NC532m: FW 6.2.25, EFI 5.2.59

HP Smart Update Manager (HP SUM)
HP SUM Version: 5.3.5

Note:

• HP SUM 5.3.5 introduces the capability to update IO firmware on integrity servers using HP SUM. However due to a hang issue when updating p410i SAS IO from 5.82 to another version with HP SUM, p410i SAS IO version 5.82 must continue to be updated using alternate methods (EFI applications, ISO images, ...). All other IO components, including SAS IO 5.84 or later, can be updated using HP SUM.
• If a system FW update is pending, it will be automatically activated at next server power off, and server will only power on after the firmware activation completes.
• To verify if a system FW update is pending, run the iLO3 MP “SYSREV” command and check if the Pending column shows any version for “System FW”.
• While the server is powered off, you can monitor the progress of the system firmware activation by running the iLO3 MP “FW” command.

DESCRIPTION:
This bundle contains the HP Smart Update Manager (HP SUM) application with the firmware for HP Integrity BL860c/BL870c/BL890c i4 Servers (System firmware (SFW), FPGA firmware, iLO-3 MP firmware & Power Monitor and I/O firmware). This bundle can be used to update the firmware using the HP SUM application.

Note:

• OA versions 3.70 and 3.71 are not supported with BL8x0c i4 servers due to the possible loss of network connections during OA failover in configurations with Integrity blades, Virtual Connect and OA 3.70. For more details, see advisory c03613140. You should continue using OA 3.60 until a fix is available.
• It is required to have appropriate SAS RAID firmware (version 6.22 or later) and LAN-On-Motherboard (LOM) firmware (version 4.2.401.2212 or later) installed on your server along with this firmware bundle, available on http://www.hp.com
• Current versions can be checked using the HP-UX commands “ioscan -kfnd ciss”, “sautil /dev/cissx vpd” and “nwmgr -q vpd -c lan0”
• Any update to the information below will be available in the release notes for HP Integrity BL860c/BL870c/BL890c i4 Servers firmware bundles with HP Smart Update Manager, available on http://www.hp.com/

Refer to HP SUM 5.3.5 User Guide and Release notes for more information. 

UPDATE RECOMMENDATION: Critical

[X] Critical 
[  ]  Panic,  [ X]  Hang,  [  ]  Abort,   [  ]  Corruption,  [  ]  Memory Leak,
     [ ]  Other: 
     [  ]  Hardware Enablement,  [  ] Software Enablement
[ ]  Recommended  
[  ]  Optional
     [  ] Hardware Enablement,  [  ]  Software Enablement, [  ]  non-critical
[  ] Initial Customer Release

SUPERSEDES:
HP Integrity BL860c/BL870c/BL890c i4 Servers
Bundle Version: 43.01

PRODUCT MODEL(S):

• HP Integrity BL860c i4 Server
• HP Integrity BL870c i4 Server
• HP Integrity BL890c i4 Server

OPERATING SYSTEMS:

• HP-UX 11i v3 September 2012 Update and later (with Insight Management 7.1.2 patch).  

LANGUAGES:
International English

ENHANCEMENTS:

• Optimized the memory settings to improve the reliability of the memory system.
  Note: WBEMMgtBundle version C.07.01 (or later) is also required for this optimization to be fully effective (see installation information under Pre-requisites)

FIXES:

SFW 2.61:

• Fixed an issue where the execution of the SetTime firmware call might cause short system hangs of 12.75 seconds. Occasionally longer system hangs were observed. The problem may cause affected servers running in a Serviceguard cluster configuration with member timeout values slightly higher than the delay to fail with a Serviceguard INIT due to expiration of the Serviceguard safety timer. Note: other third party clustering products are affected by this issue too
• A server with a controller configured in HBA mode may hang at boot time without any error messages if a Hard Disk configured for RAID mode is put into the server without previously removing the Hard Disk's RAID metadata. This issue is now  fixed.

 Fixes in IO components in this bundle (from IO components in bundle version 43.01):

LAN FW 4.2.401.2212 (from 4.1.450.14) for LOM, NC551m, NC552m, NC553m:

• Critical: As the result of auto negotiation failure, the connection between LOM and ProCurve 6120XG may link up at 1Gbps instead of 10Gbps. This occurs intermittently (as often as once in 10 retries) after executing “Reset Server blade #” from the OA CLI.
  Affected Products - All BE3 based Cards and LOMs. This is also seen with 10G passthrough Interconnect module.
• BL8x0c i4 LOM NIC LED remains green even when the LINK is down on 1Gbps switch module.
• Boot failure might be seen after running commands "reconnect -r", "map -r" commands at EFI environment.
• Boot from SAN intermittently fails during EFI bootstrap of a FCoE device that is busy.
• FCOE EFI version truncated in VPD data that is displayed by ODE-FCFUPDATE tool at EFI.
• On HP-UX, the fcoc port driver state is displayed as AUTHENTICATION/DISCOVERY when fcocutil command is run to check the port information.

LAN EFI 2.22.a1 (from 2.21.ac) for LOM, NC551m, NC552m, NC553m:

• Critical: After power cycling the entire C7000 enclosure, the HP Integrity BL8X0c i4 LOM systematically fails to initialize with Catalyst Switch 3020 when Power Restore is set to ON (PR = ON) and you enter to EFI shell before HP-UX boot. You will see an error similar to: “ iocxgbe: The device at hardware path 0/0/0/3/0/0/0 failed initialization (3821)” during HPUX boot. This issue is only seen with BL8X0c i4 LOM
• Reset to Defaults restores wrong power configuration. It shows an HP unsupported option: “MultiChannel Option”. Reset to Default is issued from Device Manager->Emulex 10G NIC-> R/r or Erase Configuration.
• BL8x0c i4 LOM Product Name is truncated when displayed from NIC interface using FCFUPDATE

SAS FW 6.22 for p410i and p711m:

• HP-UX boot may fail with READ Error (elf_load) if boot volume is built on SAS Logical Volume larger than 2TB
• On rare occasions during power-up of an HP DS2200sb, the expander backplane would be unresponsive and the attached Smart Array Controller would not be allowed to discover attached drives.
• The training of the DDR2 DIMMs has been improved in order to prevent the rare occasions when 1783 POST error messages displays followed by an unresponsive controller.
• Protection has been added to prevent potential Smart Array controller hangs under rare conditions when hot-adding hard drives.
• The Open Connection timeout was reduced to 900 microseconds so that SAS connections terminate gracefully and data transfer stalls are prevented.
• The Smart Array controller would not connect to hard drives within 20ms under heavy stress.
• Upon power up, a Post message will now be displayed to the user to indicate that a cache module is needed for the P711m controller.
• During heavy I/O, when the HP P711m controller is connected to a HP P2000sa G3 MSA Array System via a HP 6Gb SAS Switch, a lockup issue (error code 0x15) might occur.

FC Firmware 2.02x2 (from 2.00a4) for LPe1205:

• I/O “illegal frames received” errors may be reported intermittently by FC disks linked through an 8Gb HP/Emulex FC card if a disk reset is performed during heavy I/O load

PREREQUISITES:

• Warning: A system reboot is required after installing WBEMMgtBundle version C.07.01 (or later) for the system firmware enhancements in this version to be fully effective. To minimize the number of reboots, it is recommended to install WBEMMgtBundle C.07.01 before updating the system firmware to version 44.01. WBEMMgtBundle may be downloaded from http://software.hp.com.
• Onboard Administrator firmware: minimum OA version required is 3.60 
• VC firmware: minimum VC version required is 3.70. Recommended version is 4.01.
• iLO-3 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 HP SUM.

For latest dependencies on SAS IO, LOM, OA and VC, refer to this matrix:
integrity-release-sets

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: This version of HP SUM allows updating of I/O card firmware online on HP-UX, however if your current p410i SAS IO version is 5.82, you must update it using other methods (EFI, ISO image, ...) due to a hang issue when updating from SAS IO 5.82 using HP SUM.  For all other I/O updates via HP SUM, please review the instructions below for using this HP SUM feature.

A. Extracting and Running HP SUM

1. Download the firmware bundle binary <filename>.exe or <filename>.tar.gz in a new folder on your system.
2. Extract the bundle:
• Windows: double click <filename>.exe then click “Extract”
• Linux: gunzip <filename>.tar.gz; tar -xvf <filename>.tar
3. The above steps will extract the contents of the bundle in the new folder where the bundle file is located. HP SUM and firmware components will reside in the same folder.
4. Execute hpsum, located in the extracted folder, by logging as a user with Administrator or root privilege.  Executing hpsum will bring up a graphical user interface of the HP Smart Update Manager (HP SUM).

NOTE: HP SUM also provides a Command Line Interface (CLI) that allows user to perform scripted installations in silent mode. For more information please refer to the HP SUM User Guide or the "CLIHelp.txt" file in the extracted folder.

B. Installing the Firmware Components using HP SUM - Graphical User Mode

1. Welcome Screen:
• Once started, a page displays with HP SUM introduction content on it. The introduction describes HP SUM, its usage and enhancements.
2. Source Selections Screen:
• The Source Selections screen allows you to choose directories where smart components are located.
• The directory where HP SUM is running from is automatically added as the default repository.
• You can optionally have HP SUM check ftp.hp.com for additional firmware or software smart components.  This could include newer components for servers supported in this bundle, plus components for other server types.
• HP SUM will build an inventory of firmware bundles - packages that can be used to update firmware.
• Click the "Next" button to move on to the next step.
3. Select Targets Screen:
• This screen is used to specify which targets you want to update.
• Targets can be added one at a time, or a range can be searched.
• Credentials must be supplied for each target.
• Once added, targets can also be managed in groups.  See the HP SUM user guide for details.
• Click the “Next” button to move on to the next step.
• NOTE on order of performing updates: Any updates to OA, VC and iLO firmware should be done in one HP SUM session first, then exit HP SUM and perform updates to HP-UX I/O firmware in a separate HP SUM session. 
• NOTE on HP-UX I/O firmware: If you want to update I/O card firmware online through HP-UX you must add an IP address for the production HP-UX OS as a target on this screen along with HP-UX root user credentials. 
• NOTE for enclosures: The Onboard Administrator IP address can be added as the first target and HP SUM will find all of the servers and Virtual Connect in the enclosure automatically. A pop up dialog will appear suggesting to add the found associated targets. HP SUM will be able to use the OA credentials to log into the blades iLOs automatically.
• NOTE: “localhost” is not applicable for installing the firmware updates included in this bundle.
4. Review/Install Updates Screen:
• The suggested updates for each target are displayed on this screen.
• This screen also allows for retrieving details of the updates, selecting between available revisions, forcing downgrades and choosing reboot to activate options.
• For more details and component level granularity, select the item and click the "Select Components" link.
  NOTE: If firmware is the latest or already up-to-date version, HP SUM displays the message "Already-up-to-date". You can override and choose to perform force reinstallation or downgrade the firmware by clicking the "Installation Option" and checking “Force Install” option.
  NOTE: Integrity 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" on the Select Components page
• Select the "Upload and Activate" checkbox.
• If "Upload and Activate" is selected, HP SUM 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.
• NOTE: Integrity Superdome 2 nPartition firmware updates can be applied while the partition is Active, but the partition must be rebooted to have the firmware update take effect.  HP SUM defaults to not reboot Active partitions.  If you would like HP SUM to include the partition reboot as part of the firmware update process then:
• Click “Select Devices” on the Select Components page
• Click “Reboot to Activate” next to the Active partitions you  want to reboot.
• If you choose to not continue with install on one or more targets, you can uncheck the box on the left of the target.
• Updates can be scheduled for future times by clicking the “Schedule” button. Once schedules are defined, the “Install” button must still be clicked to activate the schedule.
• Click the “Install” button to start update on all of the checked targets.
• HP SUM will display the progress of the firmware update on each target.
• A status and link to the logs will be displayed for each target at the end of the update.  

Refer HP SUM User Guide and Release notes for more information.

COMPATIBILITY / INTEROPERABILITY:

WARNING: Do not disconnect power supply to HP Integrity Server during the firmware upgrade process or else the ROM will be corrupted and the system board will need to be replaced.

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.

1. Establish a ssh/telnet session with the iLO-3 MP.
2. Logon to the iLO-3 MP using the Administrator password.
3. Type "CM" to enter the Command Menu.
4. 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.62.05
     System FW       : 02.61
     MHW FPGA      : 02.02
     Power Mon FW  : 03.04
     Front Panel HW : 04.00   02.00 and 03.00 are also acceptable
     PRS HW           : 02.08   02.06 and 02.07 are also acceptable
     IOH HW            : 02.02   1.02, 1.03, and 02.00, are also acceptable

KNOWN FIRMWARE ISSUES:

OA 3.60:

• There is a rare chance that a SSH session to iLO from OA, established within a few minutes of an iLO reboot using the ‘connect server’ command, may get disconnected unexpectedly. Connection can be re-established to resume normal operation.

 SFW:

• DDDC (Double Device Data Correction) will not be invoked for a second DRAM failure in certain cases when excessive single bit memory errors are observed. This will be indicated by a WBEM Event 7000. There is no impact to customer applications however it is recommended to service the DIMM upon seeing this event as the server will stop correcting single bits memory errors if one more DRAM in the same rank fails. 

• A server containing a PCI card which does not support PCI extended capability may hang without any error message while handling an MCA.This issue affects the BL8x0c i2 and i4 servers and the rx2800 i2 and i4 servers.

iLO:

• There is a rare chance that a Telnet session to iLO may hang during an operation such as FPL dump where continuous stream of data is being sent by iLO to the client. System and iLO will continue to function normally. To recover, the hung Telnet session may be closed and new sessions can be opened to access iLO. 

KNOWN INSTALLATION ISSUES: 

• Refer to the HP SUM Release Notes for complete list of known HP SUM installation issues

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-2013 Hewlett-Packard Development Company, L.P.

SUPERSEDES HISTORY:

Version: 43.01

ENHANCEMENTS:

None

FIXES:

iLO 01.61.04:

• Fixed a security vulnerability issue that exists in HP Integrated Lights-Out (iLO 3) version 1.60.07 for BL8x0c i4 and versions 1.54.03 and lower for BL8x0c i2. The vulnerability could be remotely exploited resulting in disclosure of information.  See SSRT100934 for more details.
• When the serial port MUX is set to “Persistent AUX” mode and the server is A/C power cycled, the serial port MUX will retain the “persistent AUX” mode setting and will not reset to “iLO” mode.
• The severity of the events "VOLTAGE_FAULT" and "VOLTAGE_LOW_CRITICAL" have been increased so that power supply events in SFM such as  "power supply failed or disconnected" and "power supply AC lost" will now be reported in HP-UX syslog for easier monitoring.
• Fixed an issue where an idle SSH session to iLO3 from a PUTTY client may freeze or may get disconnected with an error message “Incoming packet was garbled on decryption”.
• SSH connection to iLO from an OpenSSH 5.9 client will now work even when a reduced list of key-exchange algorithm is not indicated.

SFW 2.40:

• Fixed an issue where, on rare occasions, the following series of events would be seen in the SEL (System Event Log) during POST (Power-On Self-Test), without being accompanied by a MCA or other errors: MEM_MEM_TEST_FAILED level 3 event, SYSTEM_SOFT_RESET, EFI_LAUNCH_BOOT_MANAGER.

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