Power6 High-End System Firmware
Applies to: 9119-FHA
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 595 (9119-FHA) 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 running a code level 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
Service Pack 1 ( PTF
MH01212) and
MH01217 (or higher).
Although the Minimum HMC Code level for this firmware is listed
above, HMC level V7 R3.5.0 with PTF MH01238
(Service Pack 3), or
higher is
suggested for
this
firmware level.
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 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.
1.2 Minimum SDMC Code
Level
This section is intended to describe the "Minimum Systems Director
Management Console (SDMC) Code Level"
required by the System Firmware to complete the firmware installation
process. When installing the System Firmware, the SDMC level must be
equal to or higher than the "Minimum SDMC Code Level" before starting
the system firmware update. If the SDMC managing the server
targeted for the System Firmware update is running a code level lower
than the "Minimum SDMC
Code Level" the firmware update will not proceed.
The Minimum SDMC Code level for
this firmware is: SDMC V6
R7.3.0 with Mandatory PTF MF53082.
For information concerning SDMC releases and the latest PTFs,
go
to the following URL to access Fix Central:
http://www-933.ibm.com/support/fixcentral/
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
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.
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.
Note: The concurrent levels
of system firmware may, on occasion,
contain
fixes that are known as Deferred and/or Partition-Deferred. Deferred
fixes can be installed
concurrently, but will not be activated until the next IPL.
Partition-Deferred fixes can be installed concurrently, but will not be
activated until a partition reactivate is performed. Deferred
and/or Partition-Deferred
fixes,
if any, will be identified in the "Firmware Update Descriptions" table
of this document. For these types of fixes (Deferred and/or
Partition-Deferred) 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:
01EHXXX_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,
01EH330_067_045 and 01EH340_067_053 are different service
packs.
An installation is disruptive if:
- The release levels (XXX) are different.
Example: Currently installed release is EH330, new release is EH340
- The service pack level (YYY) and the last disruptive
service
pack level (ZZZ) are the same.
Example: EH330_120_120 is disruptive, no matter what level of EH330 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 EH330_120_120 and
new service pack is EH330_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 EH330_126_120,
new service pack is EH330_143_120.
Firmware Information and Update Description
For information about previous firmware release levels, see Section
7.0 Firmware History
| Filename |
Size |
Checksum |
| 01EH350_108_038.rpm |
36937852
|
41485
|
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 01EH350_108_038.rpm
EH350
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
|
| EH350_108_038
07/07/11
|
Impact:
Availability
Severity: HIPER
- High Impact/PERvasive, Should be installed as soon as
possible.
System firmware changes that
affect all systems
- A problem was fixed that
caused some of the extended error log data to be parsed
incorrectly. This problem only occurs on systems with a large
number of deconfigured components.
System firmware changes that
affect certain systems
- HIPER: On
systems running
VIOS, a problem was fixed that caused the system to crash with SRC
B700F103.
- On systems running
shared processor partitions, a problem was fixed that caused a
partition to hang until powered off and back on.
Concurrent maintenance (CM)
firmware fixes
- The firmware
was enhanced to allow the concurrent replacement of the secondary
service processor even if the service processor redundancy policy
is set to "disabled".
|
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: EH350_038.
5.0 Downloading
the
Firmware Package
Follow the instructions on Fix Central. You must read and agree to
the
license agreement to obtain the firmware packages.
Note: If your HMC or SDMC 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: EHXXX_YYY_ZZZ
Where XXX = release level
- If the release level will stay the same (Example: Level
EH330_075_075
is
currently installed and you are attempting to install level
EH330_081_075)
this is considered an update.
- If the release level will change (Example: Level EH330_081_075 is
currently
installed and you are attempting to install level EH340_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/EH-Firmware-Hist.html