Power7 High-End Power Subsystem Firmware
Applies to: 9119-FHB
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 Power 795 (9119-FHB) Servers
only. Do not use on any other systems.
The firmware level in this package is:
HMC-Managed Systems
This firmware level requires HMC V7 R7.3.0.
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:
02ABXXX_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, 02AB720_067_045 and
02AB730_067_053 are different
service packs.
An installation is disruptive if:
- The release levels (XXX) are different.
Example: Currently installed release is AB720, new release is
AB730
- The service pack level (YYY) and the last
disruptive service pack level (ZZZ) are equal.
Example: AB720_061_061 is disruptive, no matter what level of
AB720
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 AB720_120_120 and
new service pack is AB720_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 AB720_061_061,
new service pack is AB720_070_061.
Firmware Information and Update Description
| Filename |
Size |
Checksum |
| 02AB730_113_032.rpm |
16,807,591 |
08411 |
AB730_113_032 /
FW730.70
04/03/2013
|
Impact:
Availability Severity: SPE
Changes:
- Fix CEC power supply code update process from leaving voltage levels
set at slightly lower voltages than normal, in some instances
- Prevent concurrent service to power supplies in above state, to
avoid crashing the node
- Fix I/O drawer service causing drawer to be dropped from
configuration on HMC
- Add diagnostics for dead voltage level 6 on 5797/5798 drawers
- Fix CEC cooling related error codes not being reported to the FSP
and operating system
- Add robustness to fan controller code update process to prevent
update failures
- When a BPA error condition is detected, BPA fan speeds will be
raised to a lower setting than the previous firmware level
- Fix wrong part number being reported in service logs for bulk power
components on IO-only frames
- Fix various erroneous error codes being posted
|
| AB730_095_032
08/22/2012
|
Impact:
Availability Severity: SPE
Changes:
- Enhancements to prevent UIRA risk during concurrent code update
because of erroneous DC input voltage sensing by BPRs
- Fix moving voltage too high at light load during power supply
current balancing; was causing GX adapter issues
- Fix problems powering on the system in a cold room environment
- Improved recovery of power supplies' BCMs and stuck I2C bus
lines
- Add detection for unplugging of battery cables
- Various fixes of erroneous error codes
|
| AB730_077_032
03/14/2012
|
Impact:
Availability Severity: HIPER -
High Impact/PERvasive, should be installed as soon as
possible.
Changes:
- HIPER/Pervasive: Prevent voltage glitches causing
Unrecoverable Events on GX adapters during code update and
service
- Fix errors during service procedure for AC power loss
- Fix HMC failing to obtain BPA lock during service when system is in
base power state
- Fix various erroneously posted errors
- Add sanity checking to the writing of Frame MTMS
|
| AB730_057_032
11/07/2011
|
Impact:
Availability Severity: HIPER -
High Impact/PERvasive, should be installed as soon as
possible.
Changes:
- HIPER/Pervasive: Added algorithm to properly recover a power
supply's BCMs (power train component) from undervoltage spikes or
microcontroller resets
- Fix incorrect location code for the cable referenced in service
code 140221BC
- Fix erroneous power supply overvoltage error (was blocking
concurrent repair of peer power supply)
|
| AB730_051_032
09/28/2011
|
Impact:
Performance Severity: HIPER
- High Impact/PERvasive, should be installed as soon as
possible.
Changes:
- Prevent voltage glitches during CEC power supply
deactivation during code updates and servicing
- Fix error occurring while attempting to resynchronize password with
the BPC
- Prevent erroneous SRC 14022651 during code update
- During service, fix not detecting cabling faults on cages not
directly involved in the service operation
- Fix extraneous SRC posted for BPD overcurrent error
- Fix 14022B01 not being reported properly
- Recovery enhancements for CEC power supply turn-on failures
- Fix wrong part number being reported in service logs for node power
supply
- Improvements to FHA -> FHB model upgrade, to persist bus
IDs
|
| AB730_032_032
05/26/2011
|
Impact:
New Severity: NEW
Changes:
- Various fixes for adding nodes/drawers
- Fix some erroneous errors posted against 5803 I/O drawers
- Fix concurrent service of BPC-BPC communication faults not
working
- Fix service redundancy check failing for dead BPD due to peer
BPC posting miscable fault
|
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: AB720_061.
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: ABXXX_YYY_ZZZ
Where XXX = release level
- If the release level will stay the same (Example: Level
AB720_061_061 is currently installed and you are attempting to
install level AB720_081_061) this is considered an update.
- If the release level will change (Example: Level AB720_061_061
is currently installed and you are attempting to install level
AB730_096_096) this is considered an upgrade.
Instructions for installing firmware updates and upgrades can be found
at http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/p7ha1/updateschapter.htm