Notes on system firmware updates - IBM eServer xSeries 260, 366, 460, MXE 460

Resolving The Problem

RETAIN tip: H186770

Multiple system firmware updates have been released on the affected systems. This tip explains the need for the updates.

The system may be any of the following IBM servers:

• IBM eServer xSeries MXE 460, Type 8874, any model
• IBM eServer xSeries 460, Type 8872, any model
• IBM eServer xSeries 366, Type 8863, any model
• IBM eServer xSeries 260, Type 8865, any model
  
  

A description of the firmware levels is provided below:

Code Designations: For this note, released code groupings are designated as IPMI 1.5 and IPMI 2.0. - IPMI 1.5 versions - build ID's: x366, x460 x260 BIOS v1.08-ZUJT47C v1.06-ZUJT40B BMC v1.20D-ZUBT35D v1.16D-ZUBT32D CPLD v1.05-HEUD17A v1.03-HEUD10A RSA II v1.07-ZUEP31B v1.05-ZUEP27A DIAG v1.04-ZUYT21A v1.03-ZUYT20A SASHDD FW B51C update not required on x260 ServeRAID8i FW 8264 8264 Onbd SAS cntrl FW v1325 v1548 Onbd BCom FW v3.36 on CD 1.20.17 v3.36 on CD 1.20.17. This code package was available on the Interim UpdateXpress CD. IPMI 2.0 versions - build ID's: This code package is available for the current models: x260, x366, x460, MXE-460 and for the "RoHS" models: x3800, x3850, x3950, x3950 E.

BIOS version 1.09 - ZUJT54A BMC version 2.06 - Z2BT05D version 2.06 CPLD version 1.06 - HEUD18A version 1.06 RSAII version 1.08 - ZUEP37C DIAG version 1.05 - DUYT27A This code package will be available on a future UpdateXpress CD.

Backflash IPMI 2.0 to IPMI 1.5: If it is required to backflash a system to IPMI 1.5 from IPMI 2.0 levels, the Interim UX CD should be used instead of legacy flash utilities. The BMC flash utility for BMC ZUBT35D and ZUBT32D have the functions needed to convert the BMC Settings data structures from IPMI 2.0 format to IPMI 1.5 format. Earlier BMC flash utilities do not have this capability. If the BMC Settings are not correctly converted, unpredictable behavior may occur, and this behavior may not be initially seen. Note that the flash utility for IPMI 2.0 BMC has the ability to convert up the Settings from the IPMI 1.5 data structure.

Avoid flashing System x3800, x3850, and x3950 system BMC and BIOS firmware to IPMI 1.5 and earlier levels The System x3800, x3850, and x3950 models have Hurricane 3.0 level chipsets which may exhibit data issues if run with BMC and BIOS at older levels. The IPMI 1.5 BMC and BIOS flash utilities have interlocks that prevent flashing if a Hurricane 3.0 level chipset is sensed. However, earlier BMC and BIOS flash utilities do not have this capability, so it is recommended that customers with customized flash deployment software replace the flash utilities with IPMI 1.5 utilities to avoid inadvertent flashing Hurricane 3.0 systems with downlevel code.

IBM eServer xSeries 360, x366, x460, and MXE460 systems should update to a minimum of IPMI 1.5 levels The IPMI 1.5 group is a critical update for the following reasons: SAS HDD firmware B51C- fix for system freezes, hangs under heavy I/O ServeRAID 8i - fix for system freezes, hangs under heavy I/O BMC flash utility - provides the full BMC Settings conversion needed to flash down from IPMI 2.0 levels; also prevents inadvertent flashing systems with Hurricane 3.0 chipsets. Note that the actual code is the same as ZUBT35A, ZUBT32A (currently on web) BIOS flash utility - prevents inadvertent flashing systems with Hurricane 3.0 chipsets. Note that the actual code is the same as ZUJT47A, ZUJT40A (currently on web).

IBM eServer xSeries 260, x366, x460, and MXE460 systems should have a plan to update to IPMI 2.0 levels There are no critical updates in IPMI 2.0 levels from IPMI 1.5 levels for IBM eServer xSeries 260, x366, x460 and MXE-460. However, there are some minor fixes as well as support for the IPMI 2.0 protocol, so IBM recommends that customers plan to update to IPMI 2.0 levels at the next opportunity.

System x3800, x3850, x3950, and x3950 require IPMI 2.0 levels These systems have Hurricane 3.0 chipsets, and should not be run with earlier ("pre-IPMI 2.0") code. Otherwise unpredictable behavior may occur.

Multi-node updates: All nodes in an IBM eServer xSeries 460, xSeries MXE460, System x3950, and System x3950 multi-node configuration are required to be at the same code levels to guarantee functional performance.

CPLD Updates require the system to be AC power cycled There is a CPLD chip on each of the Processor, I/O, and PCI-X boards which contains Memory and Logic linked with programmable interconnects. Linked logic provides device-to-device interfaces, data communication, signal processing, timing and control operations. The memory cells define how the logic is interconnected, and these interconnects are established at power up. Because the CPLD control power to the boards, it is not possible to modify the interconnects during operation without removing power to the board.

To allow programming CPLD chips during operation without removing power to the boards (On The Fly, or OTF, programming), the CPLD chips contain nonvolatile flash memory and volatile memory. In OTF programming, the flash memory is updated with new code while the board is powered up and running on the interconnects established by the volatile memory. At the next power cycle, the flash memory is copied to the volatile memory area, which is then used to establish the Logic interconnects. The CPLD then initiates board power, and the system starts. This sequence describes why it is necessary to perform an A/C power cycle to have new CPLD code take effect after a flash update.