-
Microcode for CM6-ME
U.2 NVMe SSD
800/1600/3200/6400 GB
Microcode Level C9S5
DATE: November 16, 2023
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.1
Internet AIX self extracting file (.bin)
2.4
Microcode Download Procedure
3.1
Determine the Current Microcode Level for Linux:
3.2
Downloading and Unpacking the Firmware Update Package
3.3
Verifying microcode before download and notes
3.4
Microcode Download Procedure-NVMe Adapters for Linux
===============================================================
The Microcode
files provided in this package are for NVMe drives used in
with AIX or
Linux operating systems
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 |
NVMe Model |
FRU# |
P/N (VPD) |
Microcode File Name |
Check Sum |
800
GB |
KCM6DVUL800G |
02YC738 |
02YC734 |
A180010F.43395335 |
32720 |
1600
GB |
KCM6DRUL1T92 |
02YC739 |
02YC735 |
||
3200
GB |
KCM6DRUL3T84 |
02YC740 |
02YC736 |
||
6400
GB |
KCM6DRUL7T68 |
02YC741 |
02YC737 |
Release date |
Code level |
Severity/ Impact |
Change Description |
Nov
2023 |
C9S5 |
Usability/ Attention |
Fixed
SMBus Temperature Recording |
C9S4 |
New/ New |
General
fixes and Enhancements |
===============================================================
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.
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 nvme*
Vital
Product Data (VPD)
lscfg -vl nvme1
nvme1 U78DA.ND0.WZS003L-P1-C3 PCIe4 x4 NVMe Flash Adapter
800GB NVMe Gen4 U.2 SSD :
Part Number.................01CM534
EC Level....................P45362
FRU Number..................02YC738
Product Specific.(AN).......02YC734
Feature Code/Marketing ID...EKF2
Customer Card ID Number.....5B53
Serial Number...............TSJYEK4J
Product Specific.(Z0).......10140689
Product Specific.(Z1).......3.0
Product Specific.(Z2).......800
Product Specific.(Z3).......4.38
Product Specific.(Z4).......2
Product Specific.(Z5).......01
Product Specific.(Z6).......A180010F
Product Specific.(Z7).......11S
Product Specific.(Z8).......2667
Product Specific.(Z9).......1E
Product Specific.(ZA).......11
Product Specific.(ZB).......08
Product Specific.(ZC).......00
Manufacture
ID..............2280A00BTGZ8
ROM Level.(alterable).......REV.C9S5ß- FW level
C9S5
Product Specific.(RV)........
Hardware Location
Code......U78DA.ND0.WZS003L-P1-C3
You can also use lsmcode
to find the microcode level:
lsmcode –rd nvme1
A180010F.43395335
Note that lsmcode output
FW level is displayed as ASCII/Hex
43 = C |
39 = 9 |
C9S5
53 = S |
35 = 5 |
===============================================================
2.3 Transferring
and Unpacking the Microcode Update Package
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
CM6-ME.bin
c) Unpack the file by executing the instructions below.
Enter the commands:
cd /tmp/fwupdate
chmod +x CM6-ME.bin
./CM6-ME.bin
[Don't overlook the periods (.) in the above command.]
The directory CM6-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/CM6-ME/*
/etc/microcode
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 CM6-ME-C9S5-AIX.rpm
c) Unpack the file by
executing the instructions below:
Enter the commands:
rpm -ihv --ignoreos --force CM6-ME-C9S5-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. No system power cycle OR a partition
reboot is required prior to microcode download is microcode download is done
concurrently.
2. When system comes up,
within 24 hours of reboot, Type diag at the AIX prompt.
3. Select the "Task Selection" from diagnostics menu.
4. Select "Microcode Download" from "Task Selection" menu.
5. Select resource that microcode will be applied to
(i.e.; nvme0), then press "F7" to commit..
6- A small screen displays the message " *** NOTICE*** The microcode
installation occurs while the attached drives are available for use..... "
Press enter to continue
7. Select the source for microcode, use arrow key to go up/down, Enter to
continue.
/etc/microcode
usb mass storage
- Use
/etc/microcode if microcode file is in the system
- Use “usb mass storage” if using usb flash drive
8- Display shows a list of microcodes
available for the selected drive, highlight option "M
43395335", 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.
9. You will receive a msg. "Current
Microcode is...." and "Download has completed successfully"
(this will take a several minutes)
10. Return to the Tasks Selection menu and repeat this procedure for each nvme
(in the same partition) that requires this microcode.
11. Exit diagnostic
2.4.2 Standalone (Service Mode) Download
This procedure is
used for all drives including rootvg or paging space drives
1. Properly shutdown the system.
2. Boot up the system in standalone diagnostics mode with the AIX diag CD/DVD
or USB Thumb drive
3. Select the "Task Selection" from diagnostics menu.
4. Select "Microcode Download" from "Task Selection" menu.
5. Select resource that microcode will be applied to
and PRESS ENTER.
6. Press "F7" to commit.
(The current microcode
level of the resource you selected earlier will be displayed at the top of the
screen)
7. Make the following selections on the next screen:
file system
/etc/microcode
usb mass storage (ISO 9660 file system format)
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 system in normal mode
======================================================
Note: The following procedure is for Red
Hat Linux, please use microcode file package CM6-ME-C9S5-LINUX.tgz for Ubuntu
tar -C-xzvf
CM6-ME-C9S5-LINUX.tgz
Red Hat Enterprise Linux for IBM Power LE
These steps assume you are logged in with root permissions.
Prerequisites for Red Hat
Linux:
Use the ibm-power-repo to configure the repositories and then
use yum to download the nvme-cli package.
http://www14.software.ibm.com/support/customercare/sas/f/lopdiags/home.html
1. Download the IBM Linux on Power Tools Repository configuration
RPM file available at:
http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/yum.html
2. Copy the file to the target system and install the RPM
# rpm -ivh ibm-power-repo-latest.noarch.rpm
3. To add the Tools Repository to the package management
configuration, run the following command as root user (or with root privilege)
and accept the Licensing agreement.
# /opt/ibm/lop/configure
Instructions for installing nvme-cli tool using Red Hat
Enterprise Linux
To list the currently enabled repositories, enter:
# yum repolist enabled
Install the nvme-cli package, enter:
# yum install nvme-cli
After nvme-cli is installed on the
system, to
check the current microcode level for the adapter enter the following command:
# nvme list
Note: "nvme list"
command uses libudev-devel, if it doesn't work, may need to install
“libudev-devel"
1) Type "nvme list"
2) The column “FW Rev” will list the firmware version. For example:
# nvme list
Node
SN
Model
Namespace Usage Format FW Rev
----------------
------------------------
----------------------------------- --------------- ------------------------- ------------------ -------------
/dev/nvme0n1
ZC10A0070JL1 800GB NVMe Gen4
U.2 SSD 1 800 GB /
800 GB 4 KiB + 0 B
REV.C9S5
If the Firmware Version is below
than C9S5 then you should update the microcode.
1. Download
feature code EKF2/EKF3/EKF5/EKF6 package from FixCentral, and transfer the
file, to a temporary directory on the target server such as /tmp.
2. Unpack the package
rpm
-ivh --ignoreos CM6-ME-C9S5-LINUX.rpm
3. The microcode package extracts the
firmware file to the /lib/firmware/ directory
NOTE: Microcode download must be performed
separately for each nvme under distinct Logical Partitions (LPAR's).
Please save current and older versions of the microcode update files in case
you need to restore your system.
Please verify the file size and checksum of the raw microcode files matches the
below.
Filesize: 2064384
Checksum: 32720
For Linux: "ls -l /lib/firmware/A180010F.43395335"
to verify Filesize.
"sum /lib/firmware/A180010F.43395335"
to verify Checksum.
For systems that
have LPAR installed, the microcode file must be placed on all partitions that
have(owns) an NVMe device in order to update the code.
Follow this procedure for each partition:
1.
Log into
the target partition.
2.
Type:
"cd /lib/firmware"
3.
SFTP to
the partition that has the media bay assigned. (ie.
"sftp partition1.ibm.com")
4.
Type:
"cd /lib/firmware"
5.
Type:
"get A180010F.43395335"
6.
Type:
"quit"
3.4 Microcode
Download Procedure-NVMe Adapters for Linux
1) Type "nvme list" and press "Enter". This
will list all of the NVMe adapters in your partition. In
the Node column, the NVMe adapters will be listed as /dev/nvme#n1 where
# is the number of the device.
2) For each NVMe adapter to be update, issue the following commands:
a) Type
“nvme fw-log /dev/nvme<#>” and press “Enter”, where <#> is the
number of the device.
For
example, for device /dev/nvme0n1, type
“nvme fw-log /dev/nvme0” and press “Enter”. This will
list the firmware level currently loaded on the adapter as well as the number
of slots in the adapter.
These 3 slots are listed
as frs1, frs3.
b) Download and activate firmware to the
adapter by typing:
Note that
there are 4 FW “slots” in this nvme, each slot must be updated AND activated,
example below is for nvme0
nvme fw-download
/dev/nvme0 --fw=/lib/firmware/ A180010F.43395335
nvme fw-activate
/dev/nvme0 -a 0 –s 1
Repeat for all slots (-s 2; -s 3)
nvme fw-activate
/dev/nvme0 -a 3 –s 3 ß this step
may be omitted if the nvme device does not support the function
nvme reset
/dev/nvme0