`Size`	`Disk Drive Model`	`FRU#`	`P/N (VPD)`	`Microcode File Name`	`Checksum`
`600GB`	AL14SXQ60EN	00E8653	00LY482	`AL14SXQ.A1800014.37313038`	`39627`
		00E8665	00LY524
		00E9914	00LY510
		02YC765	02YC757
`450GB`	AL14SXQ45EN	44V4432	00LY498
`300GB`	AL14SXQ30EN	74Y6496	00LY481
		74Y6498	00LY523
		00E9912	00LY509
		00LY429	00LY512
		10N7208	00LY497
		02YC764	02YC756
		03JG439	03JG438
`146GB`	AL14SXQ14EN	00E6169	00LY480
		00E6173	00LY522
		00FX876	00LY508
		10N7232	00LY496
		02YC761	02YC755
`73GB`	AL14SXQ07EN	00E6168	00LY479
`73GB`	AL14SXQ07EN	10N7230	00LY495

1.2 Microcode Change History

Release date	Code level	Impact/ Severity	Change Description
Dec. 2022	7108	Function/ ATT	-Added PN/FRU's for new drive tray (Kapton tape removal) -The following changes are made in drive FW to enhance drive's reliability a. Flatten lubricant on media with frequent patrol seek. b. Patrol seek interval is changed to 1 second from 80 second. c. Idle-B/C is disabled to prevent unload head. d. Setting for the last stage of emergency unload is changed in order to prevent head on media issue. e. Seek error recovery process is modified to reduce the opportunity which heads go to inner most diameter.
June 2020	7106	Function/ ATT	-Added DS8K PN/FRU -Changed to execute MODE SENSE command during SANITIZE command -Fix of a double post issue. If HDD receive command while HDD is executing Read Retry Step 50, HDD may execute internal reboot and report sense 06-29-04. -Fix of 02-04-02 report issue against MODE SENSE/SELECT command during a spin up by START STOP Unit command. At Power on sequence, HDD starts motor spindle up by receiving NOTIFY (ENABLE SPINUP).While AL14SX is becoming ready by receiving NOTIFY (Enable SpinUp) and STAR STOP UNIT command, there is error timing that AL14SX erroneously report sense 02/04/02 instead of 02/04/01 only for MODE SENSE and MODE SELECT command.
Feb 2019	7105	New/ New	Initial Release

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

2. AIX and VIOS(PowerVM Virtual I/O Server) Operating System

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)

hdisk2 U5887.001.G232002-P1-D2 SAS Disk Drive (300000 MB)

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

Machine Type and Model...... AL14SXQ30EN

FRU Number..................74Y6496

ROS Level and ID............ 37313038

Serial Number...............xyz

EC Level....................P02080

Part Number................. 00LY481

Device Specific.(Z0)........000006329F003002

Device Specific.(Z1)........10317108

Device Specific.(Z2)........0021

Device Specific.(Z3)........16183

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

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

Device Specific.(Z6)........P02080

Hardware Location Code......U5887.001.G232002-P1-D2

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 "37313038", this microcode applies.

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, 37 Hex= ASCII character "7"; 31 Hex= ASCII character "1"; 30 Hex=ASCII character "0"; 38 Hex=ASCII character "8", microcode level is "7108 ". Also note that the microcode level "7108" 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 isAL14SX5xx.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x AL14SX5xx.bin
./AL14SX5xx.bin
[Don't overlook the periods (.) in the above command.]
The directory AL14SX5xx 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/ AL14SX5xx/AL14SX* /etc/microcode

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 AL14SX5xx–7108-AIX.rpm

c) Unpack the file by executing the instructions below:
Enter the commands:
rpm -ihv --ignoreos --force AL14SX5xx–7108-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/

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

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

- 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

7- Display shows a list of microcodes available for the selected drive, highlight option "M AL14SXxx...", 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 AL14SX5xx–7108-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