Power7 High-End System Firmware
Applies to: 9119-FHB
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 795 (9119-FHB) 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.2.0
(PTF MH01233 or MH01234)
and PTF MH01246 (Service Pack 1).
Although the Minimum HMC Code level for this firmware is listed
above, HMC level V7 R7.2.0 with PTF MH01253 (Service Pack 2), or
higher is
suggested for
this
firmware level.
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/
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
NOTE: You must be logged in as hscroot in order for the
firmware
installation to complete correctly.
2.0 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
Firmware Release Level upgrades and Service Pack updates may consume
additional system memory.
Server firmware requires memory to support the logical partitions on
the server. The amount of memory required by the server firmware varies
according to several factors.
Factors influencing server firmware memory requirements include the
following:
- Number of logical partitions
- Partition environments of the logical
partitions
- Number of physical and virtual I/O devices
used by the logical partitions
- Maximum memory values given to the logical
partitions
Generally, you can estimate the amount of memory required by server
firmware to be approximately 8% of the system installed memory. The
actual amount required will generally be less than 8%. However, there
are some server models that require an absolute minimum amount of
memory for server firmware, regardless of the previously mentioned
considerations.
Additional information can be found at:
http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/topic/p7hat/iphatlparmemory.htm
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. 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:
01AHXXX_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,
01AH330_067_045 and 01AH340_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: AH330_120_120 is disruptive, no matter what level of AH330 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 AH330_120_120 and
new service pack is AH330_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 AH330_126_120,
new service pack is AH330_143_120.
| Filename |
Size |
Checksum |
| 01AH720_102_064.rpm |
49484543 |
41937 |
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 01AH720_102_064.rpm
AH720
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
|
AH720_102_064
08/03/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 the Advanced
System Management Interface (ASMI) menus to be displayed in English no
matter which language was selected.
- The
firmware was enhanced
to verify that no uncorrectable memory errors are present in all of a
partition's memory when the hypervisor accesses that memory.
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 partitions running the Red
Hat Linux 6.1, a problem was fixed that caused a partition migration
operation to fail.
- On systems with an
uninterruptible power supply (UPS) attached, a problem was fixed that
caused the system to power cycle between power on and power off after a
power failure, instead of waiting for the power to be restored before
powering on.
- On systems running Active
Memory Sharing (AMS), a problem was fixed that caused the system to
crash with SRC B170E540 after a warm boot or platform dump IPL.
- A problem was fixed that
prevented the virtual I/O server (VIOS) partition associated with an
Advanced Memory Sharing (AMS) pool from shutting down.
- A problem was fixed that
caused a resume operation on a partition with dedicated memory to fail
with HMC SRC HSC0A945.
- On systems running an
IBM i partition with dedicated memory, and redundant virtual I/O server
(VIOS) partitions, a problem was fixed that caused the resumption of
the IBM i partition to fail if the hypervisor failed-over to the other
VIOS partition while the IBM i partition was in hibernation.
- On systems running
shared processor partitions, a problem was fixed that caused a
partition to hang until powered off and back on.
- On systems running
DB2 pureScale, a problem was fixed that caused intermittent remote
direct memory access (RMDA) errors, and a core dump of the pureScale
server process.
Concurrent hot add/repair maintenance firmware fixes
- On partitions running Red Hat
Linux 6.1, a problem was fixed that caused a node evacuation operation
to fail.
- A problem was fixed that caused the system to crash with
SRC B170E540 during a node evacuation that is done after a warm boot or
platform dump IPL.
|
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: AH350_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: EHXXX_YYY_ZZZ
Where XXX = release level
- If the release level will stay the same (Example: Level
AH330_075_075
is
currently installed and you are attempting to install level
AH330_081_075)
this is considered an update.
- If the release level will change (Example: Level AH330_081_075 is
currently
installed and you are attempting to install level AH340_096_096) this
is
considered an upgrade.
Instructions for installing firmware updates and upgrades can be found
at http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/p7ha1/updupdates.htm
7.0 Firmware History
The Firmware History can be reviewed at the following link:
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/AH-Firmware-Hist.html
8.0 Change History
Date
|
Description
|
September 19, 2011
|
Fix description updates for
firmware level AH720_102 |