IBM eServer
PCIe2 1.8GB Cache RAID SAS Adapter Tri-port 6Gb (CCIN 57B5)

PCIe2 3.1GB Cache RAID SAS Enclosure 6Gb x8 (CCIN 57C3)

PCIe2 RAID SAS Adapter Dual-port 6Gb (57C4)

 

 DATE:  Jun 27, 2012

Table of Contents

1.0 Microcode Change History

2.0 General Information
2.1 Installation Time
2.2 Machine's Affected
2.3 AIX Requirements
2.4 Linux Requirements

2.5 IBM i Requirements

3.0 Determine the Current Microcode Level for AIX
3.1 Determine the Current Microcode Level for Linux

4.0 Downloading and Unpacking the Firmware Update Package from CORE
4.1 Downloading the RPM Format File to the Target Server
4.2 Microcode Update via CD

5.0 Verifying microcode before download and notes
5.1 Microcode Download Procedure-57B5 SAS Adapters for AIX
5.2 Microcode Download Procedure-57B5 SAS Adapters for Linux

6.0 Microcode Readme Change History

=====================================================================================

1.0 Microcode Change History:

 

0150009a -GA level for CCIN 57C3, 57C4
-HIPER: Fix for UECC error which can cause the F/W cache to become disabled.
-Significant performance enhancements for RAID-5 and mirroring configurations
-General device error recovery enhancements in a Dual Storage IOA Configuration to prevent certain cases of IOASC 0108000, 0408000, 04448400
-Fixes for certain Watchdog Timeout errors
-PRC 04440000, DMGR logging failure for Abort Task Set TMF
Enhanced error recovery
-Properly log device failure error prior to reset for switchover on Secondary. Error reporting enhancements to log necessary errors for
certain device failures in a Dual Storage IOA Configuration
-Queue Full mitigation
-Fixes for Adapter Reset/Reload IOASC 04448200, 04448400
   - PRC 80FF0300, TMF processing could get out of sync if a device goes not connected when a TMF is outstanding)
   - Lost ops due to bridge handling cause soft cmd timeouts
   - PRC 80FF0300, double unit check processing command timeout
   - Incorrect WWID being obtained at IPL for remote IOA
   - PRC 80FF0300, when logging T10 errors with single index mode instead of a page table list
   - Certain cases of a drive failure within a RAID array in a Dual Storage Controller configuration
   - Array Manager is taking too long to update footprints when doing switchover for large arrays. Possible host timeout due to extended error recovery time with large RAID arrays
   - PRC 10013082, IE Leak. Incorrect memory resource management in the adapter may result in lack of available control store elements
01500090 - Level 0150008d + 1 Additional fix for 04448200/15212205 Battery Errors.
0150008d Fixes:
-SAS I/O adapter enhancements during error recovery to prevent a very slight chance of undetected data corruption.
-Adapter Unit Check (04448400) for
    *Incorrect abort request handling
    *Loss of access to System Enclosure Services
-Incorrect error logging when corrupted parity is detected in a RAID-6 array may prevent 06698200 from being surfaced
-General error recovery enhancements to prevent certain Temporary Error Conditions (FFFE). These may have surfaced as VRSAS_ERR21T
-Stopping multiple RAID-5 or RAID-6 arrays at the same time may result in 04448400 (IBM i only)

Performance Enhancements:
-Enhancements to performance information reported by the adapter.
-Possible performance impact with certain sequential workloads to Solid State Devices and may result in extended IPL time.

Prerequisite
- Prerequisite for FC 5913 and FC 5887 in Mode 2 configurations
01500087 -01500087 contains all the fixes in 01500084 plus an additional fix for the below issue:
Fix to prevent Adapter Unit Check if device reports back a maxLBA > 32 bits or an unexpected maxLBA of 0 in Read Capacity. The fix will now correctly fail the device.
01500084 -01500084 contains all the fixes in 01500080 plus an additional fix for the below issue:
Fixed undetected Data Corruption condition found in IBM i environment
      -No exposure in Dual Controller (cached) mode
      -Exposure only with 01500080 code
      -Exposure only if running in non-cached mode.
01500080 Fixes for
-04448400 conditions
    -Unique drive failure mode where the drive recovers after failing
    -Stopping multiple RAID arrays (IBM I only) simultaneously
-SRC B6005120
    -Insufficient adapter resources may lead to command timeouts resulting in reset/reload of the adapter
-Potential system hang due to incorrect timing on Dual Storage IOA link
-Possible command timeout under intensive write workload Error logging enhancements
0150007a -GA Level for CCIN 57B5.
-01500077 + 2 fixes
1) Possible cache data store clearing at IPL due to am improper setting in the "allowed resets" bit in DRAM Controller (very low probabilit
2) Enhanced error data when logging battery errors
01500077 May exist on some CCIN 57B5 adapters.  Any adapters at this level should be updated to 0150007a or beyond ASAP
 

2.0 General information

This subject microcode is to be used on the following SAS Adapter/controller types:
 

CCIN 57B5: PCIe2 1.8GB Cache RAID SAS Adapter Tri-port 6Gb

CCIN 57C3: PCIe2 3.1GB Cache RAID SAS Enclosure 6Gb x8
CCIN 57C4: PCIe2 RAID SAS Adapter Dual-port 6Gb

 

2.1 Installation Time:
Approximately 30 minutes
 
2.2 Machine's Affected:

57B5

8202-E4B, E4C

8205-E6B, E6C

8231-E2C

8233-E8B

9117-MMB, MMC

9119-FHB

9179-MHB, MHC

 

2.3 AIX Requirements:
TL refers to Technology Level

SP refers to Service Pack

 

57B5

6.1 TL3 SP10
6.1 TL4 SP10
6.1 TL5 SP6
6.1 TL6 SP5
6.1 TL7
7.1 TL0 SP3
7.1 TL1

or above

 

57C3 & 57C4

6.1 TL5 SP8
6.1 TL6 SP7
6.1 TL7 SP4
7.1 TL0 SP5
7.1 TL1 SP4

or above

 

2.4 Linux Requirements:

57B5 & 57C4

Red Hat Enterprise Linux 5.7 for POWER, or later
Red Hat Enterprise Linux 6.1 for POWER, or later
Novel SUSE Linux Enterprise 10, Service Pack 4, or later
Novel SUSE Linux Enterprise 11 Service Pack 1, or later

 

57C3

Red Hat Enterprise Linux 5.8 for POWER, or later
Red Hat Enterprise Linux 6.2 for POWER, or later
Novel SUSE Linux Enterprise 11 Service Pack 2, or later

 

2.5 IBM i Requirements:

57B5 & 57C4

IBM i 7.1 (& applicable PTFs), or later
IBM i 6.1 with 6.1.1 machine code 6.1.1  (& applicable PTFs) or later

 

57C3

Not supported on IBM i

 

 

3.0 Determine the Current Microcode Level for AIX:

Before you install the microcode, it is important to determine the microcode level of the Adapter installed in the target system. Use

the following instructions to read the ROM level stored in the Adapter's VPD.

1)  List the SAS RAID Adapters installed in the system by typing:

    lsdev -C | grep sissas

Note: All of the SAS RAID initiators addresses that are installed will be displayed. The names will be sissasX, where X is 0, 1, etc.

2) To check the current microcode level for the adapter or controller enter the following command

   lscfg -vl sissasX

Where X is the number/s of the previous command. The Command will produce output similar to

 

Example show for CCIN 57B5

DEVICE   LOCATION                                     DESCRIPTION

sissas1 U78C0.001.DBJ0102-P2-C4-T1 PCIe2 1.8GB Cache RAID SAS Adapter Tri-port 6Gb

PCIe2 1.8GB Cache RAID SAS Adapter Tri-port 6Gb :
Part Number.................74Y7759
FRU Number..................74Y7759
Serial Number...............YL30JH116130
Manufacture ID..............00JH
EC Level....................0
ROM Level.(alterable).......01500077
Customer Card ID Number.....57B5
Product Specific.(Z1).......1
Product Specific.(Z2).......2D20
Hardware Location Code......U78C0.001.DBJ0102-P2-C4-T1

 

If the ROM Level is less than 0150009a then you should update the microcode.

 

3.1 Determine the Current Microcode Level for Linux:
1) Type "iprconfig"
2) Select "Display hardware status"
3) Select SAS adapter by typing a "1" in front of it and pressing Enter.
4) The Command will produce output similar to
"Firmware Version . . . . . . . . . . . . : 01500077"

If the Firmware Version is less than 0150009a then you should update the microcode.

4.0 Downloading and Unpacking the Firmware Update Package from CORE

NOTE:  The CORE image will now be the RPM Format File.

1) After downloading the files from CORE on to your personal system find the following files in the CORE destination directory (c:\ibmdocs\DISKIMG):
    A) "pci.1014033d.50-0150009a-1.aix6.1.noarch.rpm"
    B) "pci.1014033d.50-0150009a-1.Linux.noarch.rpm"
2) Log in to the Target Server
3) Create a directory, if not already existent (mkdir /tmp/microcode; mkdir /tmp/microcode/RPM)
4) Transfer the file to the Target Server "/tmp/microcode/RPM directory" using ftp or another method.  Change to that directory, "cd /tmp/microcode/RPM".
5a) For AIX/Linux:  Unpack the RPM file by using the following command:  "rpm -ihv --ignoreos --force pci.1014033d.50-0150009a-1.aix6.1.noarch.rpm"
5b) For Linux:  Unpack the RPM file by using the following command:  "rpm -ihv --ignoreos --force pci.1014033d.50-0150009a-1.Linux.noarch.rpm"
6a) For the AIX rpm file:  The microcode files will be added to /usr/lib/microcode/.
6b) For the Linux rpm file:  The microcode files will be added to /lib/firmware/.

4.1 Downloading the RPM Format File to the Target Server
Use this method to download to an AIX or Linux system:

Note: The instructions that follow are specific AIX/Linux commands. AIX/Linux commands are CASE (lower and upper) SENSITIVE, and must be entered exactly as shown, including filenames.

1) Make a directory on an AIX/Linux system to receive the RPM format file.

    Enter: "mkdir /tmp/microcode"
    Enter: "mkdir /tmp/microcode/RPM"
2) Transfer the RPM format file to the /tmp/microcode/RPM directory (using "Save as ...").  Change to that directory, "cd /tmp/microcode/RPM".

You'll see the filenames for the RPM files.
    A) For AIX/Linux:  The filename is pci.1014033d.50-0150009a-1.aix6.1.noarch.rpm
    B) For Linux:  The filename is pci.1014033d.50-0150009a-1.Linux.noarch.rpm
3) Unpack the file by executing the instructions below:
    A) For AIX/Linux:  Type "rpm -ihv --ignoreos --force pci.1014033d.50-0150009a-1.aix6.1.noarch.rpm"
    B) For Linux:  Type "rpm -ihv --ignoreos --force pci.1014033d.50-0150009a-1.Linux.noarch.rpm"
4a) For AIX rpm file:  The microcode files will be added to /usr/lib/microcode/.
4b) For Linux rpm file:  The microcode files will be added to /lib/firmware/.
 

4.2 Microcode Update via CD

Below are references and the general flow on how to update microcode update via CD
1) Boot the system via a Standalone Diagnostic's CD
b) To create a bootable Diagnostic's CD go to the following URL.
Burn cdlatest.iso on to a CD-R (or CD-RW). Currently, DVD media cannot be utilized.
http://www14.software.ibm.com/webapp/set2/sas/f/diags/home.html
c) After booting to Standalone Diagnostics, the Diagnostic's CD can be removed.

2) The Diagnostic's CD should be replaced by a CD containing the unpacked microcode image(s).
The CD containing the microcode images should be prepared prior. This can be done by taking the rpm file(s) from the microcode download site and unpacking them on a usable server. The unpacked files can then be burned on to the CD media.
b) Another method is to use a Microcode Update CD
See the below website for more details
http://www14.software.ibm.com/webapp/set2/firmware/lgjsn?mode=10&page=cdrom.html#downloadcdrom

The Microcode Update CD and Discovery Tool can also be ordered through the following link
http://www14.software.ibm.com/webapp/set2/firmware/lgjsn?mode=10&page=compare.html&title=Microcode%20Survey%20and%20update%20tool

5.0 Verifying microcode before download and notes

NOTE: Microcode download must be performed separately for each Adapter bus under distinct Logical Partitions (LPAR's).
              Please save current and older versions of the microcode update files in case you need to restore your system.

NOTE: Microcode Download CAN be performed concurrently.

Installation Time:  Approximately 30 min System Time.

Please verify the file size and checksum of the raw microcode files matches the below.
Filesize:  2255960
Checksum:  61165
For AIX/Linux:  "ls -l /usr/lib/microcode/53495350.0150009a" to verify Filesize. 
                "sum /usr/lib/microcode/53495350.0150009a" to verify Checksum.
For Linux:  "ls -l /lib/firmware/pci.1014033d.50.0150009a" to verify Filesize.
                 "sum /lib/firmware/pci.1014033d.50.0150009a" to verify Checksum.

For systems that have LPAR installed, the microcode file must be placed on all partitions that have a SAS device in order to update the code.  Follow this procedure for each partition:

For AIX/Linux:
    A)  Log into the target partition.
    B)  Type: "cd /usr/lib/microcode"
    C)  FTP (for AIX) or SFTP (for Linux) to the partition that has the media bay assigned. (ie.  ftp/sftp partition1.ibm.com)
    D)  Type: "cd /usr/lib/microcode"
    E)  If using FTP then Type: "bin"
    F)  Type: "get 53495350.0150009a"
    G)  Type: "quit"

For Linux:
    A)  Log into the target partition.
    B)  Type: "cd /lib/firmware"
    C)  SFTP to the partition that has the media bay assigned. (ie.  "sftp partition1.ibm.com")
    D)  Type: "cd /lib/firmware"
    E)  Type: "get pci.1014033d.50.0150009a"
    F)  Type: "quit"

5.1 Microcode Download Procedure-57B5 SAS Adapters for AIX

Procedure:
1) It is advised, but not necessary to stop all applications.
2) Enter diag
3) Select the "Task Selection" from diagnostics menu.
4) Select "Download Microcode" or "Microcode Tasks -> Download Microcode" from "Task Selection" menu.
5) Select all of the SAS Adapters/Controllers that need to be updated from the list of devices by pressing "Enter".  The devices will be displayed as sissas#, where # is the number of the device.  Press "F7".
6) A dialogue box will be displayed on screen.  Press "Enter" to continue.
7) Select "/usr/lib/microcode".
8) A dialogue box will may be displayed on screen.  It will state that the current microcode level on the adapter is not in the /usr/lib/microcode directory.  This is acceptable as you will be flashing new microcode onto the adapter.  Also, incorrect code will automatically be rejected.  Press "Enter" to continue.
9) An "M" will be displayed next to the latest level of microcode in the /usr/lib/microcode directory.  Select that level and press "Enter".
10) The following message will appear on the screen when download is completed: "Microcode download complete successfully.  The current microcode level for the device sissas# is .....  Please run diagnostics on the adapter to ensure that it is functioning properly."  DO NOT run diagnostics on the device at this time.
11) Exit diagnostics.
12) Verify the code level is 0150009a by typing "lscfg -vl sissas#" for each SAS device updated. <Where # is the number sissas device>

5.2 Microcode Download Procedure-57B5 SAS Adapters for Linux

Procedure:
1) Stop all applications.
2) Type "iprconfig" and press "Enter".
3) Select "Download Microcode" and press "Enter".
4) Select all of the SAS Adapters/Controllers  that need to be updated from the list of devices by pressing "1". Then press "Enter".
5) Select the appropriate microcode image to flash by pressing "1".  (The image will end in 0150009a).  Press Enter.  Press Enter again to confirm.
6) If multiple devices were selected in step 4, then repeat step 5 until finished.

6.0 Microcode Readme Change History

2012-06-27 -Added UECC error to 0150009a microcode details
2012-06-04 -Added microcode level 0150009a
2012-04-04 -Added microcode level 01500090
2012-03-14 -Added microcode level 0150008d
2012-02-12 -Added microcode level 01500087
2011-12-08 -Added microcode level 01500084
2011-11-16 -Added microcode level 01500080
2011-10-21 -First Readme File for microcode level 0150007a