Power7 High-End Power Subsystem Firmware

Applies to:  9119-FHB

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 795 (9119-FHB)  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  R7.6.0.

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.


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:

     02ABXXX_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, 02AB720_067_045 and 02AB730_067_053 are different
service packs.

An installation is disruptive if:

              Example:  Currently installed release is AB720, new release is AB730                Example:  AB720_061_061 is disruptive, no matter what level of AB720  is currently
                                   installed on the system                  Example:  Currently installed service pack is AB720_120_120 and
                                     new service pack is AB720_152_130

An installation is concurrent if:

              Example: Currently installed service pack  is AB720_061_061,
                                 new service pack is AB720_070_061.
 

Firmware Information and Update Description

 
Filename Size Checksum
02AB760_079_043.rpm 19,072,198 04188
 
AB760_079_043 /
FW760.41

06/24/2014
 

Impact:  Security        Severity:  HIPER

Changes:
  • HIPER /Pervasive A security problem was fixed in the OpenSSL (Secure Socket Layer) protocol that allowed clients and servers, via a specially crafted handshake packet, to use weak keying material for communication. A man-in-the-middle attacker could use this flaw to decrypt and modify traffic between the management console and the service processor. The Common Vulnerabilities and Exposures issue number for this problem is CVE-2014-0224.
  • HIPER /Pervasive A security problem was fixed in OpenSSL for a buffer overflow in the Datagram Transport Layer Security (DTLS) when handling invalid DTLS packet fragments. This could be used to execute arbitrary code on the service processor. The Common Vulnerabilities and Exposures issue number for this problem is CVE-2014-0195.
  • HIPER /Pervasive Multiple security problems were fixed in the way that OpenSSL handled read and write buffers when the SSL_MODE_RELEASE_BUFFERS mode was enabled to prevent denial of service. These could cause the service processor to reset or unexpectedly drop connections to the management console when processing certain SSL commands. The Common Vulnerabilities and Exposures issue numbers for these problems are CVE-2010-5298 and CVE-2014-0198.
  • HIPER /Pervasive A security problem was fixed in OpenSSL to prevent a denial of service when handling certain Datagram Transport Layer Security (DTLS) ServerHello requests. A specially crafted DTLS handshake packet could cause the service processor to reset. The Common Vulnerabilities and Exposures issue number for this problem is CVE-2014-0221.
  • HIPER /Pervasive A security problem was fixed in OpenSSL to prevent a denial of service by using an exploit of a null pointer de-reference during anonymous Elliptic Curve Diffie Hellman (ECDH) key exchange. A specially crafted handshake packet could cause the service processor to reset. The Common Vulnerabilities and Exposures issue number for this problem is CVE-2014-3470.

AB760_072_043 /
FW760.40

01/20/2014
 

Impact:  Availability        Severity:  SPE

Changes:
  • Frame input power information is not correctly returned to the HMC for the second line cord when there are 3 BPRs per BPA
  • Fix to no longer recover DCA power for internal hardware resets if CEC node is critical (powered off from fault). This allows normal SRC to be posted to improve servicability.
  • Fix location codes used in part callouts for SRCs 1402328C and 1402328B
  • Fix to allow servicing of a DCA in a CEC that is already in Low Power Mode if the HMC sends commands to BPA side B
  • Fix to prevent erroneous posting of DCA to DCA communication faults during code updates
  • Fix to prevent system level power off if a critical CEC node fault independently occurs before or during concurrent BPA service

AB760_066_043 /
FW760.30

06/24/2013
 

Impact:  Availability        Severity:  SPE

Changes:
  • Post error code if BPC bypass switch is left in bypass position after service
  • Fix cross-power cable's circuit breaker not being opened as part of BPC service when mailbox cable is broken
  • Detect and block service of power supplies that have been left in voltage biased down condition
  • Allow service procedure to continue if CEC node being serviced for power supply repair is already in Low Power Mode from a prior repair
  • Add tests to detect and report a dead voltage level 6 on 5797/5798 I/O drawers
  • Fix to prevent erroneous defective planar error posted after power off of 5797/5798 I/O drawer
  • Robustness added to various hardware recovery processes

AB760_055_043 /
FW760.20

02/26/2013
 

Impact:  Availability        Severity:  SPE

Changes:
  • When a BPA error condition is detected, BPA fan speeds will be raised to a lower setting than the previous firmware level.

AB760_043_043

11/23/2012
 

Impact:  New        Severity:  NEW

Changes:
  • 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:  AB720_061.

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: ABXXX_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/updateschapter.htm