IBM
pSeries Microcode Update for Cheetah 73LP Model
ST3xxx05LW/LC
9.1/18.2/36.4/73.4 GB
M/T 2104 MODELS
DU3/TU3 (SCALLOP)
DATE:
Table of Contents
4.0 Determine Drive Model, FRU&PN and Current Microcode level
5.0.0 Downloading and
Unpacking the Firmware Update Package From WEB
5.0.1 Downloading the RPM Format
File to the Target Server
5.0.2 Downloading Files from the Microcode CD-ROM
6.0.0 Microcode Download
Procedure-SCSI Drives Attached to SCSI Adapter - Non SP systems
6.0.1 Microcode Download
Procedure-SCSI Drives Attached to RAID Adapter
6.0.2 Microcode Download
Procedure-SP systems
===================================================================================
1.0 Disk Drives
Affected:
The microcodes in this package applies ONLY to the following IBM SCSI hard disk drive FRU/PN's (pSeries systems), it does not apply to any other drives even if they have the same model as these drives:
Size
Model FRU # Drive P/N
--------------
---------- ------------------ ------------------
9.1GB (80 Pin)
ST318305LC 07K8180 or 07K9446 07K8176 or 07K9444
18.2GB(80 Pin) ST318305LC 07K8181 or 07K9450 07K8177 or 07K9448
36.4GB(80 Pin) ST336605LC 07K8182 or 07K9454 07K8178 or 07K9452
73.4GB(80 Pin)
ST373405LC 07K8183 or 07K9458 07K8179 or 07K9456
|
Release date |
MC Level |
Change Description |
|
|
C70A (C74A, 9GB) |
This level of code enables a feature that clears busy condition in rare situations that drive reports busy status. |
|
|
C707 (C747, 9GB) |
Fixed Cheetah drive and AIX 4.33 ML<5 incompatibility problem. |
|
|
C705 (C745, 9GB) |
Fixed I/O Timeout after Download, small number of drive hanged the SCSI bus after code download. Fixed spin-up problem, a very small number of drives would not spin-up when installed vertically. |
|
|
C704 (C744, 9GB) |
Initial Release version |
SUBJECT: IBM pSeries Cheetah 73LP Microcode level C70A for 18.2/36.4/73.4
GB drives and
Microcode level C74A for 9.1 GB drive
******* PLEASE READ THIS ENTIRE NOTICE *********
Determine Drive Model, FRU&PN and Current Microcode
level:
a- SCSI Drives attached to SCSI Controllers(Not
RAID)
To see the drive type and current microcode level, Execute the following
command:
lscfg -vl hdisk* |pg
Example of the info on a 18.2GB SCSI hard
disk:
lscfg -vl hdisk1
DEVICE LOCATION DESCRIPTION
hdisk1 10-68-00-13,0 16 Bit LVD SCSI Disk Drive (18200MB)
Manufacturer................IBM
Machine Type and
Model......ST318305LC
FRU Number..................07K8181
ROS Level and ID............43373041
Serial Number...............3JK0031Q
EC Level....................0H11333
Part Number.................07K8177
Device
Specific.(Z0)........000003129F00013E
Device Specific.(Z1)........1109C70A
Device Specific.(Z2)........1000
Device Specific.(Z3)........01309
Device Specific.(Z4)........0001
Device Specific.(Z5)........22
Device Specific.(Z6)........162870 C
If the data returned in the "Part Number" field matches the one listed
above AND the "ROS Level and ID...." field of that data is
"43373041" or below [(43373441 or below for 9.1GB drives)], this
microcode applies. If this level is already installed then the "ROS
Level and ID...." shows:
"43373041" ["43373441" for 9.1GB drive)].
Note: Drive microcode level 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"; 41 Hex=ASCII character
"A", therefore the microcode level is C70A. Also note that last four
digits of field "Device Specific.(Z1)........1109C70A"
shows drive's microcode level.
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 (18200MB)
pesp_n1:
ROS Level and ID............43373041
pesp_n1:
Part Number.................07K8177
pesp_n5:
hdisk0
10-60-00-0,0 16 Bit LVD SCSI Disk Drive (18200MB)
pesp_n5:
ROS Level and ID............ 43373041
pesp_n5:
Part Number.................07K8177
pesp_n5:
hdisk1
10-60-00-8,0 16 Bit LVD SCSI Disk Drive (18200MB)
pesp_n5:
ROS Level and ID............ 43373041
pesp_n5:
Part Number.................07K8177
b- SCSI Drives attached to 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.
If "Product Type"+"Model Number"
is ST3xxxx5 (where xxxx is drive capacity, refer to
the table above), and ROM+RAM is C70A or below [(C74A or below for 9GB)], then this microcode can be applied.
5.0.0
Downloading and Unpacking the Firmware Update Package From
the WEB
NOTE: The following values apply to this microcode file:
ST31830.53433138.43373041 Size: 622,592 Checksum: 53192
ST33660.53433336.43373041 Size: 622,592 Checksum: 12725
ST37340.53433733.43373041
Size: 622,592 Checksum: 15487
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 the /tmp/fwupdate
directory (using "Save as ...").
You'll see the filename is ch73lpA.bin
c) Unpack the file by executing the instructions below. You will be asked for
the password from the license agreement.
Enter the commands:
cd /tmp/fwupdate
chmod +x ch73lpA.bin
./ch73lpA.bin
[Don't overlook the periods (.) in the above command.]
The directory ch73lpA with these files will be added to /etc/microcode.
ST31830.53433039.43373441
ST31830.53433138.43373041
ST33660.53433336.43373041
ST37340.53433733.43373041
ch73lpA.txt
Note: ch73lpA.txt is a read me file (same as this file), it can be saved or printed for future use.
d-Enter the following command to copy the microcode files to " /etc/microcode " directory :
cp /tmp/fwupdate/ch73lpA/ST*41
/etc/microcode
e- Do this step if you want to copy microcode files onto a diskettes
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/ microcode_filename | backup
-ivf /dev/rfd0
where microcode_filename is
microcode file that is needed, for example:
ls /etc/microcode/ ST31830.53433138.43373041 | backup -ivf /dev/rfd0
The following microcode files are included in this package, use the list below for cross reference:
Size Assembly
Model
FRU #
DRIVE P/N
Microcode File Name
-------------- ----------
------------------ ------------------
-------------------------
9.1GB (80 Pin) ST318305LC 07K8180 or 07K9446 07K8176 or 07K9444 ST31830.53433039.43373441
18.2GB(80 Pin) ST318305LC 07K8181 or 07K9450 07K8177 or 07K9448 ST31830.53433138.43373041
36.4GB(80 Pin) ST336605LC 07K8182 or 07K9454 07K8178 or 07K9452 ST33660.53433336.43373041
73.4GB(80 Pin) ST373405LC 07K8183 or 07K9458 07K8179 or 07K9456 ST37340.53433733.43373041
5.0.1
Downloading the RPM Format File to the Target Server
Use this method to download to an AIX system:
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 /etc/microcode directory (using
"Save as ...").
You'll see the filename is 2104_ch73lp-C70A.rpm
c) Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv
--ignoreos 2104_ch73lp-C70A.rpm
The file size and checksum will be verified.
The microcode files will be added to /etc/microcode/
5.0.2 Downloading File from the Microcode 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 the location specified in the individual
ReadMe file for the microcode being copied. Please reference the ReadMe
for the files being copied for more details.
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.
6.0.0 Microcode Download Procedure-SCSI Drives Attached to SCSI adapter - Non SP Systems
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 micro code be installed Concurrently?
AIX level 5.1 and above will allow concurrent download of microcode to all
drives in the system, including rootvg drive(s) as
long as drive is not busy.
For AIX levels 4.3.3 and below, if the disk is part of rootvg, microcode download can ONLY be performed in service
mode using diagnostics CD, if disk is not part of rootvg,
microcode download can be performed concurrently as long as drive is not in
use.
Is system reboot needed to activate the microcode:
Drive microcode will be updated and drive will function properly after a
successful microcode download operation.
However, to see correct microcode level in VPD, system needs to be rebooted(for rootvg drive), or
drive needs to be removed and reconfigured after microcode download(i.e; rmdev -l hdisk1 followed
by mkdev -l hdisk1)
Installation Time: Approximately 30 minutes CE Time; Approximately 15 minutes System Time
Procedure(AIX level 4.33 and
below):
a- Online(Concurrent) Diagnostics(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.
b- Standalone Diagnostics (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.
Procedure (AIX level 5.1 and above):
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?) 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 avilable for use..... "
Press enter to continue
6. Select the source for microcode, use arrow key to go up/down, use
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 avilable for the selected drive, highlight option "M ST3xxx...", the latest microcode for the drive listed below 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).
6.0.1
Microcode Download Procedure-SCSI Drives Attached to RAID 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? yes
Disk drives attached to RAID controllers are not part of rootvg,
therefore microcode download can be performed cuncurrently.
Is system reboot needed to activate the microcode: Yes
Installation Time: Approximately 30 minutes CE Time; Approximately 15 minutes System Time
Procedure:
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 "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.
6.0.2 SCSI
Disk Drive Microcode Download Procedure-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.
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?
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 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)