Microcode Update for Nytro 3731
Models: XS400ME70014 XS800ME70014 XS1600ME70014
400/800/1600 GB
2.5” SFF
SAS Solid State Drive (SSD)
Microcode Level E096
DATE: April 1, 2021
Table of Contents
2.
AIX and VIOS(PowerVM Virtual I/O Server) Operating System
2.2 Determine Drive Model,
FRU&PN and Current Microcode Level
2.3 Transferring and Unpacking
the Microcode Update Package
2.3.1 Internet AIX self
extracting file (.bin)
2.4 Microcode Download
Procedure
===============================================================
The Microcode
files provided in this package are for SAS disk drives used in
Below is the list of
microcode files in this package:
NOTE: To insure the integrity of microcode files, please make sure the checksum value is correct after extraction
Size |
Sector
Size |
Disk Drive Model |
FRU# |
P/N
(VPD) |
Microcode
File Name |
Check sum |
400GB |
4K |
XS400ME70014 |
01LU931 |
01LU925 |
XS400ME.A180001E.45303936 |
44196 |
01LU928 |
01LU922 |
|||||
5xx |
01LU958 |
01LU956 |
||||
01LU918 |
01LU914 |
|||||
01LU920 |
01LU916 |
|||||
800GB |
4K |
XS800ME70014 |
01LU932 |
01LU926 |
XS800ME.A180001E.45303936 |
|
01LU929 |
01LU923 |
|||||
5xx |
01LU959 |
01LU957 |
||||
01LU919 |
01LU915 |
|||||
01LU921 |
01LU917 |
|||||
1600GB |
4K |
XS1600ME70014 |
01LU933 |
01LU927 |
XS1600M.A180001E.45303936 |
|
01LU930 |
01LU924 |
Release date |
Code level |
Impact/ Severity |
Change Description |
April 2021 |
E096 |
Function/ ATT |
This level of microcode has fix for the
following issue: Command I/O Time Out due to improper retention
scan if drive receives very few write commands in 6 month or more |
November 2020 |
E095 |
Usability/ ATT |
Minor FW fixes: Incorrect unrecovered status returned for
recovered read Drive reports 03/3100/99 on IO to unsupported
block size Max power behavior not reflected in mode page
0x1A |
May 2020 |
E091 |
Function/ ATT |
This level of microcode has fix for the
following issues: - Drive reports format corrupt if power cycled
during format or sanitize operation |
January 2020 |
E089 |
Function/ ATT |
Fixed: During a long running read workload there
is a low chance the drive may hang and go unresponsive. Power cycling the
drive leads to a scram failure and format corrupt state |
November 2019 |
E088 |
NEW/ NEW |
Initial Release |
===============================================================
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.
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)
pdisk1 U78C9.001.WZS0KX3-P2-D7 Physical SAS Solid State Drive
Manufacturer................IBM
Machine Type and
Model......XS800ME70014
FRU
Number..................01LU921
ROS Level and
ID............45303936
Serial
Number...............HLK033EZ
EC
Level....................P65456
Part
Number.................01LU917
Device Specific.(Z0)........000007329F003002
Device Specific.(Z1)........0924E096 ß-- Microcode level
Device Specific.(Z2)........0021
Device Specific.(Z3)........19103
Device Specific.(Z4)........
Device Specific.(Z5)........22
Device Specific.(Z6)........
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
Note:
Drive microcode level in “
===============================================================
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 nytro3731.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x nytro3731.bin
./
nytro3731.bin
[Don't overlook the periods (.) in the above command.]
The directory nytro3731 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/nytro3731/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
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
Enter: mkdir
/tmp/microcode
b) Transfer the
You'll see the filename is nytro3731-E096-AIX.rpm
c) Unpack the file by
executing the instructions below:
Enter the commands:
rpm -ihv
--ignoreos --force nytro3731–E096-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
========================================================
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
======================================================
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 nytro3731-E096-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
--------------------------------------------------------------------------
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 nytro3731–E096-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