Power7 High-End Power Subsystem Firmware
Applies to: 9125-F2C
This document provides information about the installation of
Licensed
Machine or Licensed Internal Code, which is sometimes referred to
generically
as microcode or firmware.
Contents
This package provides firmware for IBM Power 775 (9125-F2C)
Servers only. Do not use on any other
systems.
The firmware level in this package is:
HMC-Managed Systems
This firmware level requires a minimum HMC level of:
HMC V7 R7.3.0 Service Pack 1.
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.
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:
02APXXX_YYY_ZZZ
- XXX is the release level
- YYY is the service pack level
- ZZZ is the last disruptive service pack level
NOTE: Values of service pack and last disruptive service
pack level (YYY and ZZZ) are only unique
within a release level (XXX). For example, 02AP730_067_045 and
02AP731_067_045 are different
service packs.
An installation is disruptive if:
- The release levels (XXX) are different.
Example: Currently installed release is AP730, new release is
AP731
- The service pack level (YYY) and the last
disruptive service pack level (ZZZ) are equal.
Example: AP730_061_061 is disruptive, no matter what level of
AP730 is currently
installed on the system
- 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.
Example: Currently installed service pack is AP730_120_120 and
new service pack is AP730_152_130
An installation is concurrent if:
- The service pack level (YYY) is higher than the service
pack level currently installed on your system.
Example: Currently installed service pack is AP730_061_061,
new service pack is AP730_070_061.
Firmware Information and Update Description
| Filename |
Size |
Checksum |
| 02AP730_092_092.rpm |
16,899,205 |
17111 |
| 02AP730_092_092
06/13/2012
|
Impact: Serviceability
Severity: SPE
- The number of required Water Cooling Units and Bulk Power
Supplies (BPRs) has been changed. The requirement is based on the
number of installed cages and the input line voltage/type
- Changed the pump speeds in various conditions for the Water
Cooling Units
- Fixed problems with running downlevel Fill & Drain Tools
- Fixed some BPR rails not turning on after DC input is lost
and recovered
- Changed the current balancing procedure to prevent power
supplies being left unbalanced
- Added detection and reporting of lack of water flow to Disk
Enclosure power supplies
- Fixed Disk Enclosure being erroneously powered off while
servicing a port card
- Fixed various erroneously reported error codes
|
| 02AP730_086_086
04/09/2012
|
Impact: Function
Severity: SPE
- Added support for DC input power
- Improved error detection, fault prevention, and fault
recovery on node power supplies
- Fix Disk Enclosure power supply fans not reaching max speed
when required
- Add recovery of Disk Enclosure power supplies if they
reboot due to loss of bias voltage
- Various fixes for Fill & Drain tool
- Fix incorrect power information being reported to XCAT (BPR
current and Disk Enclosure power usage)
|
| 02AP730_071_071
01/23/2012
|
Impact: Function
Severity: SPE
- Fixed BPC incorrectly going to 'Rack Standby' mode after
service of the BPA
- Fixed generation of various erroneous bulk power supply
(BPR) error codes
- Fixed BPRs not being enabled after completion of service
- Fixed some BPRs incorrectly remaining on after frame is
switched off
- Implemented common firmware to support various Fill/Drain
Tool hardware levels
- Various Fill/Drain Tool operation fixes
- Enhancements and fixes to Water Conditioning Unit
operation, error detection, and service
- Allow extra Water Conditioning Units to be configured to
prevent over-temperature issues for "over-configured" systems
- Enhancements and fixes to CEC power supply operation, error
detection, and service
- Fixed LEDs incorrectly remaining on after service of Disk
Enclosure drives
- Prevent defective port cards from causing Disk Enclosure
power on reset to "hang"
- Improved fault handling for Disk Enclosure port card faults
to prevent erroneous side effect error codes
- Improved Disk Enclosre fan speed algorithm to prevent
overheating for small configurations
|
| 02AP730_054_054
12/02/2011
|
Impact: Function
Severity: SPE
- Enhancements and fixes to Water Conditioning Unit
operation, error detection, and service
- Enhancements and fixes to Fill/Drain tool operation and
service
- Enhancements and fixes to frame's bulk power supply (BPR)
operation and service
- Enhancements and fixes for CEC power supplys to prevent
erroneous power faults and add recovery
- Support to light up the frame roll-up LED when servicing
BPA parts
- Emergency Power Off Warning (EPOW) support for Hot Water /
Hot Room
- Support for unlocking of Disk Enclosure carriers for service
- Increase the number of CECs allowed to power on when
running in low voltage DC range from 4 up to 8
- Many other fixes to service/erroneously generated faults
- Various other general stability/usability fixes
|
| 02AP730_042_042
08/26/2011
|
Impact: New
Severity: NEW
- General Availability Level
|
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. Example: AP730_042.
Follow the instructions on the web page. You must read and agree to
the license agreement to obtain the firmware packages.
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.
Example: EPXXX_YYY_ZZZ
Where XXX = release level
- If the release level will stay the same (Example: Level
AP730_075_075 is currently installed and you are attempting to
install level AP730_081_075) this is considered an update.
- If the release level will change (Example: Level AP730_081_075
is currently installed and you are attempting to install level
AP731_096_096) this is considered an upgrade.
Instructions for installing firmware updates and upgrades can be found
at http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/ipha1/updateschapter.htm