DATE: Dec 03, 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

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 Discovery Tool Microcode CD-ROM creation and download instructions

5.0 Verifying microcode before download and notes
5.1 Microcode Download Procedure-PCI-X Dual Channel Ultra320 SCSI Adapter bus for AIX
5.2 Microcode Download Procedure-PCI-X Dual Channel Ultra320 SCSI Adapter bus for Linux (SLES 9 SP1, RHEL4 and above)
5.3 Microcode Download Procedure-PCI-X Dual Channel Ultra320 SCSI Adapter bus for Linux (SLES 9 base, RHEL3 and prior)

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

1.0 Microcode Change History:
 

070A0027	-Contains fixes for all known issues
070A0011	-iSeries enhancement for all U320 SCSI Controllers. Enhancement to recognize Hot Spare (RAID 0) DASD. -GA microcode level necessary for SCSI RAID AUX Cache Card Support. -Corrects p570 AIX microcode download issue present in 070A000b microcode level. 070A000b was not released for AIX/Linux.
050A008a	-Fix for a system hang at 0255/0266 after a SCSI Cable Pull test. -Improve error logging for 9010 errors by including the Bats status area. -Change handling of the Handle Query Resource State Command with the sync override bit set.
050A007b	-Dual-Initiator (HA) mode fixes: A) Adapter transition timing window shortened for non-SCSI RAID adapters (fix for CCIN 5702, 571A) B) Modification to cache flushing algorithm, fix for the below.      1) A Stand Alone SCSI RAID adapter (that is not the preferred Primary) is full of cache data that will take a long time to flush.      2) Power on a second SCSI RAID that is the preferred Primary.      3) When the failover happens the first SCSI RAID will not have finished flushing cache data before the second IOA starts talking to the drives that the first IOA is still flushing data to (CCIN 5703 & 571B) -Added NACA support (all U320 SCSI Controllers/Adapters)
050A006a	-Contains fix for HUS10K DASD Selection Timeouts which can cause a boot drive not to be found and the system to boot to SMS. -SCSI Target Mode fix for possible hung I/O operation -Added support for vendor unique “c0” command used in Atape & 3590 configurations w/ HVD/LVD converter and created workaround to prevent SCSI bus hang resulting in reset condition -Fix to prevent the following: Data may exist in the cache marked for the same section of disk. The older data was in the process of being destaged when power was lost on the adapter while the newer data was just written. The older data has a chance to be written back to disk upon power on rather than the newer.  This problem was seen sporadically in test w/ the IBM Hitachi 15K Rpm DASD.
050A0064	Do not install this level.  Configuration Problems w/ HUS10K DASD. -New revision level of microcode.  -Ported 20MBps SE fix to new revision level.
020A005e	Added detection for invalid DMA's. This DMA issue represents a potential data error. IBM recommends that you install this fix immediately.
020A005c	-Minimum support level for HV products -Increased BATs speed (Adapter/Controller comes available faster on bringup) -Added support for HV products
020A0057	Prior to microcode update, a shutdown is performed to the I2C bus to acquiesce activity.  This prevents the I2C bus from getting hung and the Virtual SES devices from coming up "defined".
020A0054	-Virtual SES code fix (SF2, L4).  1) (SF2, L4) I2C bus may hang when adapter reset occurs while the adapter is reading the EEPROM on the I2C bus.  Reduce window of occurrence. 2) (L4).  I2C bus timeout when adapter is reset and running diagnostics.
020A0052	-Virtual SES fixes:  a) LED fix for L4 system and b) PCI-X Quad Channel Ultra320 SCSI RAID Adapter fix for all systems -Error log changes:  a) Differentiated a error condition.  Adapter now logs a specific error instead of generic for a given situation. b) Return the correct error information to the pSeries Adapter Device Driver (ADD) so a SCSI adapter detected CRC error is logged instead of a program error microcode problem. Problem was seen on L4, SF2 and SF4. -Added Linux support features and fixed Linux drive replacement problem -Force SE mode to 20MBps when an SE device is connected to the 7029-6C3/6E3 new feature backplane.  This backplane expands the Integrated SCSI Controller adding an external port.
020A004e	External SE device fix;  external SE devices are limited to 20MBps. Added support for unique vendor command on 3580/3583 LTO tape device. Modification to run Ultra320 speeds using Linux kernel 2.6. Various performance enhancements.
020A0049	Enhanced SCSI signal path validation. Removed extended Target Mode delays. Removed erroneous AIX errors logged during drive microcode download. Added unique RAID array identifiers for Linux support. Removed erroneous SCSI bus reset error logged when a device reports an error condition. Corrected extended SCSI bus reset that may occur when running HACMP.
020A0041	Installing two 4-pack backplanes in a p615 may cause the second backplane (sesX) to boot in the defined state or not be seen.  Microcode 0041 corrects this problem.
020A0039	Enables Ultra 320 support
020A0018	This level removes erroneous SCSI_ERR_10 errors at boot and runtime and allows for internal Hot Swap
020A0005	GA level for p615
020A0003	GA level for Virtual SES support on p655 (7039-651), introduces Hot Swap on internal drives

Note:  In order for Ultra320 to function properly a minimum level of microcode is required for the DASD.  These are listed below

2.0 General information

2.1 Installation Time:
Approximately 30 minutes
 
2.2 Machine's Affected:
7029-6C3/6E3
7039-651

9110-510
9111-520

9113-550
9114-275

9116-565
9117-570

9133-55A
9406-520/550/750   

2.3 AIX Requirements:
For support:  AIX 5.1 ML_04 or AIX 5.2 ML_01
For U320 support:  AIX 5.1 ML_05, AIX 5.2 ML_02, AIX 5.3 or above along w/ the aforementioned minimum DASD microcode requirements.

2.4 Linux Requirements:
For support: SLES 8 SP3 or RHEL 3 U1 or above

Notes:
-SLES9 SP1 and RHEL4 introduce the functionality of the "iprconfig" utility which is referenced in the instructions for Linux sections, below.
-If you are using SLES9 base level, RHEL3 or below then please follow the instructions for AIX through section 5.0.  To flash the microcode continue to section 5.3.
-"iprconfig", the tool referenced in the Linux instructions, may be available in a Linux RPM package.  The tool set is called "iprutils".

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 bus installed in the target system. Use the following instructions to read the ROM level stored in the Adapter bus' VPD.

1)  List the SCSI initiators (adapters and controllers) installed in the system by typing:

    lsdev -C | grep scsi

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

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

   lscfg -vl scsiX

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

    DEVICE       LOCATION         DESCRIPTION

  scsi0             1S-08-00          PCI-X Dual Channel Ultra320 SCSI
                                      Adapter bus

        ROM Level.(alterable).......020A0018

If the ROM Level is less than 070A0027 then you should update the microcode.

3.1 Determine the Current Microcode Level for Linux:

RHEL 3:
1) To list the scsi initiators Type:  "ls /proc/scsi/ipr"

The Command will produce output similar to
"0 1 2"
2) To check the current microcode level for the adapter or controller Type:  "cat /proc/scsi/ipr/X"  (where X is the number from the previous command).
The Command will produce output similar to
"Firmware Version: 020A0018"

SLES 8 SP4:
1) To list the scsi initiators Type:  "ls /proc/scsi/ibmsis"
The Command will produce output similar to
"0 1 2"
2) To check the current microcode level for the adapter or controller Type: "cat /proc/scsi/ibmsis/X" (where X is the number from the previous command)
The Command will produce output similar to
"Firmware Version: 020A0018"

SLES 9 and RHEL 4:
1) Type "iprconfig"
2) Select "Display hardware status"
3) Select SCSI adapter by typing a "1" in front of it (570A or 570B) and pressing Enter.
4) The Command will produce output similar to
"Firmware Version . . . . . . . . . . . . : 020A0054"

If the Firmware Level is less than 070A0027 then you should update the microcode.

4.0 Downloading and Unpacking the Firmware Update Package from CORE

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, SLES9 base, RHEL3 & prior, the filename is pci.1069B166.0A-070A0027-1.aix5.1.noarch.rpm
    B) For SLES9 SP1, RHEL4 & above, the filename is pci.1069B166.0A-070A0027-1.Linux.noarch.rpm
3) Unpack the file by executing the instructions below:
    A) For AIX, SLES9 base, RHEL3 & prior, type "rpm -ihv --ignoreos --force pci.1069B166.0A-070A0027-1.aix5.1.noarch.rpm"
    B) For SLES9 SP1, RHEL4 & above, type "rpm -ihv --ignoreos --force pci.1069B166.0A-070A0027-1.Linux.noarch.rpm"
4a) For AIX, SLES9 base, RHEL3 & prior:  The microcode files will be added to /usr/lib/microcode/.
4b) For SLES9 SP1, RHEL4 & above:  The microcode files will be added to /lib/firmware/.
 

4.2 Discovery Tool Microcode CD-ROM creation and download instructions

To obtain information how to burn a CD-ROM and run the Discovery Tool for an AIX System please go to: http://techsupport.services.ibm.com/server/mdownload/CDROMhelp.html
1) After running the Discovery Tool successfully the "/tmp/microcode/RPM" directory was created and your rpm files are copied from the CD-ROM.

2) Change to that directory, "cd /tmp/microcode/RPM".

3) Unpack the file by executing the instructions below:
    Enter the commands:
        rpm -ihv --ignoreos --force pci.1069B166.0A-070A0027-1.aix5.1.noarch.rpm
4) Microcode files will be copied to "/etc/microcode".  The file size and checksum of the microcode image will be verified in Section 5.0

Notes:
 - "/etc/microcode" is a symbolic link to "/usr/lib/microcode".
 - If permission does not allow the copy to the above stated directory
                  or file then the user will be prompted for a new location.

 
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:  932244
Checksum:  34296
For AIX, SLES9 base, RHEL3 & prior:  "ls -l /usr/lib/microcode/44415255.070A0027" to verify Filesize. 
                "sum /usr/lib/microcode/44415255.070A0027" to verify Checksum.
For SLES9 SP1, RHEL4 & above:  "ls -l /lib/firmware/pci.1069B166.0A.070A0027" to verify Filesize.
                 "sum /lib/firmware/pci.1069B166.0A.070A0027" to verify Checksum.

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

For AIX, SLES9 base, RHEL3 & prior:
    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 44415255.070A0027"
    G)  Type: "quit"

For SLES9 SP1, RHEL4 & above:
    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: "bin"
    F)  Type: "get pci.1069B166.0A.070A0027"
    G)  Type: "quit"

5.1 Microcode Download Procedure-PCI-X Dual Channel Ultra320 SCSI Adapter bus for AIX

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 PCI-X Dual Channel Ultra320 SCSI Integrated Controllers (Adapter buses) that need to be updated from the list of devices by pressing "Enter".  The devices will be displayed as sisscsia#, 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 sisscsia# 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 070A0027 by typing "lscfg -vl scsi#" for each scsi device updated. <Where # is the number scsi device>