`Size`	`Sector Size`	`Disk Drive Model`	`FRU#`	`P/N (VPD)`	`Microcode File Name`	`Check` `sum`
960GB	4K	XS960SE70094	02YC646	02YC638	XS960SE.A1800022.34303835	59751
			02YC642	02YC634
1920GB	4K	XS1920SE70094	02YC647	02YC639	XS1920S.A1800022.34303835
			02YC643	02YC635
3840GB	4K	XS3840SE70094	02YC648	02YC640	XS3840S.A1800022.34303835
			02YC644	02YC636
7680GB	4K	XS7680SE70094	02YC649	02YC641	XS7680S.A1800022.34303835
			02YC645	02YC637
1920GB	512e-HMC	XS1920SE70094	03GM80	03GM801	XS1920S.A1800022.34303835

1.2 Microcode Change History

Release date	Code level	Impact/ Severity	Change Description
September 2022	4085	Function/ ATT	- Potential drive hang after Invalid back-to-back frames sent to the drive - Potential drive hang upon write-protect event due to system metadata write - LOGICAL UNIT RESET task management function stalls for OPEN REJECT on other port.
January 2022	4084	Function/ ATT	- Added 512e to 4K configuration -Fixed command timeout after unrecoverable read error -Fixed drive fail to come ready after FW download -Fixed drive assert after power cycle -Fixed drive hang in excessive read error condition
November 2020	4083	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:

#aix

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 U78D2.001.WZS0SXU-P2-D4 Physical SAS 4K Read Intensive Solid State Drive

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

Machine Type and Model......XS960SE70094

FRU Number..................02YC646

ROS Level and ID............34303835

Serial Number...............HSN031JG

EC Level....................P65469

Part Number.................02YC638

Device Specific.(Z0)........000007329F001002

Device Specific.(Z1)........12284085

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

Device Specific.(Z3)........20250

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

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

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

Hardware Location Code......U78D2.001.WZS0SXU-P2-D4 Hardware Location Code......U78C7.001.1AQH376-P4-D3 Hardware Location Code......U78C9.001.WZS0KX3-P2-D7If 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 "34303835", 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, 34 Hex= ASCII character "4"; 30 Hex= ASCII character "0"; 38 Hex=ASCII character "8"; 35 Hex=ASCII character "5", microcode level is "4085". Also note that the microcode level "4085" 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 nytro3732RI.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x nytro3732RI.bin
./nytro3732RI.bin
[Don't overlook the periods (.) in the above command.]

The directory nytro3732RI 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/nytro3732RI/XS* /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 nytro3732RI-4085-AIX.rpm

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

7- Display shows a list of microcodes available for the selected drive, highlight option "M XSxx...", 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 nytro3732RI-4085-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

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. tar -C-xzvf nytro3732RI–4085-LINUX.tgz

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.3 HMC - 512e drive used in 7063-CR2

Install arcconf command line utility:

1. Go to start.microsemi.com.

2. Under “Find your product” select the controller you are using

3. Select “Storage Manager downloads” under Storage Manager.

4. Download the ARCCONF Command Line Utility installation package.

5. When the download completes, extract the package contents to the installation directory on your machine. For example, if using Linux X64,the path to the file /linux_x64/arcconf

6. Make sure file is executable by running chmod +x arcconf

Run Microcode Download Command

Assuming arcconf is located in /path/arcconf and microcode file is located in /path/file

1. The command to download microcode is:

/path/arcconf imageupdate controller# device channel# device# chunksize# /path/file mode#

We need to find the controller# of your controller and the channel#, device#, and chunksize# of your disk. mode# = 7 if disk is SAS or 3 if it is SATA. In this case mode# = 7

2. If you’re using one controller(which is most likely the case) controller# = 1.

3. Now to find device# and channel#. This can be found by running another arcconf command. Plug in 1 for controller# and the serial number of your disk(case-sensitive) for serial#:

/path/arcconf getconfig controller# | grep “serial#”

You should see a line with the serial number of your disk, along with its channel and device number.

4. ChunkSize# must be a multiple of 512. In the case for Skybolt512e, chunksize# = 512.

5. Now that you’ve got your values, you can plug in and run the command. E.g Assuming controller# = 1, channel# = 0, device# = 1, and chunksize# = 512, and it is a SAS disk, it would look like this:

/path/arcconf imageupdate 1 device 0 1 512 /path/file 7