`Size`	`Disk Drive Model`	`FRU#`	`P/N (VPD)`	`Microcode File Name`	`Checksum`
`960GB`	WUSTR1596ASS200	01LU898	01LU890	WUSTR15.A180001D.52345634	`31545`
		01LU902	01LU894
`1.92TB`	WUSTR1519ASS200	01LU899	01LU891
		01LU903	01LU895
`3.84TB`	WUSTR1538ASS200	01LU900	01LU892
		01LU904	01LU896
`7.68TB`	WUSTR1576ASS200	01LU901	01LU893
		01LU905	01LU897

Medium Endurance (ME, 10 DWPD ) 528 Block Size

`Size`	`Disk Drive Model`	`FRU#`	`P/N (VPD)`	`Microcode File Name`	`Checksum`
`400GB`	WUSTM3240ASS200	01LU845	01LU843	`WUSTM32.A180001D.52345634`	`31545`
		01LU861	01LU851
		01LU863	01LU853
`800GB`	WUSTM3280ASS20	01LU844	00VN355
		01LU862	01LU852
		01LU864	01LU854

Medium Endurance (ME, 10 DWPD ) 4K Block Size

`Size`	`Disk Drive Model`	`FRU#`	`P/N (VPD)`	`Microcode File Name`	`Checksum`
`400GB`	WUSTM3240ASS200	01LU868	01LU858	`WUSTM32.A180001D.52345634`	`31545`
		01LU865	01LU855
`800GB`	WUSTM3280ASS200	01LU869	01LU859
		01LU866	01LU856
`1600GB`	WUSTM3216ASS200	01LU870	01LU860
		01LU867	01LU857

1.2 Microcode Change History

Release date

Code level

Severity/

Impact

Change Description

Jan 2020

R4V4

Function/

ATT

- Corrected behavior of LED when drive is Format Corrupt
- Fix issue of drive not coming up in updated code after a power cycle following multiple fast downloads.
- Fixed an issue where Uncorrectable Errors caused by issuing Write Long w/UNCOR=1 were incorrectly being included in the counts with real uncorrectable errors.

- Fixed a timing condition in which the priority thread may use the port information from the HW slot that that already been invalidated.

May 2019

R4V2

New/New

Initial Release

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

2. Microcode Download Procedure-AIX and VIOS(PowerVM Virtual I/O Server) OS

Note: For VIOS systems, microcode of shared physical I/O resources can only be updated from VIOS partition.

To update disk drive microcode, from VIOS partition, enter the following command:

oem_setup_env

Then follow the instruction in section 2.3 to transfer/extract the microcode file, and section 2.4.1 to update the disk drive code.

2.1 Installation Time

Approximately 20 minutes if using Diagnostics CD; Approximately 5 minutes/drive using AIX concurrent diagnostics.

2.2 Determine Drive Model, FRU&PN and Current Microcode Level
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

Vital Product Data (VPD)

Pdisk0 UESLS.001.G86S022-P1-D13 Physical SAS Solid State Drive

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

Machine Type and Model......WUSTM3240ASS201

FRU Number..................01LU861

ROS Level and ID............52345634

Serial Number...............V6V03P2A

EC Level....................P65454

Part Number.................01LU851

Device Specific.(Z0)........000007329F003002

Device Specific.(Z1)........BPIPR4V4

Device Specific.(Z2)........0068

Device Specific.(Z3)........18352

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

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

Device Specific.(Z6)........P65454
Hardware Location Code......UESLS.001.G86S022-P1-D13

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, 52 Hex= ASCII character "R"; 34 Hex= ASCII character "4"; 56 Hex=ASCII character "V"; 34 Hex=ASCII character "4", microcode level is "R4V4". Also note that the microcode level "R4V4" is displayed in “Z1” field.

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 SSD530.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x SSD530.bin
./SSD530.bin
[Don't overlook the periods (.) in the above command.]

The directory SSD530 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/ SSD530/* /etc/microcode

e- If you are using stand alone AIX diag (bootable USB flash or CD/DVD) to update drive’s microcode, transfer microcode files to a USB drive and place it in “/etc/microcode” directory.
Please refer to this page for USB flash drive usage
https://www.ibm.com/support/pages/using-and-taking-advantage-usb-devices-and-aix

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.
You'll see the filename is SSD530-R4V4-AIX.rpm

c) Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv --ignoreos --force SSD530-R4V4-AIX.rpm ;(please note, there are two dashes)

The file size and checksum will be verified.

The microcode files will be added to /etc/microcode/
d) If you are using stand alone AIX diag (bootable USB flash or CD/DVD) to update drive’s microcode, transfer microcode files to a USB drive and place it in “/etc/microcode” directory.
Please refer to this page for USB flash drive usage
https://www.ibm.com/support/pages/using-and-taking-advantage-usb-devices-and-aix

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

2.4 Microcode Download Procedure

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
Is system reboot needed to activate the microcode: Yes if stand alone diagnostics CD 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 concurrent diagnostics is used.

2.4.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
                      usb mass storage    (ISO 9660 file system format)

- Use /etc/microcode if microcode file is in the system
- Use “usb mass storage” if using usb flash drive

7- Display shows a list of microcodes available for the selected drive, highlight option "M xx...", 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.2 Standalone (Service Mode) Download
Use similar steps as above when booting from a Diagnostics CD

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

3. Linux Operating System

3.1 ReadHat (RHEL) and SLES

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.

1. If using SLES 9 base, install the package by typing:

rpm -ivh --ignoreos SSD530-R4V4-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 Ubuntu