Power6 Mid-Range Firmware
Applies to: 9117-MMA and 9406-MMA
This document provides information about the installation of Licensed
Machine or Licensed Internal Code, which is sometimes referred to generically
as microcode or firmware.
1.0 Systems Affected
This package provides firmware for System p 570 (9117-MMA) and System
i 570 (9406) Servers
not use on any
The firmware level in this package is:
2.0 Important Information
ECA620 Withdrawn for 9117-MMA Systems
ECA620 has been withdrawn and cannot be ordered after 11/07/07. It
will be replaced by ECA702, which will be available in the near future.
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.
3.0 Firmware Information
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
examples are for clarification only, and are not
necessarily levels that have been, or will be released.
An installation is disruptive if:
Example: Currently installed release is EM310, new release is EM320
The release levels (XXX) are different.
Example: EM310_120_120 is disruptive, no matter what level of EM310
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 EM310_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
new service pack is EM310_152_130
An installation is concurrent if:
Example: Currently installed service pack is EM310_126_120,
The service pack level (YYY) is higher than the service pack
level currently installed on your system.
new service pack is EM310_143_120.
System firmware file naming convention:
NOTE: Values of service pack and last disruptive service pack
level (YYY and ZZZ) are only unique within a release level (XXX).
For example, 01EM310_067_045 and 01EM320_067_053 are different service
XXX is the release level
YYY is the service pack level
ZZZ is the last disruptive service pack level.
Firmware Information and Update Description
Additional features and functions:
System firmware changes that affect all 9117-MMA systems:
Added support for 9406-MMA.
Additional information concerning this service pack:
HIPER: A problem was fixed that caused the system to crash
with SRC B170E450.
HIPER: A problem was fixed that, in rare circumstances, could
cause the system to hang due to the improper handling of certain exceptions.
HIPER: A problem was fixed that prevented the operating system
from being notified of certain EPOW conditions that could lead to the system
or partition being shut down, with the possible loss of data. These
EPOW conditions included the ambient temperature being too high, the loss
of utility power (with or without UPS backup), and a user-initiated power
off using the white power button or the HMC.
A problem was fixed that could cause a firmware installation from the HMC
to fail with SRC E302F85C on the HMC, and SRC B1813088, B1818A0F, or B1813011
logged in the service processor error log.
A change was made so that if a failure occurs during a memory-preserving
reboot, the system continues to reboot rather than remaining in the termination
(powered off) state.
A problem was fixed that caused EEH (enhanced error handling) errors to
be erroneously logged against certain I/O adapters.
A problem was fixed that prevented "linked" resources that had been guarded
out from being reconfigured during the next reboot after a service action
on one of the guarded parts.
A problem was fixed that, after the backplane was replaced in a 7314-G30
I/O drawer, prevented the partition that owned the drawer from seeing those
A problem was fixed that caused the serial connection to a partition to
be lost. When this occurred, SRCs B181D307, B200E0AA, and/or B200813A
were generated by the service processor and the hypervisor.
A problem was fixed in partition firmware that, in some circumstances,
prevented a CD-ROM or tape device from being in the default service mode
boot list, even if one was present in the system.
A problem was fixed that caused the HMC to go to the incomplete state,
and SRC B182953C to be logged in the service processor error log every
five minutes or so, when the managed system was booted.
A problem was fixed that caused the system to intermittently fail to configure
devices attached to the integrated USB port when booting.
A problem was fixed that might have caused erroneous callouts if a problem
was found with certain levels of memory controller chips.
A problem was fixed that caused the system to call home and reboot instead
of allowing the failing part (a memory controller or DIMM) to be deconfigured
by PRD (processor runtime diagnostics).
In addition to the fixes described above, this service pack also contains
a fix for a low probability problem and content intended for newly-manufactured
systems, or enhancements to system internal interfaces, which is not required
for systems already in production use. This content will not
be activated on systems that install this service pack concurrently.
Even though this content is not required for systems which are already
installed and in use, a disruptive installation of this service pack or
a re-IPL after installing it will cause this content to become active.
It is not necessary to plan a window for re-IPL the system the activate
How to Determine Currently Installed Firmware Levels
You can view the server's current firmware level on the Advanced System
Management Interface (ASMI) Welcome pane. It appears in the top right
corner. Example: SF310_057.
the Firmware Package
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
You may download the rpm file for system firmware from this location
to your server, an ftp server, or a CD-ROM. If your system is HMC-managed,
you will also need to download the xml file located on the final download
page. Make sure the file names have the format 01SF3xx_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 image 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.
6.0 Installing the Firmware
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 Chapter 9. Updates, section Mangaged Systems Updates at:
If the release level will stay the same (Example: Level EM310_075_075
is currently installed and you are attempting to install level EM310_081_075)
this is considered an update.
If the release level will change (Example: Level EM310_081_075 is currently
installed and you are attempting to install level EM320_096_096) this is
considered an upgrade.
7.0 Change History
|Nov 9, 2007
||Information in Section 2.0 concerning ECA620 has been revised.
|Oct 15, 2007
||Added information in Section 2.0 concerning mandatory ECA620.