Power6 High-End Power Subsystem Firmware
Applies to: 9125-F2A
This document provides information about the installation of Licensed Machine
or Licensed Internal Code, which is sometimes referred to generically as
microcode or firmware.
This package provides firmware for Power 575 (9125-F2A) Servers only.
Do not use on any other systems.
The firmware level in this package is:
This firmware level requires HMC V7 R3.3.0 with
MH01119 and MH01130.
Go to the following URL to access the HMC code packages:
NOTE: You must be logged in as hscroot in order for the
firmware installation to complete correctly.
WARNING: This Power Subsystem Firmware Update (EP330_049) is Disruptive!
To install the Power Subsystem Firmware and System Firmware follow the instructions below:
- Power off all of the 9125-F2A Managed Systems
- Update the Managed Frame firmware ONLY (during this step the Managed Systems will transition from "Power Off" to "No Connection" and then back to "Power Off")
- Wait for all 9125-F2A Managed Systems to return to the "Power Off" state
- Cycle the Managed Frame's UEPO switch (Turn the Red Switch Off ; wait one minute ; Turn the Red Switch back On)
- Wait for the Managed Frame to return to the "Standby/Standby" state
- Update the firmware for each Managed System (Managed Systems should still be in "Power Off" state during firmware update)
- Power on the Managed Systems
Use the following example as a reference to determine whether your installation
will be concurrent or disruptive.
Note: The file names and service pack levels used in the following
examples are for clarification only, and are not
necessarily levels that have been, or will be released.
Power Subsystem firmware file naming convention:
NOTE: Values of service pack and last disruptive service pack
level (YYY and ZZZ) are only unique
- XXX is the release level
- YYY is the service pack level
- ZZZ is the last disruptive service pack level
within a release level (XXX). For example, 02EP330_067_045 and 02EP340_067_053
An installation is disruptive if:
Example: Currently installed release is EP330, new release is EP340
- The release levels (XXX) are different.
Example: EP330_120_120 is disruptive, no matter what level of EP330
- The service pack level (YYY) and the last disruptive
service pack level (ZZZ) are equal.
installed on the system
Example: Currently installed service pack is EP330_120_120 and
- The service pack level (YYY) currently installed on the system is
lower than the last disruptive service pack level (ZZZ) of the service pack
to be installed.
new service pack is EP330_152_130
An installation is concurrent if:
Example: Currently installed service pack is EP330_126_120,
- The service pack level (YYY) is higher than the service
pack level currently installed on your system.
new service pack is EP330_143_120.
Firmware Information and Update Description
- Service Pack 2
- Fix for intermittent false Logic Temperature Sensor SRCs
- Fix for code update failures to I/O power supplies
- Fix for false power supply SRCs during concurrent firmware update
- Fix for the hardware management console (HMC) getting stuck at "Pending Authentication" for the rear Bulk Power Controller (BPC)
- Updates to cable error logging
- Change to prevent 11008710/11008711 SRCs during code update to an IH DCA (power supply)
- Updates to error logging to add a secondary FRU to the list of possible failing hardware
- Fix for false SRCs while servicing a Cross-Power Cable
- Fix for posting a defective power supply SRC when the fault was a defective fan
- Support for posting high/low room temperature SRCs and improved handling of high logic temperature
- Fix for internal communication problems in power supplies
- Support for low power mode on Air-cooled IH systems
- Fix for a missing FRU call-out in some MWU (Modular Water Unit) SRCs
- Fix for reversed cable descriptions in power supply SRCs
- Fix for code updates to MWUs (Modular Water Units)
- Fix for false SRCs during power supply code update
- Improved handling of code update of fans and Bulk Power Regulators (BPRs)
- Fix for code update failing to run on both Bulk Power Controllers (BPCs)
- Fix for failure to power on I/O drawers
- Fix for Bulk Power Regulators (BPRs) not recovering properly after line cord removal/replacement
- Update to Health Check behavior to prevent HSCF0168E error
- Fix for false 14010135 SRC
- Fix for false 14012051/14012052 SRCs
- Improvement to prevent water flow oscillations in Modular Water Units (MWUs)
- Improved handling of water level sensors in Modular Water Units (MWUs)
- Improvements to the Fill and Drain Tool
- Service Pack 1
- BPC to BPC communication enhancements
- BPF Fan speed setpoint changes
- Fix for false B1868C59 reference codes
- Change to memory throttling initiation point
- Fix for false 14017195 reference code when UEPO cable is disconnected
- Fixes for wrong/missing FRUs in PEL logs
- Fixes for problems during code download of power FRUs
- Fix for missing I/O drawer after BPC reset or BPC code update
- Fix for occasional slow BPC performance
- Change to prevent exit from Power Save if power supply fails
while in Power Save
- Support for new 8.8KW BPR
- Improved handling of VRM failures in power supplies
- Fix to prevent loss of I/O drawer VPD data during replacement
of I/O power supplies
- Improvements to the CEC power supply balancing function
- Change to shift load to the rear BPRs if front BPF fan fails
- Support for concurrent code update of 9125-F2A power supplies
You can view the frame's current firmware level on the Advanced System Management
Interface (ASMI) Welcome pane. It appears in the top right corner.
The firmware is located at the web site
Follow the instructions on this web page. You must read and agree to the
license agreement to obtain the firmware packages.
In the drop-down box, choose the entry for your specific machine type and
You may download the individual .rpm and .xml files for Power
Subsystem firmware from this location to your server, an ftp server, or a
CD-ROM (both files are required). Make sure the file names have the
format 02EP3xx_yyy_zzz, with an extension of .rpm and .xml before copying
them to your server, an ftp server or CD-ROM. If using a CD-ROM,
copy the .rpm and .xml files to the CD-ROM using a local CD-ROM burner utility.
Another method is to download the .iso file and create a CD-ROM
to use with your HMC.
Note: If your HMC is not internet-connected you will need to download
the new firmware level to a CD-ROM or ftp server.
The method used to install new firmware will depend on the release level
of firmware which is currently installed on your server. The release level
can be determined by the prefix of the new firmware's filename.
Where XXX = release level
Instructions for installing firmware updates and upgrades can be found in
Guide for the Hardware Management Console and Managed Systems, see Chapter
9. Updates, section Managed Systems Updates.
- If the release level will stay the same (Example: Level EP330_075_075
is currently installed and you are attempting to install level EP330_081_075)
this is considered an update.
- If the release level will change (Example: Level EP330_081_075 is
currently installed and you are attempting to install level EP340_096_096)
this is considered an upgrade.
See Chapter 9. Updates, section Mangaged Systems Updates.
|September 16, 2008
- Corrected warning message ". . . Update (EP330_046) is Disruptive!" to ". . . Update (EP330_049) is Disruptive!" in section 2.0
|September 9, 2008
- Revised "HMC V7 R3.3.0 with MH01119 and MH01126" to "HMC V7 R3.3.0 with MH01119 and MH01130" in section 2.0
|September 2, 2008
- Added this Change History Section
- Revised "HMC V7 R3.3.0 with MH01102" to "HMC V7 R3.3.0 with MH01119 and MH01126" in section 2.0