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.
Contents
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:
HMC-Managed Systems
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.
Installing Power Subsystem Firmware and System Firmware
Atention: 9125-F2A servers should be evaluated for ECA845 installation
prior to performing firmware upgrades. Contact your service provider
for more information about ECA845. If firmware must be upgraded prior
to the installation of ECA845, use the following special instructions:
Firmware updates should be performed on an entire Managed Frame and all
Managed Systems
contained in that frame at one time. The following instructions
can be used to update
one Managed Frame and all Managed Systems that it contains. The
instructions can be
repeated as many times as needed until all Managed Frames have been
updated.
1) Power off all Managed Systems in the Managed Frame
2) Reinstall the current firmware level on all Managed Systems in the
Managed Frame:
The following command can be used to determine the current
firmware level:
lslic -t sys -m <managedsystem_1>
-F activated_level
The following command will retrieve and reinstall the current
firmware level on
one Managed System:
updlic -o a -m <managedsystem_1> -t
sys -l <current_fsp_level> -r <repos>
<current_fsp_level> is the level determined
with the lslic command.
<repos> is the location of the firmware
such as "-r dvd", "-r ibmwebsite", etc.
Additional parameters might be required,
depending on the repository selection.
If the firmware has already been retrieved
to the HMC, the HMC hard drive (-r disk)
should be used as the repository.
After the firmware has been retrieved to the HMC, the HMC
hard drive (-r disk) should
be used as the repository to update the remaining Managed
Systems:
updlic -o a -m <managedsystem_2> -t
sys -l <current_fsp_level> -r disk
updlic -o a -m <managedsystem_3>
-t sys -l <current_fsp_level> -r disk
......
updlic -o a -m <managedsystem_N>
-t sys -l <current_fsp_level> -r disk
These commands can be run in the background in parallel to
speed up the processing.
Wait for all updlic commands to complete before proceeding
to step 3.
3) Install and activate new BPC firmware only (during this step the Managed
Systems will
transition from "Power Off" to "No Connection" and then
back to "Power Off"):
Select 1 Managed System as the target of the updlic command
and update BPC firmware.
The following command will retrieve firmware from the repository
and update the BPCs:
updlic -o a -m <managedsystem_1> -t
power -l latest -r <repos> .....
<repos> is the location of the firmware
such as "-r dvd", "-r ibmwebsite", etc.
Additional parameters might be required,
depending on the repository selection.
If the firmware has already been retrieved
to the HMC, the HMC hard drive (-r disk)
should be used as the repository.
4) Wait for all Managed Systems to return to "Power Off" state.
5) Install and activate new firmware on all Managed Systems in the Managed
Frame.
updlic -o a -m <managedsystem_1> -t
sys -l latest -r <repos> .....
<repos> is the location of the firmware
such as "-r dvd", "-r ibmwebsite", etc.
Additional parameters might be required,
depending on the repository selection.
If the firmware has already been retrieved
to the HMC, the HMC hard drive (-r disk)
should be used as the repository.
After the firmware has been retrieved to the HMC, the HMC
hard drive (-r disk) should
be used as the repository to update the remaining Managed
Systems:
updlic -o a -m <managedsystem_2> -t
sys -l latest -r disk
updlic -o a -m <managedsystem_3>
-t sys -l latest -r disk
......
updlic -o a -m <managedsystem_N>
-t sys -l latest -r disk
These commands can be run in the background in parallel to
speed up the process.
Wait for all updlic commands to complete before proceeding
to step 6.
6) 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:
02EPXXX_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, 02EP330_067_045
and 02EP340_067_053 are different
service packs.
An installation is disruptive if:
- The release levels (XXX) are different.
Example: Currently installed release is EP330, new release is EP340
- The service pack level (YYY) and the last
disruptive service pack level (ZZZ) are equal.
Example: EP330_120_120 is disruptive, no matter what level of EP330
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 EP330_120_120 and
new service pack is EP330_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 EP330_126_120,
new service pack is EP330_143_120.
Firmware Information and Update Description
| Filename |
Size |
Checksum |
| 02EP330_092_078.rpm |
18,067,511 |
38635 |
| EP330_092_078 05/18/2009
|
Impact: Serviceability Severity: SPE
- Service Pack 4
- Fix to prevent Bulk Power Controller reset/reload when the Bulk Power Hub is defective
- Fix for false 14010135 SRC after cable fault
- Fix for false 14012x5x SRCs
- Fix to prevent Bulk Power Controller reset/reload when reading VPD from specific components
- Fix for extraneous SRCs posted after specific power supply faults
- Fix for SRC 14010080 where CEC DCAs were powering on during Frame Initialize (and setting voltage values to zero)
- Change to not power of the 9125-F2A node for a fan fail
- Fix for HMC 'Add Drawer' function failing on 9125-F2A
- Fix for 9125-F2A not being able to power on after node repair
- Fix for incorrect Modular Water Unit part number in Serviceable Event log
- Change to add Overcurrent and Overvoltage protection to the valve in the Fill and Drain Tool
- Fix for Concurrent Firmware Update fail on 9125-F2A
- Fix for Concurrent Node Add failure on 9119-FHA
- Fix for false 140130x5 SRCs
- Fix for failure of Frame Initialize to power on all I/O drawers
- Fix for incorrect customer voltage and current readings
- Fix for incorrect 9125-F2A SRC Posted for defective node fan
|
| EP330_078_078
01/15/2009
|
Impact: Function Severity: Hiper
- Service Pack 3
- Enhanced fault reporting for the Integrated Battery
Feature
- Overcurrent protection for the driver card on the
Fill/Drain Tool
- Modular Water Unit performance enhancements
- Fixes for false System Reference Codes during UEPO
cycling
- Fixes for false System Reference Codes during AC power
outages
- Fix for I/O fans not going to the proper speed after
concurrent I/O power supply replacement
- Fixes for false System Reference Codes during Concurrent
Firmware Maintenance
- Fixes for various other false System Reference Codes
- Fix for problem syncing the HMC Service Lock between
both Bulk Power Controllers
- Fix for BPC reset/reload problem on frames with large
F2A configurations
- Fix for F2A CEC power supply failure during Concurrent
Firmware Maintenance
- Fix for failing false 'transition to Low Power Mode
failed' message when AC power is lost on one side
|
| EP330_057_029
10/20/2008
|
Impact: Function
Severity: Hiper
- Service Pack 2++
- Corrects a problem that causes all nodes in the frame
to transition into 'Low Power Mode' where all nodes will run
at reduced performance
|
| EP330_054_029
09/22/2008
|
Impact: Function
Severity: Hiper
- Service Pack 2+
- Corrects a problem introduced in BPC level EP330_049
that could result in SRCs 11008720 /21 being generated. If
level EP330_049 is installed, IBM recommends you install this
level (EP330_054) as soon as possible
|
| EP330_049_029
08/28/2008
|
Impact: Function
Severity: Hiper
- 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
|
| EP330_029_029
06/10/2008
|
Impact: Function
Severity: Hiper
- 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
|
| EP330_017_017
05/13/2008
|
Impact: New
Severity: New
|
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: EP330_029.
The firmware is located at the web site
http://www14.software.ibm.com/webapp/set2/firmware/gjsn
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
model.
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.
Example: EPXXX_YYY_ZZZ
Where XXX = release level
- 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.
Instructions for installing firmware updates and upgrades can be found in the
Operations Guide for the Hardware Management Console and Managed Systems.
See the Managed Systems Updates section in Chapter 9. Updates.