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. Do not use on any other systems.

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 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.

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. 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:

01EHXXX_YYY_ZZZ

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:

Example: Currently installed release is EH330, new release is EH340 Example: EH330_120_120 is disruptive, no matter what level of EH330 is currently
installed on the system Example: Currently installed service pack is EH330_120_120 and
new service pack is EH330_152_130

An installation is concurrent if:

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_103_038.rpm 36711918 23450
   
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_103_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_103_038

02/21/11

Impact: Data           Severity:  HIPER - High Impact/PERvasive, Should be installed as soon as possible.

System firmware changes that affect certain systems
  • HIPER: IBM testing has uncovered a potential undetected data corruption issue when a mobility operation is performed on an AMS (Active Memory Sharing) partition.  The data corruption can occur in rare instances due to a problem in IBM firmware.  This issue was discovered during internal IBM testing, and has not been reported on any customer system. IBM recommends that systems running on EH340_075 or later move to EH350_103 to pick up the fix for this potential problem.  (Firmware levels older than EH340_075 are not exposed to the problem.)
  • On systems with a F/C 5803 or 5873 I/O drawer attached, a problem was fixed that caused a partition to crash during a page migration operation.
  • A problem was fixed that caused a partition to crash with SRC BA330002 after several concurrent installations of system firmware, or partition migrations, without a reboot.
  • A problem was fixed that caused AIX licensing issues when migrating a partition from a P6 to a P7 system.
  • On systems running IBM i partitions, a problem was fixed that caused SRC BA040030 to be erroneously logged, and a call home to be made, even though the partition booted successfully.
EH350_085_038

10/26/10

Impact: Availability           Severity:  HIPER - High Impact/PERvasive, Should be installed as soon as possible.

System firmware changes that affect all systems

  • HIPER:  A problem was fixed that caused the HMC to show the server's status as incomplete, and SRC B7000602 to be logged against SFLPHMCCMDTASK in serviceable events.  This problem can also cause the system to crash when it occurs.
  • HIPER:  A problem was fixed that caused repeated reset/reloads of the service processor, and fail-overs, to occur after a hypervisor-initiated reset/reload of the service processor was completed.  That led to loss of communication between the service processor and the hypervisor (indicated by SRC B182951C).
  • A problem was fixed that caused a CEC node to unexpectedly lose power, and caused a system crash.  Systems that had a service processor role change at server power off are exposed to this issue.
  • A problem was fixed that caused SRC B181440D to be erroneously logged.
  • The firmware was enhanced to log SRC B181D30B as informational instead of predictive.
  • The firmware was enhanced to list the attached devices when viewing the adapter information for a partition profile on the HMC GUI.
  • A problem was fixed that caused the hypervisor to issue almost continuous reset/reload requests to the service processor.
System firmware changes that affect certain systems
  • The firmware was enhanced to support the network installation of the IBM i operating system from the hardware management console (HMC) command line interface (CLI).
  • On systems using the IPv6 protocol, a problem was fixed that caused valid link local and unique link local addresses to be erroneously invalidated.  This prevented the port with that address from being used for network boot or network installation.
EH350_071_038

06/30/10

Impact: Usability        Severity:   SPE

System firmware changes that affect all systems

  • DEFERRED: A problem was fixed that could result in a system checkstop while running floating point computations.  Although this is a high-impact problem, it has a very low probability of occurring.
  • 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.
  • The firmware was enhanced to improve the callouts for certain types of processor failures that log SRC B1xxE504.
  • The firmware was enhanced to make a hidden error log visible when a failing GX adapter caused errors to be logged by the processor run-time (PRDF) diagnostics.
  • The firmware was enhanced to improve the callouts when NVRAM corruption is detected in the bulk power controller's (BPC's) service processor.
  • On systems running EH350_xxx firmware, 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 SRC B181E617 to be erroneously logged and a service processor dump to be unnecessarily generated.
System firmware changes that affect certain systems
  •  On systems running the IBM i operating system, a problem was fixed that caused a DLPAR move operation with an IOP (I/O processor) and IOA (I/O adapter) to fail intermittently.  The DLPAR operation was successful, but the IOA failed to power on in the new partition.
Concurrent maintenance (CM) firmware fixes
  • A problem was fixed that would cause a concurrent maintenance operation to fail if the HMC was rebooted before the previous CM operation was complete.
  • On systems with F/C 5803 or F/C 5873 I/O drawers attached and a boot device in the drawer, a problem was fixed that prevented a partition from booting after the concurrent repair of the GX adapter that connects the 5803 or 5873 drawer to the system, or to the node that contains the GX adapter.
EH350_049_038

03/10/10

Impact: Serviceability           Severity:   HIPER

System firmware changes that affect all systems

  • HIPER: A problem was fixed that caused the system to crash if the server was running AIX and had a  F/C 5802 or 5877 drawer (in a 19" rack), or F/C 5803 or 5873 drawer (in a 24" rack), attached.
  • DEFERRED:  This fix corrects the handling of a specific processor instruction sequence that has the potential to result in undetected data errors.  This specific instruction sequence has only been observed in a small number of highly tuned Floating Point intensive applications.  However, it is strongly recommended that this fix be applied to all POWER6 systems.  This fix has the potential to decrease system performance on applications that make extensive use of floating point divide, square root, or estimate instructions.
  • A problem was fixed that prevented an SRC from being recorded in the service processor dump produced by a host-initiated reset.
  • A problem was fixed that prevented the repair of a deconfigured system controller from being completed successfully.
  • A problem was fixed that caused SRC 10009135, followed by 10009139, to be erroneously logged.  These SRCs indicate a system power control network (SPCN) loop is being broken, then re-established.
  • The firmware was enhanced to allow a temporary threshold reduction for processor unit book interconnect predictive errors.
  • A problem was fixed that caused a reset/reload of a network controller.
  • A problem was fixed that, under certain rare circumstances, caused a partition to hang when being shut down.
  • A problem was fixed that caused the system to hang with SRCs B182953C, B182954C and B17BE434 being logged.
  • The firmware was enhanced to detect and handle 12X InfiniBand I/O drawer cabling errors better.
  • A problem was fixed that, under certain rare circumstances, caused the system to become unresponsive and appear to hang  when page migration occurred on a PCIe slot.
System firmware changes that affect certain systems
  • A problem was fixed that caused a virtual SCSI or virtual fibre channel adapter to be seen by the operating system as not bootable when it was added to a partition using a dynamic LPAR (DLPAR) operation.
  • On systems running IBM i, a problem was fixed that caused booting the operating system from a fibre channel device to fail with SRC 576B8301.
  • On systems with a F/C 5802 or 5877 drawer attached, a problem was fixed that could impact the performance of a 4-port Ethernet adapter F/C 5272, 5275, 5279, 5280, 5525, 5526, or 5527 installed in that drawer.
  • In partitions running AIX or Linux, a problem was fixed that caused the addition of an I/O slot to a partition using a dynamic LPAR (DLPAR) add operation to fail.
  • On systems with shared processors, a problem was fixed that caused the partitions to hang and become unresponsive for very short periods of time.
  • A problem was fixed that prevented the IPv6 DHCP address from being displayed on the advanced system management interface (ASMI) network configuration screens when IPv6 and DHCP were enabled.  This only occurred on systems with virtual LAN (VLAN) addresses (such as eth0.30, eth0.31), and when IPv6 addresses were assigned to the eth0.xx interface.
  • On systems running redundant VIOS partitions, a problem was fixed that prevented Ethernet traffic from being properly bridged between the two partitions.  This problem also prevented shared Ethernet adapter failover from working correctly.
  • A problem was fixed that caused the hypervisor to loop unnecessarily and consume too many processor cycles.  This impacted the performance of the system.
Concurrent maintenance (CM) firmware fixes
  • The firmware was enhanced such that if an Ethernet cable is misplugged on a node controller during a concurrent node add operation, the node add operation will be completed successfully.
  • A problem was fixed that prevented the concurrent repair of a redundant system controller.
  • A problem was fixed that caused unpredictable system behavior if a capacity on demand (CoD) or a virtualization engine technology (VET) activation code was entered and accepted after a node 0 evacuation was done.  The unpredictable machine behavior might also have occurred, if a node 0 evacuation failed, a system dump was taken, and a memory-preserving IPL was then initiated.
  • A problem was fixed that caused a concurrent maintenance operation after a node evacuation to fail.  When this problem occurred, the system erroneously states that a platform memory dump is pending.
  • A problem was fixed that prevented a concurrent maintenance operation from completing successfully.
EH350_038_038

10/30/09

Impact: Function           Severity:   Special Attention 

New Features and Functions:

  • Support for the concurrent repair of a system controller.
  • Support for the concurrent removal of 12X-attached 24" I/O drawers.
  • Support for a USB-attached half-high 5.25" backup device using a removable hard disk drive (HDD).
  • Support for a platform dump that is not disruptive.
  • Support for i5/OS multipath storage I/O through VIOS partitions.
System firmware changes that affect all systems
  • A problem was fixed that might cause a concurrent firmware maintenance (CFM) operation to fail repeatedly, or a concurrent maintenance (CM) operation to fail repeatedly, when a large number of I/O loop errors were being logged during the CFM operation.
  • The firmware was enhanced to handle system dumps (SYSDUMPs) larger than 4GB in size.
  • On systems running system firmware release EH340 EH340, a problem was fixed that caused a dynamic LPAR (DLPAR) operation on memory to fail until the platform was rebooted.
  • The firmware was enhanced to improve the performance of the F/C 5732 , 5735, and 5769 PCI-E adapters. The firmware was enhanced such that SRCs B181F126, B181F127, and B181F129 are correctly logged, and no longer calls home unnecessarily for these SRCs.
  • A problem was fixed that caused a repair and verify (R&V) operation on the hardware management console (HMC) to fail with the message "Exception encountered while rendering panel as HTML".
  • The firmware was enhanced such that a generic B1817201 SRC will no longer be logged when a cache error occurs on a node controller (NC).  Unique SRCs will now be logged for cache failures, and upper and lower thresholds have been added to the NC cache error logging scheme.
  • The firmware was enhanced to improve the field replaceable unit (FRU) callouts for SRCs B1xxC004 and B1xxC005.
  • A problem was fixed that might cause the system to crash with SRC B181E504, then SRC B1813909, being logged.
  • The firmware was enhanced to more accurately describe the reason memory was deconfigured on the advanced system management interface (ASMI) memory deconfiguration screen.
  • The firmware was enhanced such that when a certain type of hardware failure occurs in a bulk power controller (BPC), the appropriate errors will be logged instead of SRCs B1818601 and B1818611, which indicate a firmware failure.
  • On systems using the HEA (host Ethernet adapter), also know as the Integrated Virtual Ethernet (IVE) function, a problem was fixed that caused link failures if the HEA was connected to certain third-party Ethernet switches.  A problem causing an unexpected increment in the Pxs_TXIME register, but not affecting network performance, was also fixed.
Concurrent maintenance (CM) firmware fixes
  • A problem was fixed that caused SRC B181A494 to be erroneously logged if a concurrent maintenance operation took longer than 60 minutes.
  • On systems with 24" I/O drawers, a problem was fixed that might cause a partition to crash, with a system reboot required for recovery, when a F/C 5797 or 5798 drawer was concurrently added.
  • On systems with four drawers, a problem was fixed that caused the system controller to perform a reset/reload, which caused a concurrent maintenance operation to fail, on the fourth node (P4).
  • A problem was fixed that caused the current replacement of an InfiniBand GX adapter or I/O planar to fail if a partition owned an embedded device on the planar.


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 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

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