Power6 Mid-Range Firmware
Applies to: 9117-MMA , 9406-MMA, and 8234-EMA
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
1.0 Systems Affected
This package provides firmware for System p 570 (9117-MMA), System i570
(9406-MMA), Power 570 (9117-MMA), and Power 560 (8234-EMA) servers
only.
The firmware level in this package is:
1.1 Minimum HMC Code Level
This section is intended to describe the "Minimum HMC Code Level"
required by the System Firmware to complete the firmware installation
process. When installing the System Firmware, the HMC level must be
equal to or higher than the "Minimum HMC Code Level" before starting
the system firmware update. If the HMC managing the server
targeted for the System Firmware update is lower than the "Minimum HMC
Code Level" the firmware update will not proceed.
The Minimum HMC Code level for this firmware is: HMC V7 R3.5.0 with PTFs MH01212 and
MH01217 (or higher).
For specific fix level information on key components of IBM
Power
Systems running the AIX, IBM i and Linux operating systems, we suggest
using the Fix Level Recommendation Tool (FLRT):
http://www14.software.ibm.com/webapp/set2/flrt/home
For information concerning HMC releases and the latest PTFs,
go
to the following URL to access the HMC code packages:
http://www14.software.ibm.com/webapp/set2/sas/f/hmcl/home.html
NOTE: You must be logged in as hscroot in order for the
firmware
installation to complete correctly.
2.0 Cautions
and Important
Information
2.1 Cautions
CEC Concurrent Maintenance
Several CEC Concurrent Maintenance issues have been resolved with this
firmware level. It is important that HMC 7.3.5.0 with PTFs MH01212 and
MH01217 (or higher), and
this Service Pack are installed prior to attempting
to perform a CCM
function. It is also recommended that CCM is performed in a maintenance
window where the system is quiesced (i.e. all applications are shutdown
and the system is idling at the operating system level).
Upgrading from EM320_031 to EM350_xxx
If your current level of firmware is EM320_031
you
must install any higher level of EM320 before upgrading your firmware
to
this level.
Upgrading from EM310_xxx to EM350_yyy
If your current level of firmware is
EM310_xxx,
you must install EM320_040 or higher before upgrading your firmware to
this level.
2.2 Important Information
IPv6 Support and Limitations
IPv6 (Internet Protocol version 6) is supported in the System
Management
Services (SMS) in this level of system firmware. There are several
limitations
that should be considered.
When configuring a network interface card (NIC) for remote IPL, only
the most recently configured protocol (IPv4 or IPv6) is retained. For
example,
if the network interface card was previously configured with IPv4
information
and is now being configured with IPv6 information, the IPv4
configuration
information is discarded.
A single network interface card may only be chosen once for the boot
device list. In other words, the interface cannot be configured for the
IPv6 protocol and for the IPv4 protocol at the same time.
Memory Considerations for Firmware Upgrades
The increase in memory used by the firmware is due to the additional
functionality
in later firmware releases.
3.0 Firmware
Information
and Description
Use the following examples as a reference to determine whether your
installation
will be concurrent or disruptive.
For systems that are not managed by an HMC, the installation of
system
firmware is always disruptive.
Note: The concurrent levels of system firmware may, on occasion,
contain
fixes that are known as deferred. These deferred fixes can be installed
concurrently, but will not be activated until the next IPL. Deferred
fixes,
if any, will be identified in the "Firmware Update Descriptions" table
of this document. For deferred fixes within a service pack, only the
fixes
in the service pack which cannot be concurrently activated are
deferred.
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.
System firmware file naming convention:
01EMXXX_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, 01EM310_067_045 and 01EM320_067_053 are different
service packs.
An installation is disruptive if:
- The release levels (XXX) are different.
Example: Currently installed release is EM310, new release is EM320
- The service pack level (YYY) and the last disruptive
service
pack level (ZZZ) are the same.
Example: EM310_120_120 is disruptive, no matter what level of EM310 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 EM310_120_120 and
new service pack is EM310_152_130
An installation is concurrent if:
- The release level (XXX) is the same, and
- The service pack level (YYY) currently installed on the
system
is
the same or higher than the last disruptive service pack level
(ZZZ)
of the service pack to be installed.
Example: Currently installed service pack is EM310_126_120,
new service pack is EM310_143_120.
Firmware Information and Update Description
For information about previous firmware release levels, see
Section 7.0 Firmware History.
Filename |
Size |
Checksum |
01EM350_071_038.rpm |
24081695
|
07233
|
Note: The Checksum can be found by running the AIX sum command against the rpm file
(only the first 5 digits are listed).
ie: sum 01EM350_071_038.rpm
EM350 |
EM350_071_038
06/30/10
|
Impact: Usability
Severity: ATT
System firmware changes that affect all systems
- A problem was fixed
that caused a call home to be erroneously made with SRC B181E911, and a
service processor dump to be taken unnecessarily.
- A problem was fixed
that caused the HMC to show a status of "Incomplete" for the managed
system, and numerous service processor dumps to be generated.
System firmware changes that affect certain systems
- On systems
running the IBM i operating system, a problem was fixed that caused a
DLPAR move operation with an IOP (I/O processor) and IOA (I/O adapter)
to fail intermittently. The DLPAR operation was successful, but
the IOA failed to power on in the new partition.
Concurrent Maintenance (CM) firmware fixes
- A problem was fixed
that would cause a concurrent maintenance operation to fail if the HMC
was rebooted before the previous CM operation was complete.
|
EM350_063_038
05/10/10
|
Impact: Availability
Severity: HIPER
System firmware changes that affect all systems
- DEFERRED, HIPER: A
problem was fixed that caused SRC B113E504 with word 8 of the SRC =
074B001F or, 0197001F on 8234-EMA systems with processor F/C 7537, and
9406-MMA and 9117-MMA systems with processor F/Cs 7387, 7388 and 7540.
- The firmware was enhanced to
dynamically update the IPL speed on the control (operator) panel when
the IPL speed is changed by another method.
- On systems running EM350_xxx
firmware, a problem was fixed the prevented the reset/reload bit from
being set correctly in a service processor error log entry.
System firmware changes that affect certain systems
- On systems with F/C 5802 or
F/C 5877 I/O drawers attached, the firmware was enhanced to prevent
SRCs 10001510, 10001512, 10001520, and 10001521 from being erroneously
logged when A/C power was removed and reapplied when the drawer is
powered off.
- On systems with redundant
service processors, a problem was fixed that caused SRC B181E617 to be
erroneously logged and a service processor dump to be unnecessarily
generated.
Concurrent maintenance (CM) firmware fixes
- On systems with F/C 5802
or F/C 5877 I/O drawers attached and a boot device in the drawer, a
problem was fixed that prevented a partition from booting after the
concurrent repair of the GX adapter that connects the 5802 or 5877
drawer to the system, or to the node that contains the GX adapter.
|
EM350_049_038
03/15/10
|
Impact: Serviceability
Severity: HIPER
System firmware changes that affect all systems
- HIPER: A problem was fixed that caused the system
to crash with SRCs B700F103 and B181F0E7, if the server was running AIX
and had a F/C 5802 or 5877
drawer (in a 19" rack), or F/C 5803 or 5873 drawer (in a 24" rack),
attached.
- DEFERRED: This fix corrects the
handling of a specific processor instruction sequence that has the
potential to result in undetected data errors. This specific
instruction sequence has only been observed in a small number of highly
tuned Floating Point intensive applications. However, it is
strongly recommended that this fix be applied to all POWER6
systems. This fix has the potential to decrease system
performance on applications that make extensive use of floating point
divide, square root, or estimate instructions.
- A problem was fixed that prevented an SRC from being
recorded in the service processor dump produced by a host-initiated
reset.
- A problem was fixed that caused SRC 10009135, followed by
10009139, to be erroneously logged. These SRCs indicate a system
power control network (SPCN) loop is being broken, then re-established.
- A problem was fixed that, under certain rare circumstances,
caused a partition to hang when being shut down.
- A problem was fixed that caused the system to hang with
SRCs B182953C, B182954C and B17BE434 being logged.
- The firmware was enhanced to detect and handle 12X
InfiniBand I/O drawer cabling errors better.
- A problem was fixed that, under certain rare circumstances,
caused the system to become unresponsive and appear to hang when
page migration occurred on a PCIe slot.
System firmware changes that affect certain systems
- A problem was fixed that caused a virtual SCSI or virtual
fibre channel adapter to be seen by the operating system as not
bootable when it was added to a partition using a dynamic LPAR (DLPAR)
operation.
- On systems running IBM i, a problem was fixed that caused
booting the operating system from a fibre channel device to fail with
SRC 576B8301.
- On systems with a F/C 5802 or 5877 drawer attached, a
problem was fixed that could impact the performance of a 4-port
Ethernet adapter F/C 5272, 5275, 5279, 5280, 5525, 5526, or 5527
installed in that drawer.
- In partitions running AIX or Linux, a problem was fixed
that caused the addition of an I/O slot to a partition using a dynamic
LPAR (DLPAR) add operation to fail.
- On systems with shared processors, a problem was fixed that
caused the partitions to hang and become unresponsive for very short
periods of time.
- A problem was fixed that prevented the IPv6 DHCP address
from being displayed on the advanced system management interface (ASMI)
network configuration screens when IPv6 and DHCP were enabled.
This only occurred on systems with virtual LAN (VLAN) addresses (such
as eth0.30, eth0.31), and when IPv6 addresses were assigned to the
eth0.xx interface.
- On systems running redundant VIOS partitions, a problem was
fixed that prevented Ethernet traffic from being properly bridged
between the two partitions. This problem also prevented shared
Ethernet adapter failover from working correctly.
Concurrent maintenance (CM) firmware fixes
- A problem was fixed that prevented the concurrent repair
of a redundant service processor.
- A problem was fixed that caused unpredictable system
behavior if a capacity on demand (CoD) or a virtualization engine
technology (VET) activation code was entered and accepted after a node
0 evacuation was done. The unpredictable machine behavior might
also have occurred, if a node 0 evacuation failed, a system dump was
taken, and a memory-preserving IPL was then initiated.
- A problem was fixed that caused a concurrent maintenance
operation after a node evacuation to fail. When this problem
occurred, the system erroneously states that a platform memory dump is
pending.
- A problem was fixed that prevented a concurrent
maintenance operation from completing successfully.
|
EM350_038_038
10/30/09
|
Impact:
Function
Severity: Special Attention
New Features and Functions:
- Support for the concurrent removal of 12X-attached 19" I/O
drawers.
- Support for F/C 5877, the diskless version of 19" I/O
drawer F/C 5802.
- Support for a USB-attached half-high 5.25" backup device
using a removable hard disk drive (HDD).
- Support for a platform dump that is not disruptive.
- Support for i5/OS multipath storage I/O through VIOS
partitions.
System firmware changes that affect all systems
- A problem was fixed that might cause a concurrent firmware
maintenance
(CFM) operation to fail repeatedly, or a concurrent maintenance (CM)
operation
to fail repeatedly, when a large number of I/O loop errors were being
logged
during the CFM operation.
- The firmware was enhanced to handle system dumps (SYSDUMPs)
larger than 4GB in size.
- On systems running system firmware release EM340, a problem
was fixed that caused a dynamic LPAR (DLPAR) operation on memory to
fail until the platform was rebooted.
- The firmware was enhanced to improve the performance of the
F/C 5732, 5735 and 5769 PCI-E adapters.
- A problem was fixed that caused a repair and verify
(R&V) operation on the HMC to fail with the message "Exception
encountered while rendering panel as HTML".
- The firmware was enhanced such that SRCs B181F126,
B181F127, and B181F129 are correctly logged, and no longer calls home
unnecessarily for these SRCs.
- The firmware was enhanced to more accurately describe the
reason memory was deconfigured on the advanced system management
interface (ASMI) memory deconfiguration screen.
Concurrent maintenance (CM) firmware fixes
- A problem was fixed that caused SRC B181A494 to be
erroneously logged
if
a concurrent maintenance operation took longer than 60 minutes.
- On systems with four drawers, a problem was fixed that
caused the
service
processor to perform a reset/reload, which caused a concurrent
maintenance
operation to fail, on the fourth drawer.
|
4.0
How to Determine Currently Installed Firmware Level
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: EM350_038.
5.0 Downloading
the
Firmware Package
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.
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.
Example: EMXXX_YYY_ZZZ
Where XXX = release level
- 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 EM320_081_075 is
currently
installed and you are attempting to install level EM340_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/updupdates.htm
7.0 Firmware History
The Firmware History can be reviewed at the following url:
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/EM-Firmware-Hist.html