Power6 High-End Power Subsystem Firmware

Applies to:  9125-F2A

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 575 (9125-F2A)  Servers only.  Do not use on any other systems.
 

The firmware level in this package is:


2.0 Important Information

HMC-Managed Systems

This firmware level requires  HMC V7  R3.3.0  with MH01119 and MH01130.

Go to the following URL to access the HMC code packages:

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

Attention:  9125-F2A servers should be evaluated for ECA845 installation prior to performing firmware upgrades.  Contact your service provider for more information about ECA845.   If firmware must be upgraded prior to the installation of ECA845, use the following special instructions:

 Firmware installations should be performed on an entire managed frame, and all managed systems
housed in that frame, at one time.  The following instructions can be used to install firmware on
one managed frame and all of the managed systems that it houses.  The instructions can be
repeated as many times as needed until all firmware has been installed on all managed frames.

1) Power off all managed 9125-F2A systems in the managed frame.

2) Reinstall the current system firmware level on all managed systems in the managed frame:

   The following command can be used to determine the current firmware level:

      lslic -t sys -m <managedsystem_1> -F activated_level

   The following command will retrieve and reinstall the current firmware level on
   one managed system:

      updlic -o a -m <managedsystem_1> -t sys -l <current_fsp_level> -r <repos>

      <current_fsp_level> is the level determined with the lslic command.

      <repos> is the location of the firmware such as "-r dvd", "-r ibmwebsite", etc.
      Additional parameters might be required, depending on the repository selection.
      If the firmware has already been copied onto the HMC, the HMC hard drive (-r disk)
      should be used as the repository.

   After the firmware has been copied onto the HMC, the HMC hard drive (-r disk) should
   be used as the repository to update the remaining managed systems:

      updlic -o a -m <managedsystem_2> -t sys -l <current_fsp_level> -r disk
      updlic -o a -m <managedsystem_3> -t sys -l <current_fsp_level> -r disk
      ......
      updlic -o a -m <managedsystem_N> -t sys -l <current_fsp_level> -r disk

   These commands can be run in the background in parallel to speed up the installation of
   the firmware.

   Wait for all updlic commands to complete before proceeding to step 3.

3) Install and activate new bulk power controller (BPC) firmware only.  During this step, the
   managed systems will transition from "Power Off" to "No Connection", and then back to "Power
   Off".

   Select one managed system as the target of the updlic command and update the BPC firmware.
   The following command will retrieve firmware from the repository and update the BPCs:

      updlic -o a -m <managedsystem_1> -t power -l latest -r <repos> .....

      <repos> is the location of the firmware such as "-r dvd", "-r ibmwebsite", etc.
      Additional parameters might be required, depending on the repository selection.
      If the firmware has already been copied onto the HMC, the HMC hard drive (-r disk)
      should be used as the repository.

4) Wait for all managed systems to return to "Power Off" state.

5) Cycle the managed frame's UEPO switch by doing the following:
     1.  Turn the red switch off.
     2.  Wait one minute.
     3.  Turn the red switch back on.

6) Wait for the managed frame to return to the "Standby/Standby" state

7) Install and activate new firmware on all managed systems in the managed frame.

      updlic -o a -m <managedsystem_1> -t sys -l latest -r <repos> .....

      <repos> is the location of the firmware such as "-r dvd", "-r ibmwebsite", etc.
      Additional parameters might be required, depending on the repository selection.
      If the firmware has already been copied onto the HMC, the HMC hard drive (-r disk)
      should be used as the repository.

   After the firmware has been copied onto the HMC, the HMC hard drive (-r disk) should
   be used as the repository to update the remaining managed systems:

      updlic -o a -m <managedsystem_2> -t sys -l latest -r disk
      updlic -o a -m <managedsystem_3> -t sys -l latest -r disk
      ......
      updlic -o a -m <managedsystem_N> -t sys -l latest -r disk

   These commands can be run in the background in parallel to speed up the installation of
   the firmware.

   Wait for all updlic commands to complete before proceeding to step 8.

8) Power on the managed systems.
 


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 following examples are for clarification only, and are not
             necessarily levels that have been, or will be released.

Power Subsystem firmware file naming convention:

     02EPXXX_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, 02EP330_067_045 and 02EP340_067_053 are different
service packs.

An installation is disruptive if:

              Example:  Currently installed release is EP330, new release is EP340                Example:  EP330_120_120 is disruptive, no matter what level of EP330  is currently
                                   installed on the system                  Example:  Currently installed service pack is EP330_120_120 and
                                     new service pack is EP330_152_130

An installation is concurrent if:

              Example: Currently installed service pack  is EP330_126_120,
                                 new service pack is EP330_143_120.
 

Firmware Information and Update Description

 
Filename Size Checksum
02EP330_057_029.rpm 17,972,390 54013
 
EP330_057_029

10/20/08
 

Impact:  Function        Severity:  Hiper
  • Service Pack 2++
    • Corrects a problem that causes all nodes in the frame to transition into 'Low Power Mode' where all nodes will run at reduced performance
EP330_054_029

09/22/08
 

Impact:  Function        Severity:  Hiper
  • Service Pack 2+
    • Corrects a problem introduced in BPC level EP330_049 that could result in SRCs 11008720 /21 being generated. If level EP330_049 is installed, IBM recommends you install this level (EP330_054) as soon as possible
EP330_049_029

08/28/08
 

Impact:  Function        Severity:  Hiper
  • Service Pack 2
    • Fix for intermittent false Logic Temperature Sensor SRCs
    • Fix for code update failures to I/O power supplies
    • Fix for false power supply SRCs during concurrent firmware update
    • Fix for the hardware management console (HMC) getting stuck at "Pending Authentication" for the rear Bulk Power Controller (BPC)
    • Updates to cable error logging
    • Change to prevent 11008710/11008711 SRCs during code update to an IH DCA (power supply)
    • Updates to error logging to add a secondary FRU to the list of possible failing hardware
    • Fix for false SRCs while servicing a Cross-Power Cable
    • Fix for posting a defective power supply SRC when the fault was a defective fan
    • Support for posting high/low room temperature SRCs and improved handling of high logic temperature
    • Fix for internal communication problems in power supplies
    • Support for low power mode on Air-cooled IH systems
    • Fix for a missing FRU call-out in some MWU (Modular Water Unit) SRCs
    • Fix for reversed cable descriptions in power supply SRCs
    • Fix for code updates to MWUs (Modular Water Units)
    • Fix for false SRCs during power supply code update
    • Improved handling of code update of fans and Bulk Power Regulators (BPRs)
    • Fix for code update failing to run on both Bulk Power Controllers (BPCs)
    • Fix for failure to power on I/O drawers
    • Fix for Bulk Power Regulators (BPRs) not recovering properly after line cord removal/replacement
    • Update to Health Check behavior to prevent HSCF0168E error
    • Fix for false 14010135 SRC
    • Fix for false 14012051/14012052 SRCs
    • Improvement to prevent water flow oscillations in Modular Water Units (MWUs)
    • Improved handling of water level sensors in Modular Water Units (MWUs)
    • Improvements to the Fill and Drain Tool
EP330_029_029

06/10/08
 

Impact:  Function        Severity:  Hiper
  • Service Pack 1
    • BPC to BPC communication enhancements
    • BPF Fan speed setpoint changes
    • Fix for false B1868C59 reference codes
    • Change to memory throttling initiation point
    • Fix for false 14017195 reference code when UEPO cable is disconnected
    • Fixes for wrong/missing FRUs in PEL logs
    • Fixes for problems during code download of power FRUs
    • Fix for missing I/O drawer after BPC reset or BPC code update
    • Fix for occasional slow BPC performance
    • Change to prevent exit from Power Save if power supply fails while in Power Save
    • Support for new 8.8KW BPR
    • Improved handling of VRM failures in power supplies
    • Fix to prevent loss of I/O drawer VPD data during replacement of I/O power supplies
    • Improvements to the CEC power supply balancing function
    • Change to shift load to the rear BPRs if front BPF fan fails
    • Support for concurrent code update of 9125-F2A power supplies
EP330_017_017

05/13/08
 

Impact:  New        Severity:  New
  • GA Level


4.0 How to Determine Currently Installed Power Subsystem Firmware Levels

You can view the frame's current firmware level on the Advanced System Management Interface (ASMI) Welcome pane.  It appears in the top right corner.   Example:  EP330_029.

5.0 Downloading the Firmware Package

The firmware is located at the web site

       http://www14.software.ibm.com/webapp/set2/firmware/gjsn

Follow the instructions on this web page. You must read and agree to the license agreement to obtain the firmware packages.

In the drop-down box, choose the entry for your specific machine type and model.

You may download the individual .rpm and .xml files for Power Subsystem firmware from this location to your server, an ftp server, or a CD-ROM (both files are required).  Make sure the file names have the format 02EP3xx_yyy_zzz, with an extension of .rpm and .xml before copying them to your server, an ftp server or CD-ROM.  If using a CD-ROM, copy the .rpm and .xml files to the CD-ROM using a local CD-ROM burner utility.

Another method is to download the .iso file and create a CD-ROM to use with your HMC.

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

Where XXX =  release level

Instructions for installing firmware updates and upgrades can be found in the Operations Guide for the Hardware Management Console and Managed Systems, see Chapter 9. Updates, section Managed Systems Updates.

See Chapter 9. Updates, section Mangaged Systems Updates.


7.0 Change History

 
DATE Description
Jan 15, 2009 Revised instuctions in Section 2.0 concerning installing firmware.