IBM Microcode
Update for Ultrastar DDYS 9.1/18.2/36.4GB
DISCOVERY in 2104
EXPANDABLE STORAGE PLUS Models DU3/TU3
SCSI Hard Disk
Drive Microcode Level SB0A
DATE: August 23, 2002
REVISED: May 8, 2003
Table of Contents
3.0.0
General Information
3.0.1
Installation Time
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 File 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:
This microcode is for use in the following SCSI hard disk drive:
Size
Model
FRU ASM Assembly
P/N P/N
-------------- ------------
------- --------
9.1GB (80 Pin) DDYS-T09170M
07K7410 07K7408
18.2GB(80 Pin) DDYS-T18350M
07K7406 07K7404
36.4GB(80 Pin) DDYS-T36950M
07K7402 07K7400
Release date | Change Description |
8/2002 | Code level SB0A,
Reliability enhancement to improve the idle time sweep algorithm and optimize track following. Enhancement were also made to the drive's Predictive Failure Analysis (PFA) algorithm where the the warning from the drive will be tripped earlier than before when it see hard read and write errors. |
9/2001 | Code Level S9RA,
1- Reset Monitor Process: Reset handling were developed to further reduce the potential of a drive hanging the SCSI bus.A new timer process that monitors SCSI reset was added. 2- Apply same write ERP(Error Recovery Procedure) steps for reserved area as user data area. |
5/2001 | Code evel S9HA:
1- In microcode level S96F, Drive idle time functions--which include surface safe sweep functions--are only invoked after 10 continues minutes of drive idle time. System functions in certain configurations/RAID environments can prevent the drives from going into safe sweep function due too frequent because read ops performed as part of RAID parity checking, etc happens every 10 to 20-seconds . In microcode S9HA, drive idle time function as described above is invoked after accumulating 120 of 5second idle periods, instead of the default of 10 minutes continuous idle time. |
10/2000 | Code level S96F: Fixes and enhancement to improve disk drive reliability
and logic changes to prevent conditions that may result in a possible
error that could overwrite sectors of data. |
8/2000 | Code level S93H-Original Release |
SUBJECT: IBM (Ultrastar
DDYS) 9.1/18.2/36.4 GB SCSI Hard Disk Drive
in 2104 EXPANDABLE
STORAGE PLUS Models DU3/TU3
Microcode Update
Level SB0A
******* PLEASE READ THIS ENTIRE NOTICE *********
Microcode update for the SCSI hard disk drives
Package Owner:
IBM RS/6000 Division I/O Development Engineering-Austin,
Texas
Roger Mason - Roger Mason/Austin/IBM@IBMUS
Notes short name - rmason
Internet - rmason@us.ibm.com
This
package contains microcode files ONLY for DDYS model drives in
2104 DU3/TU3 external SCSI storage subsystems,
it
does NOT include files for pSeries systems internal disk drives
NOTE: Please verify the following
values for this microcode file: 2104_ddys-SB0A.rpm
DDYS-T0.524D3031.53423041
Size: 294909 Checksum: 47008
DDYS-T1.524D3031.53423041
Size: 294909 Checksum: 47008
DDYS-T3.524D3031.53423041
Size: 294909 Checksum: 47008
3.0.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).
4.0
Determine the 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 9.1GB SCSI hard disk:
lscfg -vl hdisk16
DEVICE LOCATION DESCRIPTION
hdisk16 30-69-00-9,0 16 Bit LVD SCSI Disk Drive (36400 MB)
Manufacturer.........................IBM
Machine Type and Model......DDYS-T36950M
FRU Number........................07K7402
ROS Level and ID................53423041
Serial Number.......................TFL43981
EC Level...............................F80151
Part Number.........................07N5834
Device Specific.(Z0).............000003029F00013A
Device Specific.(Z1).............07N4923
Device Specific.(Z2).............0933
Device Specific.(Z3).............00076
Device Specific.(Z4).............0001
Device Specific.(Z5).............22
Device Specific.(Z6).............F80151
Note: "53423041" is hex coded ASCII characters "SB0A"
dsh -a lscfg -v |egrep 'hdisk|ROS|Part'
pesp_n1:
hdisk0
10-60-00-0,0 16 Bit LVD SCSI
Disk Drive (9100 MB)
pesp_n1:
ROS Level and ID............53423041
pesp_n1:
Part Number.................07K7408
pesp_n5:
hdisk0
10-60-00-0,0 16 Bit LVD SCSI
Disk Drive (9100 MB)
pesp_n5:
ROS Level and ID............53423041
pesp_n5:
Part Number.................07K7408
pesp_n5:
hdisk1
10-60-00-8,0 16 Bit LVD SCSI
Disk Drive (9100 MB)
pesp_n5:
ROS Level and ID............53423041
pesp_n5:
Part Number.................07K7408
At AIX command line, type:5.0.0 Downloading and Unpacking the Firmware Update Package From WEB
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 Diak drives attached to the RAID adapter.
If "Product Type" is DDYS , and ROM/RAM Fields are below SB0A, then microcode of drive(s) need to be updated
The directory ddys with these files will be added to /etc/microcode.
DDYS-T0.524D3031.53423041
DDYS-T1.524D3031.53423041
DDYS-T3.524D3031.53423041
ddysSB0A.txt
Note: ddysS80A.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 /etc/microcode/ddys/DDYS*
/etc/microcode
e- Copy microcode file
onto floppy 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/
DDYS-T0.524D3031.53423041
| backup -ivf /dev/rfd0
The following microcode files are included in the diskettes, use the list below to find the right file for you disk drive.
Size
Model
FRU # or Assembly
FRU ASM# P/N
Microcode File Name
-------------- ------------
------- ------- -------------------------
9.1GB (80 Pin) DDYS-T09170M
07K7410 07K7408 DDYS-T0.524D3031.53423041
18.2GB(80 Pin) DDYS-T18350M
07K7406 07K7404 DDYS-T1.524D3031.53423041
36.4GB(80 Pin) DDYS-T36950M
00K7402 07K7400 DDYS-T3.524D3031.53423041
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 /etc/microcode
b) Transfer the RPM
format file to the /etc/microcode directory (using "Save as ...").
You'll see the filename is 2104_ddys-SB0A.rpm
c) Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv --ignoreos 2104_ddys-SB0A.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 "/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.
6.0.0 Microcode Download Procedure-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.
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, 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 DDYSxxx...", 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
NOTE: Please save current and older versions of the microcode update files in case you need to restore your system.
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
"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.
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 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).