Power7 Mid-Range Systems Firmware

Applies to: 9117-MMB and 9179-MHB

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 770 (9117-MMB)  and Power 780 (9179-MHB)  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.1.0 (PTF MH01205 or MH01206) with PTF MH01237 (Service Pack 3).

Although the Minimum HMC Code level for this firmware is listed above,  HMC level V7 R7.1.0 Service Pack 4 (MH01258), 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 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.

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:
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/index.jsp?topic=/iphat_p5/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. 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:

01AMXXX_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, 01AM720_067_045 and 01AM740_067_053 are different service packs.

An installation is disruptive if:

Example: Currently installed release is AM710, new release is AM720 Example: AM720_120_120 is disruptive, no matter what level of AM720 is currently
installed on the system Example: Currently installed service pack is AM720_120_120 and new service pack is AM720_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 AM720_126_120,  new service pack is AM720_143_120.

Firmware Information and Update Description

 
Filename Size Checksum
01AM710_119_043.rpm 26569082
 38992

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 01AM710_119_043.rpm

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

12/07/11		 Impact:  Serviceability       Severity:  SPE

New Features and Functions

  • Support for F/C 5289, a full-height 2-port async EIA-232 PCIe adapter.
  • Support for F/C 5290, a low-profile 2-port async EIA-232 PCIe adapter.

System firmware changes that affect all systems

  • A problem was fixed that prevented a system dump from being off-loaded from the service processor.  When this occurred, additional dumps were not allowed.
  • The firmware was enhanced to log SRC B1768B76 as informational instead of unrecoverable.
  • The firmware was enhanced to log SRC B1812A11 as informational, instead of service action required, when the thermal/power management device (TPMD) is successfully reset.
  • A problem was fixed that caused the message "500 - Internal Server Error." to be displayed when a setting was changed on the Advanced System Management Interface's (ASMI's) power on/off menu, when the change was attempted when the system was powering down.
  • A problem was fixed that caused a system's partition dates to revert back to 1969 after the service processor or its battery was replaced.  This occurred regardless of whether or not the service processor's time-of-day (TOD) clock was correctly set during the service action.
  • The firmware was enhanced to call out an isolation procedures (FSPSP63) when SRC B160B73F is logged.
  • A problem was fixed that caused SRC B7005442 to be erroneously logged, and functional processor cores to be guarded out, when an error occurred in the operation system or an application.
  • A problem was fixed that caused a partition migration or partition hibernation operation to hang with the partition left in the "suspending" state.
  • The firmware was enhanced by the addition of a new option in the system management services (SMS) "Mutli-boot" menu that facilitates zoning of physical and virtual fibre channel adapters.
  • On the System Management Services (SMS) remote IPL (RIPL) menus, a problem was fixed that caused the SMS menu to continue to show that an Ethernet device is configured for iSCSI, even though the user has changed it to BOOTP.
  • On a multi-drawer system, a problem was fixed that prevented the system attention LED from correctly reflecting the status of the DASD fault LEDs in drawers 2, 3, and 4.
  • A problem was fixed that caused the wrong voltage regulator module (VRM) to be called out with SRC 11002630.
  • A problem was fixed that caused a firmware installation from the HMC with the "do not auto accept" option selected to fail.

System firmware changes that affect certain systems

  • On systems running VIOS, a problem was fixed that prevented virtual LANs (VLANs) in a VIOS with partition ID of 1 from being displayed as bootable devices in the system management services (SMS) menus.
  • On systems running Active Memory Sharing (AMS), a problem was fixed that caused a partition to crash with SRC B700F103 if the size of an AMS pool is reduced at the same time as an AMS partition is dynamically created, or an AMS partition's maximum memory is changed. 
  • On a system that terminates when in dynamic power save mode, a problem was fixed that caused SRCs B150B943, B113C660, and B113C661 to be erroneously logged when the system rebooted.
  • On partitions running Red Hat Linux 6.1, a problem was fixed that caused a partition migration operation to fail.
  • A problem was fixed that caused the installation of some versions of Linux to fail.
  • On systems running AIX, a problem was fixed that caused AIX to log an "INTERNAL ERROR CODE" against sysplanar0 after a partition migration operation from a POWER7 to a POWER6 system.
  • A problem was fixed that caused a partition migration operation to abort when the partition has more than 4096 virtual slots.
  • On systems running the Advanced Energy Manager (AEM), a problem was fixed that caused the work rate calculation for a processor to be incorrect if the system dropped into safe mode.
  • On systems running VIOS, a problem was fixed that caused the location code in the output of the "lsmap -npiv -all" command to be incorrect.
  • On systems running AIX partitions, a problem was fixed that caused the virtual memory manager in AIX to crash on the target system after the migration of a partition from a POWER6 system to a POWER7 system.
  • On systems on which a NIM installation is being set up using the system management services (SMS) menus, the firmware was changed to limit the packet size options to 512 and 1024 bytes.
  • On systems running iSCSI, a problem was fixed that caused the system to hang when booting from an iSCSI device in the system management services (SMS) menus.
  • On systems with an iSCSI network, when booting a logical partition using that iSCSI network, a problem was fixed that caused the iSCSI gateway parameter displayed on the screen to be incorrect.  It did not impact iSCSI boot functionality.
  • On systems running a virtual I/O (VIO) partition, or using a Shared Ethernet Adapter (SEA), a problem was fixed that caused a severe performance degradation.
  • On systems using Capacity on Demand (CoD), a problem was fixed that caused informational SRC B7005300 to be logged so often that the error logs wrapped, and other information in the error logs was lost.
  • On systems with more than one drawer, a problem was fixed that prevented the battery on the secondary service processor from being called out when it needed to be replaced.

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

Alternately, use the Advanced System Management Interface (ASMI) Welcome pane. The current server firmware  appears in the top right corner. Example: AM710_yyy.

5.0 Downloading the Firmware Package

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

Where XXX = release level

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

7.0 Firmware History

The Firmware History can be reviewed at the following url:

http://download.boulder.ibm.com/ibmdl/pub/software/server/firmware/AM-Firmware-Hist.html