Power6 Entry Systems Firmware

Applies to: 8204-E8A, 8203-E4A, 9407-M15, and 9408-M25

This document provides information about the installation of Licensed Machine or Licensed Internal Code, which is sometimes referred to generically as microcode or firmware.

1.0 Systems Affected
2.0 Important Information
3.0 Firmware Information and Description
4.0 How to Determine Currently Installed Firmware Level
5.0 Downloading the Firmware Package
6.0 Installing the Firmware
7.0 Change History Revised (12/02/2008)

1.0 Systems Affected

This package provides firmware for System p 550 (8204-E8A), System p 520 (8203-E4A), System i 515 (9407-M15) and System i 525 (9408-M25), servers only. Do not use on any other systems.

The firmware level in this package is:

EL320_046

Updating your system firmware from EL320_031 or EL320_040 directly to EL320_076 (in one step) can not be performed concurrently. An interim firmware level, EL320_046, has been created that will allow an update to EL320_076 concurrently.

To reduce the amount of time required to perform this update and to activate any deferred content in EL320_076, Product Engineering recommends that the firmware update from EL320_031 or EL320_040, directly to EL320_076 is performed disruptively during a scheduled window.

If you plan to install this firmware concurrently, it will require two firmware updates:
1 - Install system firmware level EL320_046.
2 - Then, install system firmware level EL320_076.

Note: Both service packs, EL320_046 and EL320_076, contain a HIPER fix to correct a service processor communications hang which could result in a system checkstop. If you are unable to update your firmware to the latest level (EL320_076), Product Engineering recommends that you minimally install the EL320_046 level to obtain the HIPER fix.

2.0 Important Information

HMC-Managed Systems

Systems may continue to use HMC code Version 7, Release 3.2. If you choose to upgrade to Version 7, Release 3.3.0, you will have to install MH01119 before attempting to load this system firmware on your server.

For information concerning HMC releases and to access the HMC code packages, go to the following URL: http://www14.software.ibm.com/webapp/set2/sas/f/hmc/home.html

NOTE: You must be logged in as hscroot in order for the firmware installation to complete correctly.

Support for EnergyScale^tm and Active Energy Manager^tm

For more information on the energy management features now available, please see the EnergyScale^tmwhite paper.

Signal Cable in an InfiniBand loop, and InfiniBand I/0 drawer power on/off

The problems noted in this section in earlier levels of this description file were corrected in the EL320_059 firmware level by the last two fixes in the "affects certain systems" section.

Concurrent Firmware Updates

Concurrent system firmware update is only supported on HMC-Managed Systems only.

Memory Considerations for Firmware Upgrades

The increase in memory used by the firmware is due to the additional functionality in later firmware releases.

Systems Not Managed by an HMC

Instructions for installing firmware on systems that are not managed by an HMC can be found at http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/ipha5/fix_serv_firm_kick.htm

3.0 Firmware Information and Description

Use the following example as a reference to determine whether your installation will be concurrent or disruptive.

Note: The file names and service pack levels used in the examples are for clarification only, and are not
necessarily levels that have been, or will be released.

An installation is disruptive if:

The release levels (XXX) are different.

Example: Currently installed release is EL320, new release is EL330

The service pack level (YYY) and the last disruptive service pack level (ZZZ) are equal.

Example: EL320_120_120 is disruptive, no matter what level of EL320 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 EL320_120_120 and
new service pack is EL320_152_130

An installation is concurrent if:

The service pack level (YYY) is higher than the service pack level currently installed on your system.

Example: Currently installed service pack is EL320_126_120,
new service pack is EL320_143_120.

System firmware file naming convention:

01ELXXX_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, 01EL320_067_045 and 01EL330_067_053 are different service packs.

Firmware Information and Update Description


*Filename*	*Size*	*Checksum*
01EL320_046_031.rpm	21707691	62770

EL320
EL320_046_031 06/09/08	Impact: Serviceability Severity: HIPER HIPER: A problem was fixed that caused a concurrent firmware installation to hang with SRC BA00E840 being logged. This problem may also cause a partition migration to hang, under certain circumstances, with the same SRC, BA00E840, being logged. This SRC will be logged when this level of firmware is installed and will generate a call home; it should be ignored. It will not be logged during subsequent installations.
EL320_040_031 02/29/08	8204-E8A Impact: Serviceability Severity: Special Attention 8203-E4A Impact: New Severity: New New Features and Functions: Support for the 8203-E4A system was added. Fixes that affect all model E8A systems: DEFERRED: A problem was fixed that caused a system crash (with SRC B131E504) by changing the initialization settings of the I/O control hardware. A problem was fixed that, under certain circumstances, caused the InfiniBand adapter to stop responding to InfiniBand requests. A problem was fixed that caused SRC B1813014 to be logged after a successful system firmware installation. This SRC will be logged when this level of firmware is installed and will generate a call home; it should be ignored. It will not be logged during subsequent installations. System firmware changes that affect certain model E8A systems: On systems with a 1519-100 tower attached, a problem was fixed that caused the location code of a connector on the integrated virtual IOP to be displayed as Un-SE1-SE1-T1 instead of Un-SE1-T1. On systems with 7134-G30 I/O drawers attached in certain cabling configurations, a problem was fixed that prevented the I/O port labels from being displayed for the port location codes on the hardware topology screens. On systems running system firmware level EL320_031, a problem was fixed that caused attempts to call home to fail. On systems running the Active Energy Manager^tm, a problem was fixed that caused the Exhaust Heat Index (EHI) to read up to 21 degrees lower than the actual exhaust air temperature.
EL320_031_031 02/08/08	8204-E8A Impact: New Severity: New 8203-E4A not supported at this level Features and Functions: Support for the creation of multiple virtual shared processor pools (VSPPs) within the one physical pool. (In order for AIX performance tools to report the correct information on systems configured with multiple shared processor pools, a minimum of AIX 5.3 TL07 or AIX 6.1 must be running.) Support for the "hyperboot" boot speed option in the power on/off menu on the Advanced System Management interface (ASMI). Support for the capability to move a running AIX or Linux partition from one system to another compatible system with a minimum of disruption. Support for the collection of extended I/O device information (independent of the presence of an operating system) when a system is first connected to an HMC and is still in the manufacturing default state. Support for EnergyScale^tm and Active Energy Manager^tm. For more information on the energy management features now available, please see the EnergyScale^tmwhite paper . Note 1: The lowest power cap that Active Energy Manager^tm will allow the user to set is below the power value that can be guaranteed. To avoid error conditions, set the power cap above the power used by the system at maximum load. See the EnergyScale^tm white paper at the link above for more information on how to set the power cap. Note 2: The Exhaust Heat Index (EHI), as shown on Active Energy Manager^tm, may read up to 21 degrees lower than the actual exhaust air temperature.

4.0 How to Determine Currently Installed Firmware Levels

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

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

Where XXX = release level

If the release level will stay the same (Example: Level EL320_075_075 is currently installed and you are attempting to install level EL320_081_075) this is considered an update.
If the release level will change (Example: Level EL320_081_075 is currently installed and you are attempting to install level EL330_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/updateschapter.htm

7.0 Change History

Date	Description
Dec 02, 2008	Revised the link in Section 2.0 for updating and upgrading firmware without and HMC. Revised the link in Section 6.0 for updating and upgrading firmware with HMC.
Sep 29, 2008	- Updated HMC information from MH01105 to MH01119 in Section 2.0. - Revised pointer to instructions for installing firmware on systems not managed by an HMC. - Revised information in fixlist to emphasize that EL320_031 is not supported on 8203-E4A systems.
Jul 02, 2008	Change to Section 2.0: - Added a pointer to instructions for installing firmware on systems not managed by an HMC.
Jun 24, 2008	Changes to Section 2.0: - Revised information pertaining to HMC Managed Systems. - Added information concerning Concurrent firmware Updates.