IBM
eServer
PCI-X266 Ext Tri-x4 3Gb SAS RAID Adapter(CCIN
572F)
DATE: May 06, 2011
Table of Contents
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 Microcode Update via CD
5.0 Verifying microcode before download and notes
5.1 Microcode Download Procedure-572F SAS Adapters for AIX
5.2 Microcode Download Procedure-572F SAS Adapters for Linux
6.0 Microcode Readme Change History
=====================================================================================
NOTE: There were major changes between the "04xxxxxx", "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.
| 04210029 |
-572F: Resolution of DMA Access Error. Sense Data 01418000/11050E34 -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) -Various other fixes/enhancements |
| 04210020 |
Level 04210019 + 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 |
| 04210019 |
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. |
| 0421000f |
First customer release in the "04xxxxxx" level. |
| 03210066 |
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 |
| 03210063 |
-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 |
| 03210060 | -Convergence of microcode paths. The fixes in 03210059 and 03210056 are contained in this code along with others. |
| 03210059 |
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 03210051. It does not contain the fixes in 03210056.
(This code was not actually released to customers) |
| 03210051 |
Level 03210048 + 1 additional fix
(This code was not actually released to customers) |
| 03210048 |
-Add support (GA Level) for
-Allow for 6G devices under an expander. Devices will run at 3G -Various Unit Check fixes -Dual Controller mode: Enabled Active/Active mode |
This subject microcode is to be used
on the following SAS Adapter/controller types:
CCIN 572F: PCI-X266 Ext Tri-x4 3Gb SAS RAID Adapter
2.1
Installation Time:
Approximately 30 minutes
2.2
Machine's Affected:
572F
7311-D20
7314-G30
8202-E4B
8203-E4A
8204-E8A
8205-E6B
8233-E8B
8234-EMA
8236-E8C
9117-MMA
9119-FHA
9125-F2A
2.3
AIX Requirements:
TL refers to Technology Level
SP refers to Service Pack
572F
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
572F
SUSE Linux Enterprise Server 10-SP3
for POWER or above
Red Hat Enterprise Linux for POWER Version 5 Update 2 or above
572F
IBM I V5R4 with V5R4M5 machine code, or later.
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 572F
DEVICE LOCATION DESCRIPTION
sissas0
U7311.D20.109517A-P1-C01-T1 PCI-X266 Ext Tri-x4 3Gb SAS RAID Adapter
PCI-X266 Ext Tri-x4 3Gb SAS RAID Adapter :
Part Number.................44V4579
FRU Number..................44V5193
Serial Number...............YL3229020007
Manufacture ID..............0022
EC Level....................2
ROM Level.(alterable).......03210047
Customer Card ID Number.....572F
Product Specific.(Z1).......1
Hardware Location Code......U7311.D20.109517A-P1-C01-T1
If the ROM Level is less than 04210029 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 . . . . . . . .
. . . . : 03210047"
If the Firmware Version is less
than 04210029 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.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.101402c3.21.04210029-1.aix5.1.noarch.rpm
B) For
Linux: The filename is
pci.101402c3.21.04210029-1.Linux.noarch.rpm
3) Unpack the file by executing the instructions
below:
A) For AIX:
Type "rpm -ihv --ignoreos --force pci.101402c3.21.04210029-1.aix5.1.noarch.rpm"
B) For Linux:
Type "rpm -ihv --ignoreos --force pci.101402c3.21.04210029-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/.
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: 1362172
Checksum: 37475
For AIX: "ls -l /usr/lib/microcode/53495321.04210029" to
verify Filesize.
"sum /usr/lib/microcode/53495321.04210029"
to verify Checksum.
For Linux: "ls
-l /lib/firmware/pci.101402c3.21.04210029"
to
verify Filesize.
"sum /lib/firmware/pci.101402c3.21.04210029" 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 53495321.04210029"
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.101402c3.21.04210029"
F) Type: "quit"
5.1 Microcode Download Procedure-572F SAS Adapters for AIX
Procedure:6.0 Microcode Readme Change History
| 2011-05-06 | -Added Microcode Level 04210029 |
| 2010-11-04 | -Added Microcode Level 04210020 |
| 2010-09-02 | -Added Microcode Level 04210019. Updated Section 4.2 Microcode Update via CD |
| 2010-04-22 | -Added Microcode Level 0421000f |
| 2010-01-26 | -Added Microcode Level 03210066 |
| 2009-10-26 |
-Added Microcode Level 03210063 |
| 2009-09-30 |
-Added Microcode Level 03210060 -Added NOTE to Section 1.0 |
| 2009-07-17 |
-Added reference to Microcode Level 03210051 & 03210059.
|