Microcode Update for PM6-ME
Models: KPM6VMUG400G KPM6VMUG800G KPM6VMUG1T60
400/800/1600 GB
2.5” SFF
SAS Solid State Drive (SSD)
Microcode Level 9007
DATE: May 19, 2022
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 |
KPM6VMUG400G |
02YC680 |
02YC668 |
KPM6VMU.A1800023.39303037 |
58519 |
02YC677 |
02YC665 |
|||||
5xx |
||||||
02YC673 |
02YC718 |
|||||
02YC675 |
02YC717 |
|||||
800GB |
4K |
KPM6VMUG800G |
02YC681 |
02YC669 |
||
02YC678 |
02YC666 |
|||||
5xx |
02YC674 |
02YC719 |
||||
02YC676 |
02YC664 |
|||||
1600GB |
4K |
KPM6VMUG1T60 |
02YC682 |
02YC670 |
||
02YC679 |
02YC667 |
Release date |
Code level |
Impact/ Severity |
Change Description |
May 2022 |
9007 |
Data/ HIPER |
This Firmware update is
required on the listed drives to prevent undetected data loss. Undetected
data loss can occur in rare cases when data on a drive is being cleared. While there is no known
occurrence on IBM systems for data corruption for this issue, due to the
possibility of undetected data corruption, it is recommended that this code
be loaded immediately |
February 2022 |
9006 |
Availability/ ATT |
The change in this level of
microcode only affects IBM MFG process, no functional change in this code
level Fix SN: changed Bytes
98-101 in Standard Inquiry Data from "11S " to "11S0" |
Dec 2021 |
9005 |
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)
hdisk1 U5887.001.G1AR010-P1-D9 SAS Solid State Drive (400000 MB)
Manufacturer................IBM
Machine Type and
Model......KPM6VMUG400G
FRU
Number..................02YC673
ROS Level and
ID............39303037
Serial
Number...............TSJNKFJ2
EC
Level....................P65470
Part
Number.................02YC718
Device
Specific.(Z0)........000007329F001002
Device
Specific.(Z1)........900790079007
Device
Specific.(Z2)........11S
Device
Specific.(Z3)........21014
Device
Specific.(Z4)........
Device Specific.(Z5)........22
Device
Specific.(Z6)........P65470
Hardware Location
Code......U5887.001.G1AR010-P1-D9
If 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 “
For example in VPD
displayed above, 39 Hex= ASCII
character "9"; 30 Hex= ASCII character "0"; 30 Hex=ASCII character "0";
37 Hex=ASCII character "7",
microcode level is "9007".
Also note that the microcode level "9007"
is displayed in “Z1” field.
===============================================================
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 PM6-ME.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x PM6-ME.bin
./PM6-ME.bin
[Don't overlook the periods (.) in the above command.]
The directory PM6-ME 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/PM6-ME* /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 PM6-ME-9007-AIX.rpm
c) Unpack the file by
executing the instructions below:
Enter the commands:
rpm -ihv --ignoreos --force PM6-ME-9007-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
KP...", 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 PM6-ME-9007-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 PM6-ME-9007-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