Power7 Entry Systems Firmware

Applies to:   8202-E4B, 8205-E6B, 8231-E2B, 8233-E8B, 8236-E8C, 8492-DW2 and 8493-SV2

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-E2B), Power 730 (8231-E2B), Power 720 (8202-E4B), Power 740 (8205-E6B, 8492-DW2 and 8493-SV2), Power 750 (8233-E8B)  and Power 755 (8236-E8C) 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).

Although the Minimum HMC Code level for this firmware is listed above,  HMC level V7 R7.3.0 with PTF MH01313 (Service Pack 4) and PTF MH01320 (Fix for V7R7.3.4), 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.

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.

Although the Minimum SDMC Code level for this firmware is listed above, SDMC level V6.730 SP1 (MF53437), or higher is suggested for this firmware level.

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

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 or SDMC - Managed Systems only.

Changes to DIMM VPD reported under FW Release AL730, for select DIMMs

 After installation of AL730 firmware, select DIMMs may display VPD information that does not match the attached FRU label.  The FRU number displayed may differ from the FRU number printed on the DIMM label.
This change would not apply when the server is running an earlier supported release of system firmware (ex. AL710, or AL720).

Changes in VPD (Vital Product Data) May be Reported for Feature Codes 4526, 4529, and 4528
Feature Code Supported
Systems		 Description DIMM FRU Label Under FW Release AL730,
VPD is displayed as the following



FRU Number CCIN FRU Number CCIN
4526 8202-E4B
8205-E6B
8231-E2B
8233-E8B
8236-E8C
8492-DW2
8493-SV2

4GB Memory DIMM

 77P8784
 31C5
 78P0554
 31F3
4529 8202-E4B
8205-E6B
8492-DW2
8493-SV2

8GB Memory DIMM

 77P8919
 31D2
 78P0555
 31F4
4528 8233-E8B
8236-E8C

16GB Memory DIMM

 77P8633 31C9 78P0639 31F5
Note: This change does not apply to all DIMMs with the FRU numbers listed above, only a sub-set of DIMMs will report changes in VPD information.  The change in displayed VPD information has no functional impact and does not affect the operation or reliability of the associated memory DIMMs, it simply reports select DIMMs with new VPD information as a means of differentiating their capabilities to service providers.  Future service actions should be placed using the displayed VPD information, as logged by diagnostic and service related software, and not against the FRU number printed on the DIMM FRU label.


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/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 or SDMC, 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

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 01AL740_067_053 are different service packs.

An installation is disruptive if:

Example: Currently installed release is AL710, new release is AL720 Example: AL720_120_120 is disruptive, no matter what level of AL720 is currently installed on the system 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
01AL730_095_035.rpm 34969656 58702

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

AL730
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-Firmware-Hist.html
AL730_095_035

08/23/12		 Impact: Availability         Severity:  SPE

New Features and Functions

  • Support for booting the IBM i operating system from a USB tape drive.

System firmware changes that affect all systems

  • A problem was fixed that caused a partition with dedicated processors to hang with SRC  BA33xxxx when rebooted, after it was migrated using a Live Partition Mobility (LPM) operation from a system running Ax730 to a system running Ax740, or vice versa.
  • The firmware was enhanced to call out the correct field replaceable units (FRUs) when SRC B124E504 with description "Chnl init TO due to SN stuck in recovery" was logged.
  • A problem was fixed that caused SRC B1818A10 to be erroneously logged after a system firmware installation.
  • A problem was fixed that caused booting from a virtual fibre channel tape device to fail with SRC B2008105.
  • The firmware was enhanced to log SRCs BA180030 and BA180031 as informational instead of predictive.
  • A problem was fixed that caused a "code accept" during a concurrent firmware installation from the HMC to fail with SRC E302F85C.  This is most likely to occur on model FHB systems.
  • On systems running the AIX operating system, a problem was fixed that caused the hypervisor to crash with SRC B7000103, after an HEA (Host Ethernet Adapter) error was logged, when there is a lot of AIX activity on the HEAs.
  • A problem was fixed that caused the suspension of a partition to fail if a large amount of data has to be stored to resume the partition.
  • A problem was fixed that caused a system crash with unrecoverable SRC B7000103 with "ErFlightRecorder" in the failing stack.
  • On systems booting from an NPIV (N-port ID virtualization) device, a problem was fixed that caused the boot to intermittently terminate with the message "PReP-BOOT: unable to load full PReP image.".  This problem occurs more frequently on the IBM V7000 Storage System running the SAN Volume Controller (SVC), but not on every boot.
  • A problem was fixed that caused SRC B181E6F1 with the description "RMGR_PERSISTENT_EVENT_TIMEOUT" to be erroneously logged.
  • A problem was fixed that prevented a change to the system operating mode ("M" or "N") made in the Advanced System Management Interface (ASMI) menu from being displayed in the physical control (operator) panel.
  • A problem was fixed that caused a memory leak in the service processor firmware.
  • A problem was fixed that caused SRC B155A491 to be erroneously logged during multiple system IPLs.  This SRC may cause the system to terminate.
  • A problem was fixed that caused the default value for Field Core Override to be incorrect in the ASMI menus the first time the system is booted.
  • The ASMI menus were enhanced to more clearly indicate which processor cores were deconfigured by the Field Core Override (FCO) option (F/C 2319).
  • On 8202-E4B and 8205-E6B systems, the firmware was enhanced to call out a failing VRM, instead of the memory card on which the VRM is plugged, if the VRM fails when the system is booting.
  • On 8231-E2B systems, the firmware was enhanced to improve the service actions for SRC 11002691.
System firmware changes that affect certain systems
  • The firmware was enhanced to fix a potential performance degradation on systems utilizing the stride-N stream prefetch instructions dcbt (with TH=1011) or dcbtst (with TH=1011).  Typical applications executing these algorithms include High Performance Computing, data intensive applications exploiting streaming instruction prefetchs, and applications utilizing the Engineering and Scientific Subroutine Library (ESSL) 5.1.
  • On systems on which Internet Explorer (IE) is used to access the Advanced System Management Interface (ASMI) on the Hardware Management Console (HMC), a problem was fixed that caused IE to hang for about 10 minutes after saving changes to network parameters on the ASMI.
  • A problem was fixed that caused informational SRC A70047FF, which may indicate that the Anchor (VPD) card should be replaced, to be erroneously logged again after the Anchor card was replaced.
  • A problem was fixed that caused a network installation of IBM i to fail when the client was on the same subnet as the server.
  • On systems with a 5796 or 5797 I/O drawer attached, a problem was fixed that could cause a system hang.
  • On system managed by an HMC, a problem was fixed that caused the lsstat command on the HMC to display an erroneously high number of packets transmitted and received on a vlan interface.
  • On systems with a 7311 I/O drawer attached, a problem was fixed that caused a system boot to hang with C700406E.
  • On system managed by an HMC, a problem was fixed that caused the lsstat command on the HMC to display an erroneously high number of packets transmitted and received on a vlan interface.
  • On 8202-E4B and 8205-E6B systems with the feature code (F/C) 5610 or F/C 5685 PCI expansion riser installed, a multi-port communications adapter installed in a slot on the expansion riser, and that are managed by an HMC, a problem was fixed that prevented hardware discovery by the HMC of the communication adapter from completing.  This problem could also cause making a system plan to fail with SRC BA350000.
AL730_087_035

05/18/12		 Impact: Availability         Severity:  SPE

New Features and Functions

  • Support for IBM i Live Partition Mobility (LPM)

System firmware changes that affect all systems

  • A problem was fixed that prevented the user from changing the boot mode or keylock setting after a remote restart-capable partition is created, even after the partition's paging device is on-line.
System firmware changes that affect certain systems
  • The firmware resolves undetected N-mode stability problems and improves error reporting on the feature code (F/C) 5802 and 5877 I/O drawer power subsystem.
AL730_078_035

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

System firmware changes that affect all systems

  • The firmware was enhanced to properly display a memory controller that has been guarded out manually on the "Deconfiguration Records" menu option (under "System Service Aids") on the Advanced System Management Interface (ASMI).
  • A problem was fixed that caused multiple service processor dumps to be unnecessarily taken during a concurrent firmware update.  SRC B181EF9A, which indicates that the dump space on the service processor is full, was logged as a result.
  • The firmware was enhanced to increase the threshold for recoverable SRC B113E504 so that the processor core reporting the SRC is not guarded out.  This prevents unnecessary performance loss and the unnecessary replacement of processor modules.
  • A problem was fixed that caused SRC B7000602 to be erroneously logged at power on.
  • The firmware was enhanced to recognize new USB-attached devices so that they will be listed as boot devices in the System Management Services (SMS) menus.
  • A problem was fixed that caused booting or installing a partition or system from a USB device to fail with error code BA210012.  This usually occurs when an operating system (OS) other than the OS that is already on the partition or system is booted or installed.
  • 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.
  • The firmware was enhanced to log SRCs BA180030 and BA180031 as informational instead of predictive.
  • The firmware was enhanced to increase the threshold of soft NVRAM errors on the service processor to 32 before SRC B15xF109 is logged.  (Replacement of the service processor is recommended if more than one B15xF109 is logged per week.)
  • A problem was fixed that caused the internal PCI slot fault LEDs to erroneously turn on after AC power was removed, then reapplied.
System firmware changes that affect certain systems
  • HIPER/Non-pervasive:  On systems managed by a Hardware Management Console (HMC), and on which a concurrent system firmware update was done, a problem was fixed that caused the number of processors available on the managed system shown on the management console to be smaller than it should have been.
  • A problem was fixed that caused the hypervisor to hang during a concurrent operation on a F/C 5802, 5803, 5873 or 5877 I/O drawer.  Recovering from the hypervisor hang required a platform reboot.
  • A problem was fixed that impacted performance if profiling was enabled in one or more partitions.  Performance profiling is enabled:
     - In an AIX or VIOS partition using the tprof (-a, -b, -B, -E option) command or pmctl (-a, -E option) command.
     - In an IBM i partition when the PEX *TRACE profile (TPROF) collections or PEX *PROFILE collections are active.
     - In a Linux partition using the perf command, which is available in RHEL6 and SLES11; profiling with oprofile does not cause the problem.
  • A problem was fixed that prevented the operating system from being notified that a F/C 5802 or 5877 I/O drawer had recovered from an input power fault (SRC 10001512 or 10001522).
  • On a system that is being upgraded from Ax720 system firmware to Ax730 system firmware, the firmware was enhanced to log B1818A0F as informational instead of predictive if it occurs during the firmware upgrade.
  • On systems running Active Memory Sharing (AMS), the allocation of the memory was enhanced to improve performance.
  • A problem was fixed that caused the suspension of a logical partition running Active Memory Sharing (AMS) to fail because the disk headers had not been erased.
  • 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 Active Memory Sharing (AMS) and Active Memory Mirrorring (AMM), a problem was fixed that caused memory allocation to fail.  This in turn caused a partition to fail to boot with SRC A2009030.
  • On systems using the Advanced Energy Manager (AEM) to run in Dynamic Power Save (DPS) mode, and with deconfigured processor cores, a problem was fixed that caused the processor voltages to be set incorrectly, which in turn caused the system to use more power than it should have been using.
  • On systems managed by an HMC and using affinity groups, a problem was fixed that prevented one of the partitions from being placed correctly.
AL730_066_035

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

System firmware changes that affect certain systems

HIPER/Pervasive on systems with a Virtual Input/Output (VIO) client running AIX, and with a F/C 5802 or 5877 I/O drawer attached:  A problem was fixed that caused the system to crash with SRC B700F103.

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 SDMC managed systems:  From the SDMC Welcome page, select the desired server(s), then select Release Management, then select Power System Firmware Management. Click Gather Target Information, then view the current levels of the desired server(s). 
NOTE:  If Inventory has not previously been collected, a message will be displayed indicating to "View and Collect Inventory" to proceed.

For standalone system running IBM i without an HMC or SDMC: From a command line, issue DSPFMWSTS.

For standalone system running IBM AIX without an HMC or SDMC: 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 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: ALXXX_YYY_ZZZ

Where XXX = release level

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

SDMC Managed Systems:

Instructions for installing firmware updates and upgrades on systems managed by an SDMC can be found at:
http://publib.boulder.ibm.com/infocenter/director/v6r2x/index.jsp?topic=/dpsm/dpsm_managing_hosts/dpsm_managing_hosts_power_firmware.html

Systems not Managed by an HMC or SDMC:

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 AL730_095:
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 AL730_095:
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-Firmware-Hist.html