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 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 R7.3.0
(PTF MH01255 or MH01256) with PTF MH01257 (Mandatory efix).
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.
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 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 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:
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 |
| 01AH730_035_035.rpm |
51454472 |
08521 |
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 01AH730_035_035.rpm
AH730
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
|
| AH730_035_035
05/27/11
|
Impact: New
Severity: New
New Features and Functions
- Support for the attachment of a System Director Management
Console (SDMC).
- Support for up to 1000 partitions on 9117-MMB,
9179-MHB, and 9119-FHB systems.
- Support for IBM i live partition hibernation.
- Support for server platform system dumps
(SYSDUMP files) larger than 4GB.
- Support for power savings settings for certain
partitions and the system processor pool.
- Support for the feature code (F/C) 5887 media drawer.
- Support for remote restart of partitions.
- Support for CEC hot add repair maintenance
operations: hot node add, hot node upgrade (memory), hot node
repair, concurrent GX adapter add, and hot GX adapter repair, on
9119-FHB (Power 795) systems. Contact
your authorized service provider and ask about ECA 256, as hardware may
have to be upgraded to support this function.
System firmware fixes that affect all systems
- A problem was
fixed that erroneously caused SRCs B1608C55
and B181EF88 to be logged, the bulk power controller (BPC) to generate
a dump, and calls home to be made.
|
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: AH730_123.
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
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
IBM i Systems:
See "Server Firmware and HMC Wizard":
http://www-912.ibm.com/s_dir/slkbase.nsf/recommendedfixes
NOTE:
For systems running with the IBM i Operating System, the following IBM
i PTFs must be applied to all IBM i partitions prior to installing
AH730_035:
- V7R1M0 - MF51869
- V6R1M1 - MF51864
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
|
October 17, 2011
|
Added IBM i Systems heading in section 6.0
|
June 20, 2011
|
Updates for SDMC support
|
June 03, 2011
|
Firmware Description and History
table updated to add information for ECA 256
|