Table of Contents

1.0 Disk Drives Affected

2.0 Microcode Change History

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 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:

This microcode is for the following IBM SCSI hard disk drive:

                                        FRU # or          Assembly
Size              Model               FRU ASM#          P/N
--------------    -------------       -------------     --------
9.1GB (68 Pin)    DPSS-30917N         07N3675           07N3721
9.1GB (68 Pin)    DPSS-30917N         31L8768(ASM)      07N3723
9.1GB (68 Pin)    DPSS-30917N         03N3873(ASM)      07N3722
9.1GB (80 Pin)    DPSS-30917M         03N3301(ASM)      07N3752

18.2GB(68 Pin)    DPSS-318350N        07N3674           07N3711
18.2GB(68 Pin)    DPSS-318350N        31L8770(ASM)      07N3713
18.2GB(68 Pin)    DPSS-318350N        03N3874(ASM)      07N3712
18.2GB(80 Pin)    DPSS-318350M        03N3302(ASM)      07N3742
 

2.0 Microcode Change History
 

Release date	Change Description
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:  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 background 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

NOTE: It is strongly recommended to update drive microcode to S9RA if current level is S96F or below to improve drive reliability.  However, if current level is S9HA, it is not recommended to update microcode. There are only minor changes from microcode level S9HA to S9RA, and these changes does not affect reliability of the disk drive.
 

3.0.0 General information

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 hdisk2

DEVICE    LOCATION        DESCRIPTION
hdisk9            10-78-00-12,0     16 Bit LVD SCSI Disk Drive (9100 MB)

        Manufacturer.........................IBM
        Machine Type and Model......DPSS-309170N
        FRU Number........................07N3675
        ROS Level and ID................53395241
        Serial Number.......................ZD025006
        EC Level.........................F79851
        Part Number....................07N3721
        Device Specific.(Z0)........000003029F00013A
        Device Specific.(Z1)........07N4912
        Device Specific.(Z2)........0933
        Device Specific.(Z3)........00036
        Device Specific.(Z4)........0001
        Device Specific.(Z5)........22
        Device Specific.(Z6)........F79851

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 below "53395241", this microcode applies.If this level is already installed then the "ROS Level and ID...."  shows:  "53395241"
Note: Drive microcode level is displayed in Hex value of ASCII charactors in VPD data. Each alpha-numeric ASCII charactor converts to a 2-digit hex  number.  For example in VPD displayed above, 53 Hex= ASCII chractor S;  39 Hex= ASCII charactor 9 ; 52 Hex=ASCII charactor R; 41 Hex=ASCII charactor A, the  Microcode level is S9RA.

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" is DPSS , and ROM/RAM Fields are below S9HA, then microcode of drive(s) need to be updated

c- SP Systems

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 (9100 MB)
pesp_n1:         ROS Level and ID............53395241
pesp_n1:         Part Number.................07N3821
pesp_n5:   hdisk0            10-60-00-0,0      16 Bit LVD SCSI Disk Drive (9100 MB)
pesp_n5:         ROS Level and ID............53395241
pesp_n5:         Part Number.................07N3821
pesp_n5:   hdisk1            10-60-00-8,0      16 Bit LVD SCSI Disk Drive (9100 MB)
pesp_n5:         ROS Level and ID............53395241
pesp_n5:         Part Number.................07N3821
 

a) Make a directory on an AIX system to receive the AIX format file.
    Enter:      mkdir /tmp/fwupdate
   Note: If the directory /tmp/fwupdate already exists, make sure it is empty before proceeding.
b) Transfer the AIX format file to the /tmp/fwupdate directory (using "Save as ...").
    You'll see the filename is dpss.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 dpss.bin
  ./dpss.bin
[Don't overlook the periods (.) in the above command.]

The directory dpss with these files will be added to /tmp/fwupdate.

DPSS-30.415A3030.53395241
DPSS-30.415A3031.53395241
DPSS-30.415A3033.53395241
DPSS-30.415A3032.53395241

DPSS-31.415A3030.53395241
DPSS-31.415A3031.53395241
DPSS-31.415A3033.53395241
DPSS-31.415A3032.53395241
dpss.txt

Note: dpss.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/dpss/DPSS*  /etc/microcode

e- Follow the procedure below to copy these file onto 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.

Diskette 1:
Enter command
ls /etc/microcode/DPSS-30*53395241 | backup -ivf /dev/rfd0
This will produce AIX backup diskettes. Label the diskettes:
" DPSS 9.1GB Microcode Level S9RA"

Diskette 2:
Enter command
ls /etc/microcode/DPSS-31*53395241 | backup -ivf /dev/rfd0
This will produce AIX backup diskettes. Label the diskettes:
" DPSS 18.2GB Microcode Level S9RA"

The following microcode files are included in the diskettes, use the list below for cross reference:
                                                                  FRU # or               Assembly
  Size                      Model                     FRU ASM#              P/N               Microcode File Name
-------------------    --------------------       -------------              --------------     --------------------------------------
9.1GB (68 Pin)    DPSS-30917N          07N3675                07N3721        DPSS-30.415A3030.53395241
9.1GB (68 Pin)    DPSS-30917N          31L8768(ASM)    07N3723        DPSS-30.415A3031.53395241
9.1GB (68 Pin)    DPSS-30917N          03N3873(ASM)    07N3722        DPSS-30.415A3033.53395241
9.1GB (80 Pin)    DPSS-30917M         03N3301(ASM)    07N3752        DPSS-30.415A3032.53395241

18.2GB(68 Pin)   DPSS-318350N      07N3674                   07N3711       DPSS-31.415A3030.53395241
18.2GB(68 Pin)   DPSS-318350N      31L8770(ASM)       07N3713       DPSS-31.415A3031.53395241
18.2GB(68 Pin)   DPSS-318350N      03N3874(ASM)      07N3712        DPSS-31.415A3033.53395241
18.2GB(80 Pin)   DPSS-318350M     03N3302(ASM)      07N3742        DPSS-31.415A3032.53395241

5.0.1 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

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

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

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?
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: Yes

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

Procedure:
1. Properly shutdown the system.
2. Boot up the system in SERVICE 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 will also come up because the diskette does not have the previous level microcode on the diskette. 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.
 

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

Is system reboot needed to activate the microcode: Yes

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

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

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 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)