Power7 System Firmware
Applies to: 8202-E4D; 8205-E6D;
8231-E1D; 8231-E2D; 8246-L1D; 8246-L2D;
8246-L1T; 8246-L2T, 8268-E1D and 8493-SV6.
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 710 (8231-E1D, 8268-E1D), Power
720 (8202-E4D), Power 730
(8231-E2D), Power 740 (8205-E6D, 8493-SV6), PowerLinux 7R1 (8246-L1D,
8246-L1T)
and PowerLinux
7R2 (8246-L2D, 8246-L2T) 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.7.0
(PTF MH01343) with Mandatory efix (PTF MH01345).
Although the Minimum HMC
Code level for this firmware is listed
above, HMC level V7 R7.7.0 Service Pack 3 (PTF MH01379), 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
NOTES:
-You must be logged in as hscroot in order for the
firmware
installation to complete correctly.
- Systems Director Management Console (SDMC) does not support this
System Firmware level.
2.0 Important
Information
F/C 5260, 5899, and EL11 (4-Port
Gigabit Ethernet PCI-Express Adapter) added to a system running AL770
system
firmware
If
a 4-Port Gigabit Ethernet PCI-Express Adapter (F/C 5260, 5899, or EL11)
is taken
from an existing system and installed in an 8202-E4D, 8205-E6D,
8231-E1D, 8231-E2D, 8246-L1D, 8246-L2D, 8246-L1T, or 8246-L2T system
running AL770 system firmware, there is a potential issue with the
adapter microcode. To resolve this issue, install the latest
Ethernet adapter firmware, version 10050160 (or higher), feature codes
5260, 5899, EL11.
This adapter firmware addresses a problem that causes IBM i network
install to fail (with SRC B2006110) on partitions running with AL770
system firmware on the models listed above. This fix is also
recommended for partitions running AIX, VIOS, and Linux operating
systems.
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.
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
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.
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 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:
01ALXXX_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,
01AL720_067_045 and 01AL770_063_032 are different service
packs.
An installation is disruptive if:
- The release levels (XXX) are different.
Example: Currently installed release is AL710, new release is AL720
- The service pack level (YYY) and the last disruptive
service
pack level (ZZZ) are the same.
Example: AL720_120_120 is disruptive, no matter what level of AL720 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 AL720_120_120 and new
service
pack is AL720_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 AL720_126_120,
new
service pack is AL720_143_120.
Firmware Information and Update Description
Filename |
Size |
Checksum |
01AL770_063_032.rpm
|
41243880 |
27645 |
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 01AL770_063_032.rpm
AL770
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
The complete Firmware Fix History for this
Release Level can be
reviewed at the following url:
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/AL-IOCp-Firmware-Hist.html
|
AL770_063_032 / FW770.31
01/14/14 |
Impact: Serviceability
Severity: SPE
New Features and Functions
- Support was added for a new Smart Analytics system,
8493-SV6. The IBM 8493 Smart Analytics System model SV6 is derived from
the Power 740 model 8205-E6D.
System firmware changes that affect all systems
- A firmware code update problem was fixed that caused a
system failure with SRC B7000103 when the allowed resource usage was
exceeded for the partition universal unique identifier (UUID)
processing
during a code update.
- A firmware code update problem was fixed that caused the
Hardware Management Console (HMC) to go to "Incomplete State" for the
system with SRC E302F880 when assignment of a partition universal
unique identifier (UUID) failed for a partition that was already
running. This problem happens for disruptive code updates from
pre-770 levels to 770 or later levels.
|
AL770_062_032 / FW770.30
12/10/13 |
Impact: Availability
Severity: SPE
New Features and Functions
- Support was added to upgrade the service processor to
openssl version 1.0.1 and for compliance to National Institute of
Standards and Technologies (NIST) Special Publications 800-131a.
SP800-131a compliance required the use of stronger cryptographic keys
and more robust cryptographic algorithms.
- Support was added in Advanced System Management Interface
(ASMI) to facilitate capture and reporting of debug data for system
performance problems. The "System Service Aids/Performance
Dump" menu was added to ASMI to perform this function.
- Support was added to the Advanced System Management
Interface (ASMI) to provide a menu for "Power Supply Idle Mode".
Using the "Power Supply Idle Mode" menu, the power supplies can
be either set enabled to save power by idling power supplies when
possible or set disabled to keep all power supplies fully on and allow
a balanced load to be maintained on the power distribution units (PDUs)
of the system. Power supply idle mode enabled helps to reduce
overall power usage when the system load is very light by having one
power supply deliver all the power while the second power supply is
maintained in a low power state.
- Support was added to the Advanced System Management
Interface (ASMI) to provide a menu for "Memory Low Power State Control"
to enable or disable the custom memory buffer low power mode. If
set to disabled, it disables low power mode (a power-saving feature) to
speed memory and improve performance for some workloads. The
"Memory Low Power State Control" menu is not available on the MTM
9117-MMC system because its memory does not have a low power state
option.
- Support was added for the IBM Flash 90 (#ES09) PCIe 2.0 x8
eMLC adapter with 900GB storage and 350,00 IOPS read performance.
The system recognizes the PCI device as one needing additional cooling
and increases the fan speeds accordingly.
- Support was added in Advanced System Management Interface
(ASMI) for saving and restoring network settings using a USB flash
drive.
- Support was dropped for Secured Socket Layer (SSL) protocol
version 2 and SSL weak and medium cipher suites in the service
processor web server (Lighttpd) . Unsupported web browser
connections to the Advanced System Management Interface (ASMI) secured
port 443 (using https://) will now be rejected if those browsers do not
support SSL version 3. Supported web browsers for Power7 ASMI are
Netscape (version 9.0.0.4), Microsoft Internet Explorer (version 7.0),
Mozilla Firefox (version 2.0.0.11), and Opera (version 9.24).
- Support was added in Advanced System Management Interface
(ASMI) "System Configuration/Firmware Update Policy" menu to detect and
display the appropriate Firmware Update Policy (depending on whether
system is HMC managed) instead of requiring the user to select the
Firmware Update Policy. The menu also displays the "Minimum Code
Level Supported" value.
System firmware changes that affect all systems
- The firmware was enhanced to display on the management
console the correct number of concurrent live partition mobility (LPM)
operations that is supported.
- A problem was fixed that caused a 1000911E platform event
log (PEL) to be marked as not call home. The PEL is now a call
home to allow for correction. This PEL is logged when the
hypervisor has changed the Machine Type Model Serial Number (MTMS) of
an external enclosure to UTMP.xxx.xxxx because it cannot read the vital
product data (VPD), or the VPD has invalid characters, or if the MTMS
is a duplicate to another enclosure.
- When powering on a system partition, a problem was fixed
that caused the partition universal unique identifier (UUID) to not get
assigned, causing a B2006010 SRC in the error log.
- For the sequence of a reboot of a system partition followed
immediately by a power off of the partition, a problem was fixed where
the hypervisor virtual service processor (VSP) incorrectly retained
locks for the powered off partition, causing the CEC to go into
recovery state during the next power on attempt.
- A problem was fixed that caused the system attention LED to
be lit without a corresponding SRC and error log for the event.
This problem typically occurs when an operating system on a partition
terminates abnormally.
- A problem was fixed that caused a memory leak of 50 bytes
of service processor memory for every call home operation. This
could potentially cause an out of memory condition for the service
processor when running over an extended period of time without a reset.
- A problem was fixed that caused a L2 cache error to not
guard out the faulty processor, allowing the system to checkstop again
on an error to the same faulty processor.
- A problem was fixed that caused a HMC code update failure
for the FSP on the accept operation with SRC B1811402 or FSP is unable
to boot on the updated side.
- A problem was fixed that caused a built-in self test (BIST)
for GX slots to create corrupt error log values that core dumped the
service processor with a B18187DA. The corruption was caused by a
failure to initialize the BIST array to 0 before starting the tests.
- A problem was fixed that caused a SRC B7006A72 calling out
the adapter and the I/O Planar.
- A problem was fixed during resource dump processing that
caused a read of an invalid system memory address and a SRC
B181C141. The invalid memory reference resulted from the service
processor incorrectly referencing memory that had been relocated by the
hypervisor.
System firmware changes that affect certain systems
- On systems running AIX or Linux, a problem was fixed that
caused the operating system to halt when an InfiniBand Host Channel
Adapter (HCA) adapter fails or malfunctions.
- On systems running AIX or linux, a hang in a Live Partition
Mobility (LPM) migration for remote restart-capable partitions was
fixed by adding a time-out for the required paging space to become
available. If after five minutes the required paging space is not
available, the start migration command returns a error code of
0x40000042 (PagingSpaceNotReady) to the management console.
- On systems running Dynamic Platform Optimizer (DPO) with no
free memory, a problem was fixed that caused the Hardware
Management System (HMC) lsmemopt command to report the wrong status of
completed with no partitions affected. It should have indicated
that DPO failed due to insufficient free memory. DPO can only run
when there is free memory in the system.
- On systems with partitions using physical shared processor
pools, a problem was fix that caused partition hangs if the shared
processor pool was reduced to a single processor.
- On systems with a ethernet PCI-Express adapter under a PLX
switch, an extended error handling (EEH) problem was fixed in run-time
abstraction services (RTAS) that caused fundamental resets of the
adapter to fail during error recovery, leaving the adapter in a
non-pingable state and off the network. Besides failure to ping,
the other symptom is that an AIX OS command of "enstat -d entX" where X
is the adapter number will fail with the following message:
"enstat -0909-004, Unable to get statistics on device entX, errno=11".
- On systems with a F/C 5802 or 5877 I/O drawer installed,
the firmware was enhanced to guarantee that an SRC will be generated
when there is a power supply voltage fault. If no SRC is
generated, a loss of power redundancy may not be detected, which can
lead to a drawer crash if the other power supply goes down. This
also fixes a problem that causes an 8 GB Fiber channel adapter in
the drawer to fail if the 12V level fails in one Offline Converter
Assembly (OCA).
- On systems managed by an HMC with a F/C 5802 or 5877 I/O
drawer installed, a problem was fixed that caused the hardware topology
on the management console for the managed system to show "null" instead
of "operational" for the affected I/O drawers.
- On Power7+ systems, a problem was fixed that caused a
system checkstop during hypervisor time keeping services.
- On systems with a F/C 5802 or 5877 I/O drawer installed, a
problem was fixed that where a Offline Converter Assembly (OCA) fault
would appear to persist after a OCA micro-reset or OCA
replacement. The fault bit reported to the OS may not be cleared,
indicating a fault still exists in the I/O drawer after it has been
repaired.
|
AL770_052_032 / FW770.21
08/07/13 |
Impact: Availability
Severity: SPE
System firmware changes that affect all systems
- A problem was fixed that caused a migrated partition to
reboot during transfer to a VIOS 2.2.2.0, and later, target system. A
manual reboot would be required if transferred to a target system
running an earlier VIOS release. Migration recovery may also be
necessary.
- A problem was fixed that can cause Anchor (VPD) card
corruption and A70047xx SRCs to be logged. Note: If a
serviceable event with SRC A7004715 is present or was logged
previously, damage to the VPD card may have occurred. After the fix is
applied, replacement of the Anchor VPD card is recommended in
order to restored full redundancy.
System firmware changes that affect certain systems
- On systems running Dynamic Platform Optimizer (DPO) ,
a problem was fixed that caused an incorrect placement of dedicated
processors for partitions larger than a single chip. When this
occurs, the performance is impacted over what would have been gained
with proper placement.
|
AL770_048_032 / FW770.20
05/17/13 |
Impact: Availability
Severity: SPE
New Features and Functions
- Support for the 8268-E1D systems.
System firmware changes that affect all systems
- A problem was fixed that caused a service processor
reset/reload with SRC B181720D due to a memory leak.
- The Hypervisor was enhanced to allow the system to continue
to boot using the redundant data chip on the anchor (VPD) card, instead
of stopping the Hypervisor boot and logging SRC B7004715, when
the primary data chip on the anchor card has been corrupted.
- A problem was fixed that caused a service processor dump to
be generated with SRC B18187DA "NETC_RECV_ER" logged.
- A problem was fixed that caused the date and time to be
incorrect in AIX if a partition is remotely restarted on a different
system from the one on which it was hibernated.
- A problem was fixed that caused a performance loss after a
configuration change, such as un-licensing a processor, because the
Hypervisor is unable to dispatch a partition to a shared
processor.
- A problem was fixed that may cause inaccurate processor
utilization reporting.
System firmware changes that affect certain systems
- On systems running Active Memory Sharing (AMS) partitions,
a problem was fixed that caused the system to hang after an AMS
partition was deleted or mobilized, combined with either an AMS pool
resize or relocation of AMS pool memory.
- On systems with I/O towers attached, a problem was fixed
that caused multiple service processor reset/reloads if the tower was
continuously sending invalid System Power Control Network (SPCN) status
data.
- On 8202-E4D and 8205-E6D systems with the PCIe expansion
card feature code (F/C) 5610 or F/C 5685 installed, a problem was fixed
that caused the wrong FRU part number (74Y8565 instead of 74Y5221) to
be called out when the fan on the expansion card failed.
- On systems managed by a management console, a problem was
fixed that was caused by an attempt to modify a virtual adapter from
the management console command line when the command specifies it is an
Ethernet adapter, but the virtual ID specified is for an adapter type
other than Ethernet. The managed system has to be rebooted to
restore communications with the management console when this problem
occurs; SRC B7000602 is also logged.
- On systems running Dynamic Platform Optimization (DPO), a
problem was fixed that caused the current DPO score for a partition to
be incorrect. When this occurs, it looks like DPO would not
improve performance when in fact it would improve the
performance. Also, on systems running Dynamic Platform
Optimization (DPO), in which there are no processors in the shared
processor pool, a problem was fixed that caused the Hypervisor to
become unresponsive (the service processor starts logging time-out
errors against the Hypervisor, and the HMC can no longer talk to the
Hypervisor) during a DPO operation.
|
AL770_038_032 / FW770.10
03/21/13 |
Impact:
Availability
Severity: SPE
System firmware changes that affect certain systems
- On
systems running Active Memory Sharing (AMS) partitions, a problem was
fixed that caused the system to hang after an AMS partition was deleted
or mobilized, combined with either an AMS pool resize or relocation of
AMS pool memory.
- On systems running Active Memory Sharing (AMS) partitions,
a problem was fixed that may arise due to the incorrect handling of a
return code in an error path during the logical partition migration
(LPM) of an AMS partition.
- On systems running Active Memory Sharing (AMS) partitions,
a timing problem was fixed that may occur if the system is running
Dynamic Platform Optimization (DPO).
|
AL770_032_032 / FW770.00
02/20/13 |
Impact:
New
Severity: New
New Features and Functions
- Support for the 8202-E4D and 8205-E6D systems.
- Support for the 8231-E1D and 8231-E2D systems.
- Support for the 8246-L1D, 8246-L2D, 8246-L1T, and 8246-L2T
systems.
- Support for version 2 of the EnergyStar standard.
|
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).
For
standalone system running IBM i
without an HMC:
From a command line, issue DSPFMWSTS.
For standalone system running IBM AIX
without an HMC:
From a command line, issue lsmcode.
Alternately, use the Advanced System
Management Interface (ASMI) Welcome pane. The current server
firmware appears in the top right
corner.
Example: AL710_yyy.
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 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: ALXXX_YYY_ZZZ
Where XXX = release level
- If the release level will stay the same (Example: Level
AL710_075_075
is
currently installed and you are attempting to install level
AL710_081_075)
this is considered an update.
- If the release level will change (Example: Level AL710_081_075 is
currently
installed and you are attempting to install level AL720_096_096) this
is
considered an upgrade.
HMC Managed Systems:
Instructions for installing firmware updates and upgrades on
systems
managed by an HMC can be found at:
http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/p7ha1/updupdates.htm
Systems not Managed by an HMC:
p Systems:
Instructions for installing firmware on systems that are not
managed
by an HMC can be found at:
http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/p7ha5/fix_serv_firm_kick.htm
IBM i Systems:
See "IBM Server Firmware and HMC Code Wizard":
http://www-912.ibm.com/s_dir/slkbase.NSF/DocNumber/408316083
NOTE: For all systems running
with
the IBM i Operating System, the following IBM i PTFs must be applied to
all IBM i partitions prior to installing AL770_063:
- V7R1M0 - MF51869
- V6R1M1 - MF51864
NOTE: For all systems running
with the IBM i Operating System and without an HMC attached, the
following IBM i PTFs must be applied to all IBM i partitions in
addition to the PTFs listed above, prior to installing AL770_063:
- V7R1M0 - MF51814 and SI41153:
- V6R1M1 - MF51225
These PTFs can be ordered through Fix Central.
7.0 Firmware History
The complete Firmware Fix History for this Release Level can be
reviewed at the following url:
http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/AL-IOCp-Firmware-Hist.html