SAS Adapter/Controller (CCIN 572A, 572B, 572C, 57B8, 575C, 57D0) Microcode README

IBM eServer

PCI-X266 Ext Dual-x4 3Gb SAS Adapter (CCIN 572A)

PCI-X266 Ext Dual-x4 3Gb SAS RAID Adapter (CCIN 572B)

PCI-X266 Planar 3Gb SAS Adapter (CCIN 2BE0, 572C, 57D0)

PCI-X266 Planar 3Gb SAS RAID Adapter (CCIN 2BD9, 2BE1, 57B8)

PCI-X266 Auxiliary Cache Adapter (CCIN 575C)

 DATE:  Jun 06, 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-572A, 572B, 572C, 575C, 57B8, 57D0 SAS Adapters for AIX
5.2 Microcode Download Procedure-572A, 572B, 572C, 575C, 57B8, 57D0 SAS Adapters for Linux

6.0 Microcode Readme Change History

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

1.0 Microcode Change History:
NOTE: There were major changes between the "04xxxxxxx", "03xxxxxx" and "02xxxxxx" microcode levels.

For updating between those levels (and in general), if you have are using CCIN 57CF PCI-E SAS Planar RAID Controllers, CCIN 57B8/57B7 SAS RAID Enablement Features or CCIN 572F/575C DoubleWide SAS Adapter, please update both adapters.

Also, in a Dual Controller environment, it is advisable to update to the same microcode level on both adapters.

04200037	-Removed SAS Adapter's initiation of the SES LED lamp check function. This change resolves some recent field issues (circa 2012) where DASD backplane LEDs stayed on due to bus contention on the I2C bus. This was mainly seen in 8205-E6B/E6C split backplane configuration. Without this microcode, the likelihood of encountering the issue varied based on the installed System FW level. -Possible system hang during replacement of a mirrored disk drive in a Dual Storage IOA configuration -04448400 Adapter Unit Check following hot spare rebuild on array optimized to secondary adapter. *** Only occurs if drive is replaced during the hot spare rebuild. Dual Controller Only -Fix for SISSAS_FABRIC_ERRs (during SAS Speed Negotiation) w/ HHLT05 tape attached to CCIN 57B8 -IBM i ONLY: SAS I/O adapter enhancements during error recovery to prevent a very slight chance of undetected data corruption. Feature codes affected are FC5904, FC5906, FC5908, FC5903, FC5805, FC5662, FC5630, FC5268, FCEJ0F, FCEJ01 -Possible system hang caused by incorrect error recovery due to a SAS Port failure DH_PRC_JADE_HDWMGR_KAM_TABLE_PTY_ERR
04200033	-Minor fixes for the following error codes IOASC/PRC 06690200/14021403, 07278C00/17034918, 04448200/11050E51, 02048000/17101c15, 04448400/17034a25 -New DDR2 register settings for 572C in 9117-MMB, 9179-MHB
04200029	-Specific to MTM 8202 & 8205: Reduction in I2C bus traffic, eliminating unnecessary communication to PSOC. This change has shown to resolve situations where one Virtual "ses" device would configure as defined in DASD split backplane configurations. Note: This microcode change does not resolve other I2C bus contention issues outside of the SAS architecture. -Specific to MTM 8203/8204 with FC 8341 (low function DASD backplane, no SAS expanders). Fix for SISSAS_ER11T reporting against phy 2 (0002 FFFF) VPD: ROM Level.(alterable).......04200018 Customer Card ID Number.....572C Detail Data PROBLEM DATA 0000 0800 0002 FFFF 0000 0000 0000 0000 0000 0000 1910 00F0 0108 0000 0101 0000 0420 0018 0000 00FF 572C FFFE 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 -Contains fixes, previously included in 042x001b levels for Power Blade architecture (1 SAS Address per phy) -Added Error Code combo 04678000/10440039 to report invalid Dual Controller configurations. Previous undetected invalid configurations included: MTM 8202/8205, High End DASD backplane without CCIN 2BD9 & 2BE1) -Fix for SSD drive errors, 0B/4400 in CCIN 57CD configuration. Reduced Overall Command Timeout Value from 16 to 2. -Various other fixes/enhancements
04200020	Level 04200019 + 1 additional fix SAS I/O adapter error recovery enhancements for device hard media errors to prevent a very slight chance of undetected data corruption. This can only occur when a RAID-5 configuration is being used. The adapter microcode is updated to prevent the problem from occurring. Affected CCINs: All that are RAID 5 capable Affected feature codes include: FC5912, FC5679, FC5904, FC5906, FC5908, FC5901, FC5278, FC5903, FC5805, FC2053, FC2054, FC2055, FC5662, FC5630, FC5267, FC5263, FC5268, FC5900, FC5902, FC5909, FC5911, FC5652, FC5631, FC5618 (not intended for Power Blades use, see level 04200021 for Power Blades)
0420001b	Power Blade specific release (CCIN 57D0) -GA Level for RSSM Switch Module attached to PS700,701,702 Blades. -In the "04xxxxxx" microcode levels, only 1 SAS Address will be reported per 4 phy set. For certain Blade specific configurations (RSSM & NSSM attached) this can change the manner in which those attached devices must reference the host adapter. See device documentation for the correct instructions on how to setup the environment with the 57D0 SAS Controller at this code level. In the case of RSSM, see the Host System Attachment Guide. -Change to allow for 1 SAS Address to be reported for each phy for all embedded SAS Controllers on Power Blade. From the 04200010 release: (In the "0420xxxx" microcode levels, only 1 SAS Address will be reported per 4 phy set. This allows for a better bringup sequence with SAS expanders that can configure a Wide Port. This was a change from the prior levels where 1 SAS Address was reported for each phy.) For certain Power Blade specific configurations (RSSM & NSSM attached) this can change the manner in which those attached devices referenced the host adapter. As such, 0420001b introduces a change to allow for 1 SAS Address to be reported for each phy. This change is specific only to Power Blade's embedded SAS Controllers. To the end user, 0420001b (and above) should provide a similar experience to 03200066. If using a device attached to a SAS Switch (RSSM or NSSM), with 04200010, it is strongly recommended to update to 0420001b (or above).
04200019	GA level of CCINs 2BD9, 2BE0, 2BE1, 572C features specific to 8202-E4B, 8205-E6B, 8231-E2B GA level of CCIN 57CD -Minor enhancements for error conditions -Enhancement to SAS Controller Inquiry Page D0 response to encode the resource address differently. This code level, or above, may be necessary for Blade configurations with AIX levels released in the 2011 and beyond timeframe.
04200010	First customer release in the "04xxxxxx" level. GA level for 57D0 on PS700,701,702 Blades. -In the "0420xxxx" microcode levels, only 1 SAS Address will be reported per 4 phy set. This allows for a better bringup sequence with SAS expanders that can configure a Wide Port. This was a change from the prior levels where 1 SAS Address was reported for each phy.
04200008	GA level of 572C SAS Controller on 9117-MMB & 9179-MHB. This code level was not released.
03200066	Fixes for · All Adapters: IOASC/PRC 04448400/80FF0200, 04448400/80FF0300, 06678400/104212C2 · non-RAID (JBOD) only: 04448400/10802033 · Dual Controller only: IOASC/PRC 06678400/10440C10 · Dual Controller w/ Active/Active only: Changes to quiesce drive ops on drives that are not performing write same commands upon insertion of DASD (RAID and non-RAID) · CCIN 57B8, 572F (on Link to Aux Cache): IOASC/PRC 01080000/10272385
03200063	-Coincides with announcement of Dual Controller 572F/575C support (10/30/2009 GA) -There was a small possibility that the SAS Controller’s VPD update process could be interrupted on the first pairing of a 8204/8203 System Planar & 57B8 SAS RAID Enablement Card. This could leave the 57B8 in an unusable state. See Retain Tip H195958. This microcode moves the VPD update to a place in time to avoid the interruption. -Skip Operation improvements for SSD devices -572F/575C. Fix for 9071 & 9072 errors on boot -Close loophole on microcode update to a SES (split-backplane) which could potentially allow for microcode update both SAS paths to a particular device. If both paths are being updated then no paths would be active to the end device. -Fixes for various Adapter Unit Check conditions. -Fix for JS23 Blade (57D0) w/ NSSM. Tape connected to Port 4 would not configure
03200060	-Convergence of microcode paths. The fixes in 03200059 and 03200056 are contained in this code along with others.
03200059	HIPER: It is of utmost importance to install this fix if Active/Active is enabled in a Dual Controller environment. Prior to updating, it is required to update any attached "STxx" model SAS DASD. See the respective "STxx" microcode readmes for the minimum required microcode levels. This code level is based off 03200051. It does not contain the fixes in 03200056. Active/Active fix: One or more disks could get lost from an array when a Link error occurs. This posed a Data Loss possibility. It is strongly recommended that Active/Active be disabled when installing this microcode! Active/Active can be re-enabled, concurrently, after microcode installation on both adapters. Microcode Download update incomplete fix: The possibility existed where future microcode download attempts will not complete successfully and thus need to be retried. Once this code is successfully flashed that possibility is removed.
03200056	Power Blade (JS12, JS22, JS23, JS43) release. Fixes are specific to CCIN 57D0 on JS23/JS43 with SAS Active Pass through card with the following attachments DS3200: Correction to Multi-path LUN breakdown accessible via the SAS Array Manager RSSM: 04050000 on new commands. Required for RSSM GA Fix for Path failover issues seen during error injection tests. Required for RSSM GA
03200051	Level 03200048 + 1 additional fix CCIN 57BA, FC 5911 specific fix for SISSAS_ERR11T w/ error code FFFE, SISSAS_FABRIC_ERROR w/ error code 4100 or 4101 (This code was not actually released to customers)
03200048	-Add support (GA Level) for CCIN 572F, 574E, 575C, 57B3, 57B7 (revision), 57BA SSD DASD Blade environment options coinciding with May 2009 release: 7778-23X BCS DASD control NSSM RSSM DS3200 -Allow for 6G devices under an expander. Devices will run at 3G -Various Unit Check fixes -Dual Controller mode: Enabled Active/Active mode NOTE: There were major changes between the "03xxxxxx" and "02xxxxxx" microcode level. If you have are using CCIN 57B8/57B7 SCSI RAID Enablement Features or CCIN 572F/575C DoubleWide SAS Adapter please update both adapters.
03200046	-EC'ed on to the 572C SAS Controller for various System Planar releases. This code level was not otherwise downloadable via the customer website for microcode download
02200070	-Fix for 04448400 with 10272212 and other Unit Checks conditions. -Corrects a situation where adapter did not enable caching in a specific dual controller scenario.
02200065	-Fix for out of resources error. The SAS/SCSI controller would previously allow for up to 16 resources per drive. This has been increased to 20 to coincide with the theoretical maximum.
02200059	-Fix for 572B in Dual Controller mode. The adapter will no longer log a 9076 error on a boot, if the system contains 572B's that have no FC 5886 SAS drawers attached.
02200056	-CCIN 572A & 57B9 enhancement to add 2 extra retries upon configuration. This modification was made to more reliably configure split backplane configurations without AIX reporting errors. For these split backplane configurations, please install this code along w/ 9117-MMA SES microcode level 0021 or 8204-E8A/8203-E4A SES microcode level 0008 -Various Target Mode/Dual Controller enhancements.
02200050	-GA Level for 572B -This microcode level fixes a potential undetected loss of data that was discovered in test between CCIN 572A and DAT72 SAS tape drive (FC 1400 or 5907). There have been no reported cases of this occurring in the field and the chance of occurrence is extremely small - near 0.
0220004a	Fix for TEMP SISSAS_ERR11T logged against CCIN 57B7 during boot or other configuration time. That error decoded further as a REASON FOR FAILURE Timeout - op started. A microcode update to 57B8 addresses the issue. It is best practice to apply the update to 57B7 when updating 57B8.
0220003c	Various Unit Check condition fixes (04448400 and 04448200 errors)
02200039	GA Level for CCIN 57B8.
02200035	GA Level for CCIN 572A, 572C on 7998-61X
01200041	-Data error fix for Low probability condition. If data loss is discovered on two devices at very close intervals, it was possible that the indication of this condition could have been lost on device 2 during device 1's recovery.
0120003b	-Numerous functional enhancements to prevent adapter error and Unit Check Conditions. Unit Checks require an adapter reset to recover. -Fix for error logged during AIX concurrent maintenance when DVD drive is removed and not replaced.
01200037	GA Level for CCIN 572C

2.0 General information

This subject microcode is to be used on the following SAS Adapter/controller types:
CCIN 572A: PCI-X266 Ext Dual-x4 3Gb SAS Adapter

CCIN 572B: PCI-X266 Ext Dual-x4 3Gb SAS RAID Adapter
CCIN 2BE0, 572C: PCI-X266 Planar 3Gb SAS Adapter
CCIN 2BD9, 2BE1, 57B8: PCI-X266 Planar 3Gb SAS RAID Adapter

CCIN 575C: PCI-X266 Auxiliary Cache Adapter

2.1 Installation Time:
Approximately 30 minutes

2.2 Machine's Affected:

2BD9

8202-E4B

8205-E6B

8231-E2B

2BE0

8202-E4B

8205-E6B

2BE1

8202-E4B
8205-E6B
8231-E2B

572A & 572B

7311-D11, D20

7314-G30

8202-E4B

8203-E4A

8204-E8A

8205-E6B

8233-E8B

8234-EMA

8236-E8C

9111-520
9113-550
9116-561
9117-570
9117-MMA

9119-590
9119-595

9119-FHA

9125-F2A

9131-52A
9133-55A

572C

8202-E4B

8203-E4A

8204-E8A

8205-E6B

8231-E2B

8233-E8B

8234-EMA

8236-E8C

9117-MMA

9125-F2A

575C

7311-D20

7314-G30

8202-E4B

8203-E4A

8204-E8A

8205-E6B

8233-E8B

8234-EMA

8236-E8C

9117-MMA

9119-FHA

9125-F2A

57B8

8203-E4A

8204-E8A

8233-E8B

8236-E8C

57D0

7778-23X

7998-60X, 61X

8406-70Y, 71Y

2.3 AIX Requirements:
TL refers to Technology Level

SP refers to Service Pack

2BD9

AIX 5.3 TL_10 w/ SP5
AIX 5.3 TL_11 w/ SP5
AIX 5.3 TL_12 w/ SP2
AIX 6.1 TL_06
AIX 7.1

or above

2BE0

AIX 5.3 TL_10 w/ SP5
AIX 5.3 TL_11 w/ SP5
AIX 5.3 TL_12 w/ SP2
AIX 6.1 TL_06
AIX 7.1

or above

2BE1

AIX 5.3 TL_10 w/ SP5
AIX 5.3 TL_11 w/ SP5
AIX 5.3 TL_12 w/ SP2
AIX 6.1 TL_06
AIX 7.1

or above

572A

AIX 5.3 TL_06 w/ SP4

AIX 5.3 TL_07

AIX 6.1

or above

572B

AIX 5.3 TL_6 w/ SP10

AIX 5.3 TL_7 w/ SP7

AIX 5.3 TL_8

AIX 6.1 TL_0 w/ SP7

AIX 6.1 TL_1

or above

572C

AIX 5.2 TL_10

AIX 5.3 TL_06

AIX 6.1

or above

(on 8202-E4B, 8205-E6B, 8231-E2B)

AIX 5.3 TL_10 w/ SP5
AIX 5.3 TL_11 w/ SP5
AIX 5.3 TL_12 w/ SP2
AIX 6.1 TL_06
AIX 7.1

or above

575C

AIX 5.3 TL_07 w/ SP9

AIX 5.3 TL_08 w/ SP7

AIX 5.3 TL_09 w/ SP4

AIX 5.3 TL_10
AIX 6.1 TL_00 w/ SP9

AIX 6.1 TL_01 w/ SP5

AIX 6.1 TL_02 w/ SP4

AIX 6.1 TL_03

or above

57B8

AIX 5.3 TL_06 w/ SP4

AIX 5.3 TL_07

AIX 6.1

or above

57D0

AIX 5.2 TL_10

AIX 5.3 TL_06

AIX 6.1

or above

2.4 Linux Requirements:

2BD9

SUSE Linux Enterprise Server 10-SP3, 11-SP1 for POWER or above
Red Hat Enterprise Linux for POWER Version 5 Update 5 or above

2BE0

SUSE Linux Enterprise Server 10-SP3, 11-SP1 for POWER or above
Red Hat Enterprise Linux for POWER Version 5 Update 5 or above

2BE1

SUSE Linux Enterprise Server 10-SP3, 11-SP1 for POWER or above
Red Hat Enterprise Linux for POWER Version 5 Update 5 or above

572A

SUSE Linux Enterprise Server 10-SP1 for POWER or above
Red Hat Enterprise Linux for POWER Version 4 Update 6, RHEL 5 Update 1 or above

572B

SUSE Linux Enterprise Server 10-SP2 for POWER or above
Red Hat Enterprise Linux for POWER Version 4 Update 7, RHEL 5 Update 2 or above

572C

SUSE Linux Enterprise Server 10 for POWER or above
Red Hat Enterprise Linux for POWER Version 4 Update 4 or above

(on 8202-E4B, 8205-E6B, 8231-E2B)

SUSE Linux Enterprise Server 10-SP3, 11-SP1 for POWER or above
Red Hat Enterprise Linux for POWER Version 5 Update 5 or above

57B8

SUSE Linux Enterprise Server 10-SP1 for POWER or above
Red Hat Enterprise Linux for POWER Version 4 Update 6, RHEL 5 Update 1 or above

575C

SUSE Linux Enterprise Server 10-SP3 for POWER or above
Red Hat Enterprise Linux for POWER Version 5 Update 2 or above

57D0

SUSE Linux Enterprise Server 10 for POWER or above
Red Hat Enterprise Linux for POWER Version 4 Update 4 or above

2.5 IBM i Requirements:

2BD9

IBM I 7.1 or later

2BE0

IBM I 7.1 or later

2BE1

IBM I 7.1 or later

572A

For Dual Controller support: IBM I V5R4 with V5R4M5 machine code, or later.

572B

For Dual Controller support: IBM I V5R4 with V5R4M5 machine code, or later.

572C

IBM I V5R4 with V5R4M5 machine code, or later.

(on 8202-E4B, 8205-E6B, 8231-E2B)

IBM I 7.1 or later

57B8

IBM I V5R4 with V5R4M5 machine code, or later.

575C

IBM I V5R4 with V5R4M5 machine code, or later.

57D0

Suported only under VIOS

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

For 2BD9

DEVICE LOCATION DESCRIPTION

sissas1 U78AA.001.DNJP058-P1-C19-T1 PCI-X266 Planar 3Gb SAS RAID Adapter

PCI-X266 Planar 3Gb SAS RAID Adapter :
Part Number.................44V8354
FRU Number..................44V8353
Serial Number...............YL300025D047
Manufacture ID..............0000
EC Level....................0
ROM Level.(alterable).......04200018
Customer Card ID Number.....2BD9
Product Specific.(Z1).......1
Hardware Location Code......U78AA.001.DNJP058-P1-C19-T1

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

For 2BE0

DEVICE LOCATION DESCRIPTION

sissas1 U78AA.001.WIH002F-P1-C19-T1 PCI-X266 Planar 3Gb SAS Adapter

PCI-X266 Planar 3Gb SAS Adapter :
Part Number.................44V8369
FRU Number..................44V8368
Serial Number...............YL3000000001
Manufacture ID..............0000
EC Level....................0
ROM Level.(alterable).......04200017
Customer Card ID Number.....2BE0
Product Specific.(Z1).......1
Hardware Location Code......U78AA.001.WIH002F-P1-C19-T1

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

For 2BE1

DEVICE LOCATION DESCRIPTION

sissas0 U78AA.001.DNJP058-P1-T9 PCI-X266 Planar 3Gb SAS RAID Adapter

ROM Level.(alterable).......04200018
Customer Card ID Number.....2BE1
Hardware Location Code......U78AA.001.DNJP058-P1-T9

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

For 572A

DEVICE LOCATION DESCRIPTION

sissas0 U78A0.001.DNWFZZT-P1-C4-T1 PCI-X266 Ext Dual-x4 3Gb SAS Adapter

PCI-X266 Ext Dual-x4 3Gb SAS Adapter :

Part Number.................42R7989

FRU Number..................42R7989

Serial Number...............YL3027138706

Manufacture ID..............0002

EC Level....................0

ROM Level.(alterable).......02200026

Customer Card ID Number.....572A

Product Specific.(Z1).......1

Hardware Location Code......U78A0.001.DNWFZZT-P1-C4-T1

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

For 572C

DEVICE LOCATION DESCRIPTION

sissas2 U789D.001.DQDTTPM-P1-T3 PCI-X266 Planar 3Gb SAS Adapter

ROM Level.(alterable).......01200036
Customer Card ID Number.....572C
Device Specific.(YL)........U789D.001.DQDTTPM-P1-T3

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

For 57B8

DEVICE LOCATION DESCRIPTION

sissas0 U78A0.001.DNWFZYA-P1-T9 PCI-X266 Planar 3Gb SAS RAID Adapter

ROM Level.(alterable).......02200026
Customer Card ID Number.....57B8
Device Specific.(YL)........U78A0.001.DNWFZYA-P1-T9

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

For 575C

DEVICE LOCATION DESCRIPTION

sissas1 U7311.D20.109517A-P1-C02-T1 PCI-X266 Auxiliary Cache Adapter

PCI-X266 Auxiliary Cache Adapter :
Part Number.................44V4577
FRU Number..................44V5193
Serial Number...............YL3229020007
Manufacture ID..............0022
EC Level....................2
ROM Level.(alterable).......03200047
Customer Card ID Number.....575C
Product Specific.(Z1).......1
Hardware Location Code......U7311.D20.109517A-P1-C02-T1

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

For 57D0

DEVICE LOCATION DESCRIPTION

sissas0 U78A5.001.WIH23D3-P1-T5 PCI-X266 Planar 3Gb SAS Adapter

ROM Level.(alterable).......0320003c
Customer Card ID Number.....57D0
Hardware Location Code......U78A5.001.WIH23D3-P1-T5

If the ROM Level is less than 04200037 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 . . . . . . . . . . . . : 02200035"

If the Firmware Version is less than 04200037 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.101402BD.20-04200037-1.aix5.1.noarch.rpm"
B) "pci.101402BD.20-04200037-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: Unpack the RPM file by using the following command: "rpm -ihv --ignoreos --force pci.101402BD.20-04200037-1.aix5.1.noarch.rpm"
5b) For Linux: Unpack the RPM file by using the following command: "rpm -ihv --ignoreos --force pci.101402BD.20-04200037-1.Linux.noarch.rpm"
6a) For AIX: The microcode files will be added to /usr/lib/microcode/.
6b) For Linux: 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: The filename is pci.101402BD.20-04200037-1.aix5.1.noarch.rpm
    B) For Linux: The filename is pci.101402BD.20-04200037-1.Linux.noarch.rpm
3) Unpack the file by executing the instructions below:
    A) For AIX: Type "rpm -ihv --ignoreos --force pci.101402BD.20-04200037-1.aix5.1.noarch.rpm"
    B) For Linux: Type "rpm -ihv --ignoreos --force pci.101402BD.20-04200037-1.Linux.noarch.rpm"
4a) For AIX: The microcode files will be added to /usr/lib/microcode/.
4b) For Linux: 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: 1360784
Checksum: 57451
For AIX: "ls -l /usr/lib/microcode/53495320.04200037" to verify Filesize.
"sum /usr/lib/microcode/53495320.04200037" to verify Checksum.
For Linux: "ls -l /lib/firmware/pci.101402BD.20.04200037" to verify Filesize.
"sum /lib/firmware/pci.101402BD.20.04200037" 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:
    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 53495320.04200037"
    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.101402BD.20.04200037"
    F) Type: "quit"

5.1 Microcode Download Procedure-572A, 572B, 572C, 575C, 57B8, 57D0 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 04200037 by typing "lscfg -vl sissas#" for each SAS device updated. <Where # is the number sissas device>

5.2 Microcode Download Procedure-572A, 572B, 572C, 575C, 57B8, 57D0 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 04200037). 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-06	-Added Microcode Level 04200037
2012-01-13	-Added Microcode Level 04200033
2011-05-06	-Added Microcode Level 04200029
2010-11-04	-Added Microcode Level 04200020
2010-09-08	-Added Microcode Level 0420001b. Specific to Power Blades CCIN 57D0 release.
2010-09-02	-Added Microcode Level 04200019. Updated Section 4.2 Microcode Update via CD
2010-04-22	-Added Microcode Level 04200010 & 04200008
2010-01-26	-Added Microcode Level 03200066
2009-10-26	-Added Microcode Level 03200063
2009-09-30	-Microcode Level 03200060 added. -Added NOTE to Section 1.0 -Added adapter types to Section 2.0
2009-07-20	-Microcode Level 03200059 added. -Added reference to microcode level 03200051. -Added to/Corrected Section 2.2 Machine's affected support
2009-07-09	-Microcode Level 03200056 added.
2009-06-19	-Added 57D0 to Title. -Added 57D0 info to Linux and IBM i Min requirements section -CCIN 57D0 was in use on Blades prior to microcode level 03200048, corrected
2009-04-27	-Microcode Level 03200048 added. -Added 575C, 57D0 -Added 8234-EMA, 7778-23X
2008-12-08	-Microcode Level 02200070 added. Updated Minimum Support levels for AIX to reflect release of SP (Service Packs) on older AIX levels.
2008-10-21	-Microcode Level 02200065 added
2008-09-08	-Added MTM 7998-60X
2008-07-15	-Microcode Level 02200059 added
2008-06-04	-Microcode Level 02200056 added
2008-04-30	-Microcode Level 02200050 added -Added 572B SAS RAID Adapter -Corrected Section 2.4 RHEL Minimum requirements for 572A, 57B8 -Added new MTM's to Section 2.2 Machine's Affected
2008-04-07	-Added 57B8 SAS RAID Enablement Card to the title of the readme -Modified Section 2.3 AIX Support Level requirements. AIX 5.2 TL_11 does not exist and thus was removed. AIX 6.1 was added.