Power7 Mid-Range Systems Firmware
Applies to: 9117-MMB and 9179-MHB
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 Power 770 (9117-MMB) and Power
780 (9179-MHB) 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 R7.1.0 Service Pack 2 (PTF MH01219)
or
higher.
For information concerning HMC releases and the latest PTFs,
go
to the following URL to access Fix Central.
http://www-933.ibm.com/support/fixcentral/
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
Downgrading firmware from any
given release level to an earlier release level is not recommended.
If you feel that it is necessary to downgrade the firmware on
your system to an earlier release level, please contact your next level
of support.
WARNING
For servers with a single CEC
enclosure running AM720_xxx_yyy, attempts to downgrade firmware to
AM710_065_043, AM710_083_043, or AM710_086_043 will not complete successfully.
The managing HMC will lose its connection with the server and manual
intervention will be required to complete the installation. To correct
this condition reference the below link, or contact your hardware
support representative.
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/AM720-AM710-Dgrd_Rcvry.html
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.
Concurrent Firmware Updates
Concurrent system firmware update is only supported on HMC Managed
Systems
only.
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:
01AMXXX_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,
01AM720_067_045 and 01AM740_067_053 are different service
packs.
An installation is disruptive if:
- The release levels (XXX) are different.
Example: Currently installed release is AM710, new release is AM720
- The service pack level (YYY) and the last disruptive
service
pack level (ZZZ) are the same.
Example: AM720_120_120 is disruptive, no matter what level of AM720 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 AM720_120_120 and new
service
pack is AM720_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 AM720_126_120,
new
service pack is AM720_143_120.
Firmware Information and Update Description
Filename |
Size |
Checksum |
01AM710_083_043.rpm |
25880393
|
20545 |
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 01AM710_083_043.rpm
AM710
For Impact, Severity and other Firmware definitions, Please
refer to the below 'Glossary of firmware terms' url:
http://www14.software.ibm.com/webapp/set2/sas/f/power5cm/home.html#termdefs
|
AM710_083_043
06/07/10 |
Impact: Serviceability
Severity: ATT
System firmware changes that affect all systems
- The firmware was enhanced to
dynamically update the IPL speed on the control (operator) panel when
the IPL speed is changed by another method.
- A problem was fixed that
caused the service processor to crash with SRC B181720D due to an
out-of-memory condition.
- A problem was fixed that
caused SRC B113E504 SRCs with a description of "Undefined Error Code"
to be erroneously logged.
- The firmware was enhanced such
that if a memory controller fails or overheats, the memory
controller/DIMM will be called out rather than the processor card.
- Two problems
were fixed that caused SRCs B181B8F8 and SCR B181B86A to be erroneously
logged during a mainstore dump. In both cases, the SRC being
logged prevented the mainstore dump data from being collected and
erroneously called out hardware for replacement.
- A problem was fixed the
prevented the reset/reload bit from being set correctly in a service
processor error log entry.
- 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
- PARTITION-DEFERRED:
A problem was fixed
that caused SRC BA210000 to be erroneously logged on the target system
when a partition was moved (using Live Partition Mobility) from a
Power7 system to a Power6 system.
- A problem was fixed that
caused SRC BA280000 to be erroneously logged on the target system when
a partition was moved (using Live Partition Mobility) from a Power7
system to a Power6 system.
- On systems with the Active
Energy Manager in IBM Director activated, a problem was fixed that
caused a small error in the processor usage calculations.
- 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.
- A problem was fixed that
caused a system or partition running Linux to crash when the
"serv_config -l" command was run.
- On systems in an i5/OS
clustering configuration, a problem was fixed that prevented a
partition in an I/O pool from being deleted.
|
AM710_065_043
03/16/10 |
Impact:
New
Severity: New
GA Level
|
4.0
How to Determine Currently Installed Firmware Level
For HMC managed systems:
From the HMC, select Updates in the navigation (left-hand) pane, then
view the current levels of the desired server(s).
Alternately, use the Advanced System
Management Interface (ASMI) Welcome pane. The current server
firmware appears in the top right
corner.
Example: AM710_yyy.
5.0
Downloading the Firmware Package
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: AMXXX_YYY_ZZZ
Where XXX = release level
- If the release level will stay the same (Example: Level
AM710_075_075
is
currently installed and you are attempting to install level
AM710_081_075)
this is considered an update.
- If the release level will change (Example: Level AM710_081_075 is
currently
installed and you are attempting to install level AM720_096_096) this
is
considered an upgrade.
For details on installing the firmware, perform the
following steps:
1. Go to the IBM Power System Hardware Information Center at:
http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp
2. Select the platform and model you are working with.
3. Select from the following options:
- For details on getting firmware fixes
through the HMC:
- select Working with consoles, terminals and interfaces >
Managing the Hard Management Console > Updates > Managed System
Updates.
- For details on getting firmware fixes
through AIX, IBM i, or
Virtual I/O Server:
- select Troubleshooting, Service, and support > Getting fixes
> Getting firmware fixes.
IBM i Systems
See "Server Firmware and HMC
Wizard",
http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes
7.0 Change History
Date |
Description |
Oct 06, 2010 |
- Added Cautions section 2.1
with Downgrade warnings.
- Other minor documentation updates |