The Microcode files provided in this package are only for use when installing disk drive microcode to a disk drive installed in a IBM pSeries/RS6000 system using the AIX or Linux Operating System.

1.1 Disk Drives Affected

Below is the list of microcode files in this package, these files are for use with the following pSeries SCSI hard disk drive ONLY:

NOTE: To insure the integrity of microcode files, please make sure the checksum value is correct after extraction

Size        Disk Drive Model        FRU#       P/N (VPD)         Microcode File Name        Checksum         Comment
--------    ---------------------   -----------      -------------    ----------------------------------       ----------      -----------------------------------------
9GB       ST373207LW         80P3392      26K5297     ST37320.4A553030.43373048    05759   (68 pin-Bolt-in)

18GB ST373207LW 80P3393 26K5298 ST37320.4A553031.43373048 05759 (68 pin-Bolt-in)

18GB ST373207LC 00P3064 26K5285 ST37320.4A553032.43373048 05759 (80 pin-U320 carrier)

18GB ST373207LC 09P4437 26K5286 ST37320.4A553033.43373048 05759 (80 pin-Scallop carrier)

18GB ST373207LC 80P3394 26K5287 ST37320.4A553034.43373048 05759 (80 pin-Mill)

36GB ST373207LW 80P3395 26K5299 ST37320.4A553035.43373048 05759 (68 pin-Bolt-in)

36GB ST373207LC 80P3396 26K5290 ST37320.4A553036.43373048 05759 (80 pin-Mill)

36GB ST373207LC 00P3068 26K5288 ST37320.4A553037.43373048 05759 (80 pin-U320 carrier)

36GB ST373207LC 09P4447 26K5289 ST37320.4A553038.43373048 05759 (80 pin-Scallop carrier)

36GB ST373207LC 80P3404 26K5184 ST37320.4A483030.43373048 05759 (80 pin-U3-HV)

73GB ST373207LW 80P3397 71P7473 ST37320.4A553039.43373048 05759 (68 pin-Bolt-in)

73GB ST373207LC 80P3398 26K5293 ST37320.4A553041.43373048 05759 (80 pin-Mill carrier)

73GB ST373207LC 00P3072 26K5291 ST37320.4A553042.43373048 05759 (80 pin-U320 carrier)

73GB ST373207LC 03N6325 26K5533 ST37320.4A523030.43373048 05759 (80 pin-U320-RoHS)

73GB ST373207LC 09P4890 26K5292 ST37320.4A553043.43373048 05759 (80 pin-Scallop carrier)

73GB ST373207LC 80P3406 26K5250 ST37320.4A483031.43373048 05759 (80 pin-U3-HV)

73GB ST373207LC 03N6327 26K5573 ST37320.4A523030.43373048 05759 (80 pin-U3-HV-RoHS)

146GB ST3146707LC 00P2665 26K5294 ST31467.4A553030.43373048 05759 (80 pin-U320 carrier)

146GB ST3146707LC 03N6330 26K5534 ST31467.4A523030.43373048 05759 (80 pin-U320-RoHS)

146GB ST3146707LC 00P2669 26K5295 ST31467.4A553031.43373048 05759 (80 pin-Scallop carrier)

146GB ST3146707LC 80P3408 26K5259 ST31467.4A483030.43373048 05759 (80 pin-U3-HV)

146GB ST3146707LC 03N6332 26K5574 ST31467.4A523030.43373048 05759 (80 pin-U3-HV-RoHS)

300GB ST330007LC 80P3400 26K5296 ST33000.4A553030.43373048 05759 (80 pin-U320 carrier)

300GB ST330007LC 03N6335 26K5535 ST33000.4A523030.43373048 05759 (80 pin-U320-RoHS)

300GB ST330007LC 80P3410 26K5284 ST33000.4A483030.43373048 05759 (80 pin-U3-HV)

300GB ST330007LC 03N6357 26K5575 ST33000.4A523030.43373048 05759 (80 pin-U3-HV-RoHS)

1.2 Microcode Change History

Release date	Code level	Change Description
May 14, 2007	C70H	Read/write performance enhancement for very large file transfers
April 20, 2006	C70D	Changed “read look ahead” routine to improve drive’s read performance in certain applications. The specific application does what is called disk "stride" or “skip” read; example of striding is to read 4KBytes of data, skip the next 4Kbytes, read the following 4KBytes, and so on. This change does not effect normal “random” or “sequential” read performance
November 15, 2005	C70C	Fixed a microcode bug that in rare situations causes drive to report un-recovered read errors, also includes other minor fixes and enhancements.
August 2005	C70A	Fixed format problem, problem description and work around procedure is explained in section 4 below.
June 2005	C708	Initial Release

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

2. AIX Operating System

2.1 Installation Time

Approximately 20 minutes if drive is part of rootvg(using Diagnostics CD); Approximately 5 minutes/drive if drive is not part of rootvg(using concurrent diagnostics).

2.2 Determine Drive Model, FRU&PN and Current Microcode Level
2.2.1 SCSI Drives attached to SCSI Controllers and PCI-X RAID Adapters

To see the drive type and current microcode level, Execute the following command:
lscfg -vl hdisk* |pg ; For drives NOT configured for RAID

lscfg –vl pdisk* |pg ; For drives configured for RAID

DEVICE LOCATION DESCRIPTION

hdisk3 U0.1-P1/Z1-A5 16 Bit LVD SCSI Disk Drive (73400 MB)

Manufacturer................IBM

Machine Type and Model......ST373207LC

FRU Number..................03N6325

ROS Level and ID............43373048

Serial Number...............00041843

EC Level....................H13979

Part Number.................26K5533

Device Specific.(Z0)........000004129F00013E

Device Specific.(Z1)........0802C712

Device Specific.(Z2)........0002

Device Specific.(Z3)........05179

Device Specific.(Z4)........0001

Device Specific.(Z5)........22

Device Specific.(Z6)........H13979

If the data returned in the “Part Number”, “FRU Number”, and “Machine Type and Model” fields match the one listed in section 1.1 AND the "ROS Level and ID...." field of that data is below "43373048", this microcode applies. If this level is already installed then the "ROS Level and ID...." shows: "43373048"
Note: Drive microcode level in “ROS Level and ID …” field is displayed in Hex value of ASCII characters in VPD data. Each alpha-numeric ASCII character converts to a 2-digit hex number. For example in VPD displayed above, 43 Hex= ASCII character "C"; 37 Hex= ASCII character "7"; 30 Hex=ASCII character "0"; 48 Hex=ASCII character "H", microcode level is "C70H".

Please note that unlike other disk drive VPD’s, field (Z1) does NOT display correct microcode level(C712) because this field only displays Hex characters and “H” is not a hex character

For SP systems with multiple nodes, you can use the following command to query all of the nodes at one time. Use of this command will also limit the amount of data returned, making it easier to audit. It returns only the pertinent information: node name, hdisk number, ROS Level and ID and part number.

dsh -a lscfg -v |egrep 'hdisk|ROS|Part'

pesp_n1:   hdisk0            10-60-00-0,0      16 Bit LVD SCSI Disk Drive (73400 MB)
pesp_n1:         ROS Level and ID............ 43373048
pesp_n1:         Part Number................. 26K5533
pesp_n5:   hdisk0            10-60-00-0,0      16 Bit LVD SCSI Disk Drive (73400 MB)
pesp_n5:         ROS Level and ID............ 43373048
pesp_n5:         Part Number................. 26K5533
pesp_n5:   hdisk1            10-60-00-8,0      16 Bit LVD SCSI Disk Drive (73400 MB)
pesp_n5:         ROS Level and ID............ 43373048
pesp_n5:         Part Number................. 26K5533

2.2.2 SCSI Drives attached to PCI SCSI RAID Controllers

At AIX command line, type:
Diag
Select "Task Selection" from diagnostics menu.
Select "PCI RAID Physical Disk Identify"
Select SCSI RAID Adapter (press enter, then F7 to Commit)
This will display the Vital Product Data for Physical Disk drives attached to the RAID adapter.

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

2.3 Transferring and Unpacking the Microcode Update Package

2.3.1 Internet AIX self extracting file (.bin)

a) Make a directory on an AIX system to receive the AIX format file.
Enter: mkdir /tmp/fwupdate
b) Transfer the AIX format file to /tmp/fwupdate directory (using "Save as ...").
You'll see the filename is CH10K7.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x CH10K7.bin
./ CH10K7.bin
[Don't overlook the periods (.) in the above command.]

The directory CH10K7 with microcode files listed in section 1.1 will be added to /tmp/fwupdate.

d-Enter the following command to copy the microcode files to " /etc/microcode " directory :
cp /tmp/fwupdate/10k300/ST3* /etc/microcode

e- If transferring files to a different system using floppy diskettes, use the following procedure to copy files to diskette
Note: Don't overlook the complete path of microcode files, AIX Diag microcode download will not work if files are not copied with complete path onto the diskette. Enter the following command to copy microcode file(s) onto a floppy diskette
ls /etc/microcode/ microcodefilename | backup -ivf /dev/rfd0
where microcodefilename is microcode file that is needed, for example:
ls /etc/microcode/ ST33000.4A523030.43373048 | backup -ivf /dev/rfd0

2.3.2 Internet RPM package

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

a) Make a directory on an AIX system to receive the RPM format file.
Enter: mkdir /tmp/microcode

b) Transfer the RPM format file to the /tmp/microcode directory (using "Save as ...").
You'll see the filename is CH10K7-C70H-AIX.rpm

c) Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv –ignoreos CH10K7-C70H -AIX.rpm

The file size and checksum will be verified.

The microcode files will be added to /etc/microcode/

2.3.3 CD-ROM

Copy microcode updates from the CD-ROM to standard locations on your local disk:

1. RPM packaged microcode files will be copied to "/tmp/microcode/RPM"
2. Microcode files will be copied to /usr/lib/microcode

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.
========================================================

2.4 Microcode Download Procedure

2.4.1 SCSI Drives Attached to SCSI Adapter

Warning: Do not power off the system or the drive during microcode download as this may permanently damage the disk drive

NOTE: Please save current and older versions of the microcode update files in case you need to restore your system.

Caution: The microcode download process is nondestructive to the hard disks; however, as a precaution, ensure that a backup operation has been performed on the affected systems PRIOR to the microcode installation.

Can microcode be installed Concurrently?
AIX level 5.1 and above supports concurrent microcode download on all drives, including drives that are part of rootvg.
AIX level 4.33 and below does not support concurrent microcode download if drive is part of rootvg, microcode download can ONLY be performed in service mode(stand alone) using diagnostics CD. If disk is not part of rootvg, microcode download can be performed cuncurrently as long as drive is not in use.

Is system reboot needed to activate the microcode: Yes if stand alone diagnostics is used, NO if concurrent diagnostics is used.

Installation Time: Approximately 20 minutes/drive if stand alone diagnostics is used(using Diagnostics CD); Approximately 5 minutes/drive if consurrent diagnostics is used.

2.4.1.1 AIX level 5.1 and above

2.4.1.2.1 Concurrent Download

1. Type diag at the prompt.
2. Select the "Task Selection" from diagnostics menu.
3. Select "Microcode Download" from "Task Selection" menu.
4. Select resource that microcode will be applied to(hdisk? For physical disk, pdisk for RAID configured disks) and press ENTER, then press "F7" to commit..
5- A small screen displays the message " *** NOTICE*** The microcode installation occurs while the attached drives are available for use..... "
    Press enter to continue
6. Select the source for microcode, use arrow key to go up/down, Enter to continue.
                      /etc/microcode
                      diskette

- Use /etc/microcode if "restore" command is used to copy files from diskette onto the disk
- Use diskette if using diskette as the source for download

NOTE: A prompt will ask you to insert the microcode diskette in diskette drive(if Diskette is selected above). Insert the diskette and press ENTER

7- Display shows a list of microcodes available for the selected drive, highlight option "M ST3xx...", the latest microcode for the drive and press ENTER. A message may warn you that current level of microcode is not available on the media, press ENTER to continue.

8. You will receive a msg. "Current Microcode is...." and "Download has completed successfully"
(this may take a few minutes)
9. Return to the Tasks Selection menu and repeat this procedure for each hard disk that requires this microcode.
10. Exit diagnostic(and reboot if needed).

2.4.1.2 AIX level 4.33:
This procedure is for drives that are not part of rootvg or paging space:
1. This step is optional. Microcode download can be performed either from Diskette or from Disk. To copy files from the diskette to disk, place the diskette containing microcode files into diskette drive A, at AIX Prompt type   restore
2- At AIX prompt, type   diag
3. Select the "Task Selection" from diagnostics menu.
4. Select "Microcode Download" from "Task Selection" menu.
5. Select resource that microcode will be applied to(hdisk?) and press ENTER.
6. Press "F7" to commit.
     (The current microcode level of the resource you selected earlier will be displayed at the top of the screen)
7. Make the following selections on the next screen:
    Select Input Device --------------------------------------- [ diskette] <---------- Disk can be used if "restore" command is used in step 1
    Microcode level to download ----------------------------- [ latest]
    Download latest level even if ------------------------------ [ yes]
    current is missing
NOTE: A prompt will ask you to insert the microcode diskette into the floppy drive(if Diskette is selected above). Insert the diskette which accompanies these instructions. If this level is already installed in the drive you've selected a message will let you know. A message also may come up to let you know that the Diskette(or Disk) does not have the previous level microcode file. This is true and is not required to complete the download.
PRESS "F7" to commit
8. You will receive a msg. "Current Microcode is....and...Download has completed successfully"
       (this may take a few minutes)
9. Return to the Tasks Selection menu and repeat this procedure for each hard disk that requires this microcode.
10. Exit diagnostic.

2.4.1.2.2 Standalone (Service Mode) Download

This procedure is used for all drives including rootvg or paging space drives
1. Properly shutdown the system.
2. Boot up the system in standalone diagnostics mode with the CDROM diagnostics(Use diagnostics level 4.21 or above; It is recommended to use the same level
    of Diagnostic CD as the AIX ).
3. Select the "Task Selection" from diagnostics menu.
4. Select "Microcode Download" from "Task Selection" menu.
5. Select resource that microcode will be applied to(hdisk?) and PRESS ENTER.
6. Press "F7" to commit.
      (The current microcode level of the resource you selected earlier will be displayed at the top of the screen)
7. Make the following selections on the next screen:
    Select Input Device --------------------------------------- [ diskette]
    Microcode level to download -----------------------------[ latest]
    Download latest level even if -----------------------------[ yes]
    current is missing

NOTE: A prompt will ask you to insert the microcode diskette into the floppy drive. Insert the diskette which accompanies these instructions. If this level is already installed in the drive you've selected a message will let you know. A message also may come up to let you know that the Diskette(or Disk) does not have the previous level microcode file. This is true and is not required to complete the download.
PRESS "F7" to commit
8. You will receive a msg. "Current Microcode is...." and "Download has completed successfully"
(this may take a few minutes)
9. Return to the Tasks Selection menu and repeat this procedure for each hard disk that requires this microcode.
10. Exit diagnostic and reboot system in normal mode.

2.4.2 SCSI Drives Attached to PCI RAID Adapter

NOTE: Please save current and older versions of the microcode update files in case you need to restore your system.

1. At AIX Command line type:
diag
2. Select the "Task Selection" from diagnostics menu.
3. Select "Microcode Download" from "Task Selection" menu.
4. Select RAID controller from the list of resources, PRESS ENTER, then F7 to commit
5. Select "Physical Disks" and PRESS ENTER
6. A list of all Physical Disks will be displayed, select the disk that needs to be upgraded, PRESS ENTER and F7 to commit.
7. Select "Latest level"
8. Select "Disk" if files are copied to /etc/microcode directory. Select "Diskette" if microcode files are saved onto a diskette, PRESS ENTER
(The current microcode level of the resource you selected earlier will be displayed at the top of the screen)

9. You will receive a message "Download has completed successfully" and "Current Microcode is" (this may take a few minutes).
10. Return to the Previous menu and repeat this procedure for each hard disk that requires this microcode.
11. Exit diagnostic and reboot system.

2.4.3 SP systems
This procedure requires copying microcode files to the appropriate SPOT(s). Therefore, it is HIGHLY recommended that someone with an appropriate level of AIX experience and expertise should perform this task, preferably the System Administrator of person(s) designated as responsible for making software updates to the system.

Warning: Do not power off the system or the drive during microcode download as this may permanently damage the disk drive

NOTE: Please save current and older versions of the microcode update files in case you need to restore your system.

Can microcode be installed Concurrently?
NO. If the disk is part of rootvg or used as a paging device, microcode download can ONLY be performed while node is "Network Booted" into "Diagnostic Standalone Mode".

Is system reboot needed to activate the microcode: Yes

Installation Time: Installation time will vary depending upon the system configuration

Procedure for SP System (Nodes):

Note: Make sure that node on which work is to be performed has been "fenced" from the switch.
1. Obtain proper microcode diskette from your IBM Service Representative.
2. Copy microcode file from diskette onto CWS:
restore -xvq
(file will be copied into the "etc/microcode" directory)

3. Move microcode file from "etc/microcode" directory to the appropriate Spot(s) that are used by the customer for the node(s) to be updated.
ie: /spdata/sys1/install/aix4??/spot/spot_aix4??/usr/lib/microcode (??= level of AIX on your system)

4. To set the Node(s) to boot from network, from CWS, run command:
spbootins -r diag [frame#] [node#] [node count]
(example - - spbootins -r diag 1 13 1)

5. From Perspectives, perform a "Shutdown" for the node(s) to be updated.
6. From perspectives screen for node to be updated, select "Network Boot" and wait for TTY to open to DIAG MENU.
7. Choose "Task Selection".
8. Choose your terminal type.
9. Select "Download Microcode"
10. Select resource that microcode will be applied to(hdisk?) and PRESS ENTER.
11. Press "F7" to commit.
(The current microcode level of the resource you selected earlier will be displayed at the top of the screen)
12. In the "Select the input device" screen, make sure settings are as follows:

      Select Input Device --------------------------------------- [ disk]
      Microcode level to download ----------------------------- [ latest]
      Download latest level even if ------------------------------ [ yes]
      current is missing

PRESS "F7" to commit

13. You will receive a msg. "Current Microcode is" and "Download has completed successfully"
(this may take a few minutes)

14. On CWS run the following command:
spbootins -r disk [frame# [node#] [node count]

15. On CWS, After spbootins finishes, run the following command:
splstdata -b (check output to see that node in question was set back to disk)

16. On "TTY" screen for node, Press F10 to get to "Shutdown Screen" and close TTY screen.
17. On perspectives screen of affected node, do a power off of the node and a power on of the node.
18. After node boots, telnet to the node, run the following command and check that correct microcode level has been updated.
lscfg -vl hdisk# (ie hdisk0,hdisk1 etc).

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

3. Linux Operating System

3.1 Linux 2.6 kernel(such as SuSE SLES 9 or RHEL 4)

Microcode can be updated using the iprconfig utility. The iprconfig utility

allows for multiple levels of adapter and device microcode to exist on the

system at the same time. After the device to update microcode is

selected, all available microcode levels are presented to choose to download.

a) If using SLES 9 base, install the package by typing:

rpm -ivh --ignoreos CH10K7-C70H-AIX.rpm

b) If using SLES 9 SP1 or better or RHEL 4 or better, install the package by typing:

rpm -ivh CH10K7-C70H-LINUX.rpm

2. Update the microcode by typing:

iprconfig

Press Enter.

3. Select Download microcode and press Enter.

4. Select the device you wish to update by typing a 1 then pressing Enter. Multiple devices may be selected.

5. Select the microcode image to be downloaded to the device by typing a 1 then pressing Enter.

6. Press Enter again to confirm the download (display shows “Microcode Download in Progress” with elapsed time)

7. If multiple devices were selected, repeat from Step 5 for the next device.

To check the microcode level:

1. Start iprconfig utility,

2. Select "Display hardware status" option.

3. Select disk to query by typing a 1 next to it and pressing "Enter"

4. Look at the "Firmware Version" field

--------------------------------------------------------------------------

3.2 RHEL 3:

Microcode can be updated using the iprupdate utility. If iprupdate finds newer

microcode on the system it will be downloaded to the disk.

1. Install the package by typing:

rpm -ivh --ignoreos CH10K7-C70H-AIX.rpm

Press Enter.

2. Update the microcode by typing:

iprupdate

Press Enter.

To check the microcode level:

1. Start iprconfig utility,

2. Select "Display disk hardware status" option.

3. Find the disk you wish to query and note its serial number.

4. Type "d" to get to the "Display disk unit details" screen.

5. Select disk to query by typing a 5 next to it and pressing "Enter"

6. Look at the "Firmware Version" field

-------------------------------------------------------------------------

3.3 SLES 8 SP4

Microcode can be updated using the sisupdate utility. If sisupdate finds newer

microcode on the system it will be downloaded to the disk.

1. Install the package by typing:

rpm -ivh --ignoreos CH10K7-C70H-AIX.rpm

Press Enter.

2. Update the microcode by typing:

sisupdate

Press Enter.

To check the microcode level:

1. Start sisconfig utility,

2. Select "Display disk hardware status" option.

3. Find the disk you wish to query and note its serial number.

4. Type "d" to get to the "Display disk unit details" screen.

5. Select disk to query by typing a 5 next to it and pressing "Enter"

6. Look at the "Firmware Version" field

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

4. Code level C708 Format Problem description and recovery procedure

A problem was found with the 10K RPM disk drives listed above with code level C708,

this problem was fixed in code level C70A and thereafter.

AIX “diag” format routine fails to format these drives.

After selecting "Format media" from Diagnostics "Task Selection" menu

and selecting one of these disk drive for format, a normal format

screen is displayed as below:

"Format Op Is In progress"

"Please Stand By"

"0% complete"

However, after about 30 Seconds, format command times out and the

following message is displayed:

"The Format operation has stopped"

"It is recommended that diagnostics be run on this disk drive."

The failure occurs only if drive is attached to a “PCI-X Dual Channel

Ultra320 SCSI Adapter” or “PCI-X Dual channel U320 SCSI Raid Adapter”,

AND only if SCSI bus speed is at U320 MB/sec. After format failure,

drive becomes format corrupt and unusable until one of the procedure

listed below is used to re-format the drive.

FIX:

If a drive becomes format corrupt, AIX Diag can not be used to format

the drive or download this new microcode. Use one of the following procedures below to get

around this problem and format these disk drives and download new microcode:

1- If drive is attached to “PCI-X Dual Channel Ultra320 SCSI Adapter”,

lower the SCSI bus speed and format the drive using AIX Diag format routine.

Note: To lower SCSI bus speed, find the “scsi#” that the drive is

attached to, then use smitty—devices--SCSI Adapters--Change/Show

Characteristics of a SCSI adapter. Highlight scsi# and change the

“Maximum SCSI bus speed” from U320 to U160. Then use AIX Diag format

routine to format the disk drive.

Also note that for SCSI bus speed change to take effect immediately,

SCSI controller (and all devices attached to it) must be in “defined”

state. If there are devices on the SCSI bus that are active and can

not be changed to “defined”, then use “Apply Change to Database Only”

and reboot the system for SCSI bus speed change to take effect.

2- If drive is attached to “PCI-X Dual channel U320 SCSI Raid Adapter”,

you can either use the procedure above, or you can use PCI-X Raid Manager

function in Smitty to format the drive to 522 Bytes sector and then back

to 512 bytes sector:

a. Use command Smitty pxdam

b. Choose “Create an array candidate pdisk and format to 522

Bytes Sector” and format the drive to 522 Bytes sector.

c. After format completion, use “change/Show PCI-X SCSI pdisk status”

and then choose “Delete an array candidate pdisk and format to 512 Byte sector”.