How to update the Flash Accelerator F320 firmware on Exalytics X6-4 systems

Asset ID:	1-71-2203931.1
Update Date:	2018-04-30
Keywords:

Solution Type Technical Instruction Sure

Solution 2203931.1 : How to update the Flash Accelerator F320 firmware on Exalytics X6-4 systems

Applies to:

Exalytics In-Memory Machine X6-4 - Version All Versions to All Versions [Release All Releases]
x86 64 bit

Goal

How to update the Flash Accelerator F320 firmware on Exalytics X6-4 systems

Solution

To update the firmware on the Flash Accelerator F320 cards used in an Exalytics X6-4 server the following steps should be followed. Note that this process will require that the flash cards are unmounted and unused during the firmware application. Please be sure to schedule downtime for this process.

First check the current firmware revision of the cards using the fwupdate command. By using the list controller option and grepping for NVMe we can get a list of just the three Flash Accelerator cards installed in the Exalytics X6-4.

[root@exalytics0 ~]# fwupdate list controller | grep NVMe
c1 NVMe Samsung 0xa821 MS1PC5ED3ORA3.2T KPYAGR3Q - - - - - N/A
c2 NVMe Samsung 0xa821 MS1PC5ED3ORA3.2T KPYAGR3Q - - - - - N/A
c3 NVMe Samsung 0xa821 MS1PC5ED3ORA3.2T KPYAGR3Q - - - - - N/A

The output above shows that the F320 cards currently have firmware version KPYAGR3Q The latest available firmware for these cards is KPYAIR3Q (as of the last update of this document). If the cards already have the latest firmware then there is no need to perform an update. If the output shows an older revision then proceed with the update steps.

When updating firmware there should be no active I/O on the devices being updated. This update should be scheduled when the flash devices can be unmounted and unused. Unmount any filesystems and ensure there will be no usage of the F320 cards during this process before proceeding further. On a normal bare metal installation of an Exalytics system the flash devices are configured into a single raid volume and mounted to /u02 so unmount this filesystem. (if the system is customized in such a way that the flash devices are used/mounted differently then adjust the command accordingly). If the system is virtualized then take the required steps to ensure that the F320 devices are not mounted or in use by any virtual machines or Dom0 (the steps for doing this are out of the scope of this document). You should also check to see that the md devices are not re-syncing currently by checking the /proc/mdstat file. The following example shows the command to unmount the flash volume and then checking the mdstat output to see that there is no active resync process. If there is a resync in progress wait until it is finished before proceeding with the firmware update process.

[root@exalytics0 ~]# umount /u02
[root@exalytics0 ~]# cat /proc/mdstat
Personalities : [raid1] [raid0]
md0 : active raid0 md6[5] md5[4] md4[3] md3[2] md2[1] md1[0]
4686849024 blocks super 1.2 512k chunks

md6 : active raid1 nvme2n1p4[1] nvme1n1p2[0]
781273088 blocks super 1.2 [2/2] [UU]
bitmap: 0/6 pages [0KB], 65536KB chunk

md5 : active raid1 nvme2n1p3[1] nvme1n1p1[0]
781272064 blocks super 1.2 [2/2] [UU]
bitmap: 0/6 pages [0KB], 65536KB chunk

md4 : active raid1 nvme2n1p2[1] nvme0n1p4[0]
781273088 blocks super 1.2 [2/2] [UU]
bitmap: 0/6 pages [0KB], 65536KB chunk

md3 : active raid1 nvme2n1p1[1] nvme0n1p3[0]
781272064 blocks super 1.2 [2/2] [UU]
bitmap: 0/6 pages [0KB], 65536KB chunk

md2 : active raid1 nvme1n1p4[1] nvme0n1p2[0]
781273088 blocks super 1.2 [2/2] [UU]
bitmap: 0/6 pages [0KB], 65536KB chunk

md1 : active raid1 nvme1n1p3[1] nvme0n1p1[0]
781272064 blocks super 1.2 [2/2] [UU]
bitmap: 0/6 pages [0KB], 65536KB chunk

unused devices: <none>

The latest Firmware for the F320 card is available in the X5-4 Firmware Pack. As of the time this document was written the latest release is 2.0.0 patch 26948450 this is the first firmware pack which contains the files needed to update the cards to version KPYAIR3Q.

Download patch 26948450 from MOS and copy it to the /tmp directory of the Exalytics X6-4 server. Then unzip the patch and cd to the Oracle-NVMe-F320 directory where the required files reside. The following example shows the needed steps. These steps assume the patch is located in /tmp if your file is in a different location on the server change the commands as appropriate.

[root@exalytics0 ~]# cd /tmp
[root@exalytics0 tmp]# unzip p26948450_200_Generic.zip
Archive: p26948450_200_Generic.zip
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/service-processor/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/service-processor/metadata.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/service-processor/ILOM-4_0_0_25_r121443-Oracle_Server_X5-4_X5-8.pkg
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/SAS9361-8i/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/SAS9361-8i/app3108.rom
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/SAS9361-8i/metadata.xml
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/mpt3x64.rom
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/metadata.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/Oracle_SAS9300-8e_it_p_000B.bin
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/mptsas3.rom
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/lsisas3f.rom
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/Oracle_SAS9300-8i_it_p_000A.bin
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/mpt3x64.rom
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/metadata.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/mptsas3.rom
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/lsisas3f.rom
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/7101684/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/7101684/metadata.xml
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/7101684/firmware/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/7101684/firmware/A11.1.160.6.grp
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/7101674/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/7101674/metadata.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/7101674/hld36025.bin
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/HSCAC2DA4SUN400G/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/HSCAC2DA4SUN400G/metadata.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/HSCAC2DA4SUN400G/HSCAC2DA4.A29A.fw
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/H101860SFSUN600G/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/H101860SFSUN600G/metadata.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/H101860SFSUN600G/H101860SF.A990.fw
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/H101812SFSUN1.2T/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/H101812SFSUN1.2T/metadata.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/H101812SFSUN1.2T/H101812SF.A990.fw
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle-NVMe-F160/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle-NVMe-F160/8DV1RA11.bin
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle-NVMe-F160/8DV1RA13.bin
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle-NVMe-F160/metadata.xml
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle-NVMe-F320/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle-NVMe-F320/MS1PC2DD3.IR3Q.fw
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle-NVMe-F320/metadata.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle-NVMe-F320/MS1PC5ED3.IR3Q.fw
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle_QDR_Infiniband_Adapter_M3/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle_QDR_Infiniband_Adapter_M3/fw-ConnectX3-rel-2_11_1280-e0-7046442.bin
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle_QDR_Infiniband_Adapter_M3/metadata.xml
creating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Fortville/
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Fortville/readme.txt
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Fortville/metadata.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Fortville/8086_1583_108E_7B1D_80002559.bin
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Fortville/8086_1583_108E_7B1D.cfg
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/license.txt
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Oracle/platform.xml
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Versions.txt
inflating: Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/readme.html
[root@exalytics0 tmp]# cd /tmp/Oracle_Server_X5-4-2.0.0.87617-FIRMWARE_PACK/Firmware/Oracle-NVMe-F320
[root@exalytics0 Oracle-NVMe-F320]# ls
metadata.xml MS1PC2DD3.IR3Q.fw MS1PC5ED3.IR3Q.fw

With all of the required files uncompressed and available the firmware can now be updated. Use the fwupdate command to perform the firmware update procedure. Make sure that your working directory is the Oracle-NVMe-F320 directory which contains the files: metadata.xml MS1PC2DD3.IR3Q.fw MS1PC5ED3.IR3Q.fw. The fwupdate command must be run from this directory.

Execute the command "fwupdate update controller -x metadata.xml" and answer "y" when prompted as shown in the example below.

[root@exalytics0 Oracle-NVMe-F320]# fwupdate update controller -x metadata.xml

The following components will be upgraded as shown:
==========================================================
ID Priority Action Status Old Firmware Ver. Proposed Ver. New Firmware Ver. System Reboot
------------------------------------------------------------------------------------------------------------------------
c1 1 Check FW Success KPYAGR3Q KPYAIR3Q N/A None
c2 1 Check FW Success KPYAGR3Q KPYAIR3Q N/A None
c3 1 Check FW Success KPYAGR3Q KPYAIR3Q N/A None
Do you wish to process all of the above component upgrades? [y/n]? y
Updating c1: Success
Sleeping for 10 seconds for component to recover
Resetting c1
Mandatory post Reset 60 second sleep
Updating c2: Success
Sleeping for 10 seconds for component to recover
Resetting c2
Mandatory post Reset 60 second sleep
Updating c3: Success
Sleeping for 10 seconds for component to recover
Resetting c3
Mandatory post Reset 60 second sleep

Verifying all priority 1 updates

Execution Summary
==========================================================
ID Priority Action Status Old Firmware Ver. Proposed Ver. New Firmware Ver. System Reboot
------------------------------------------------------------------------------------------------------------------------
c1 1 Validate Success KPYAGR3Q KPYAIR3Q KPYAIR3Q None
c2 1 Validate Success KPYAGR3Q KPYAIR3Q KPYAIR3Q None
c3 1 Validate Success KPYAGR3Q KPYAIR3Q KPYAIR3Q None

[root@exalytics0 Oracle-NVMe-F320]#

The fwupdate command can be used again to confirm that the cards now have the new firmware applied. The following example shows the expected output for cards with version KPYABR3Q applied.

[root@exalytics0 ~]# fwupdate list controller | grep NVMe
c1 NVMe Samsung 0xa821 MS1PC5ED3ORA3.2T KPYAIR3Q - - - - - N/A
c2 NVMe Samsung 0xa821 MS1PC5ED3ORA3.2T KPYAIR3Q - - - - - N/A
c3 NVMe Samsung 0xa821 MS1PC5ED3ORA3.2T KPYAIR3Q - - - - - N/A

Attachments

This solution has no attachment