| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
||
 |
||||||||||||
Solution Type Technical Instruction Sure Solution 2114031.1 : How to update the Flash Accelerator F160 firmware on Exalytics X5-4 systems
Applies to:Exalytics In-Memory Machine X5-4 - Version All Versions to All Versions [Release All Releases]x86 64 bit GoalHow to update the Flash Accelerator F160 firmware on Exalytics X5-4 systems SolutionTo update the firmware on the Flash Accelerator F160 cards used in an Exalytics X5-4 server the following steps should be followed. Note that this process will require the system to be rebooted and the flash cards 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 X5-4. [root@exalytics0 ~]# fwupdate list controller | grep NVMe The output above shows that the F160 cards currently have firmware version 8DV1RA12 The latest available firmware for these cards is 8DV1RA13 (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 F160 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 F160 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. [root@exalytics0 ~]# umount /u02
[root@exalytics0 ~]# cat /proc/mdstat Personalities : [raid1] [raid0] md0 : active raid0 md5[4] md1[0] md2[1] md4[3] md3[2] md6[5] 2342642688 blocks super 1.2 512k chunks md5 : active raid1 nvme1n1p1[0] nvme2n1p3[1] md2 : active raid1 nvme0n1p2[0] nvme1n1p4[1] md6 : active raid1 nvme1n1p2[0] nvme2n1p4[1] md3 : active raid1 nvme2n1p1[1] nvme0n1p3[0] md4 : active raid1 nvme2n1p2[1] nvme0n1p4[0] md1 : active raid1 nvme1n1p3[1] nvme0n1p1[0] unused devices: <none> The latest Firmware for the F160 card is available in the X5-4 Firmware Pack. As of the time this document was written the latest release is 1.0.3 patch 22393676 this is the first firmware pack which contains the files needed to update the cards to version 8DV1RA13. Download patch 22393676 from MOS and copy it to the /tmp directory of the Exalytics X5-4 server. Then unzip the patch and cd to the Oracle-NVMe-F160 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 p22393676_103_Generic.zip Archive: p22393676_103_Generic.zip creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/service-processor/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/service-processor/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/service-processor/ILOM-3_2_5_10_c_r105050-Oracle_Server_X5-4_X5-8.pkg creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/SAS9361-8i/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/SAS9361-8i/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/SAS9361-8i/app3108.rom creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/Oracle_SAS9300-8e_it_p_0008.bin inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/mptsas3.rom inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/lsisas3f.rom inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-EXT-SAS3/mpt3x64.rom creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/mptsas3.rom inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/Oracle_SAS9300-8i_it_p_0008.bin inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/lsisas3f.rom inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/ORCL-INT-SAS3/mpt3x64.rom creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/7101684/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/7101684/metadata.xml creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/7101684/firmware/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/7101684/firmware/A11602.grp creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/7101674/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/7101674/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/7101674/hld36017.bin creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/HSCAC2DA4SUN400G/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/HSCAC2DA4SUN400G/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/HSCAC2DA4SUN400G/HSCAC2DA4.A29A.fw creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/H101860SFSUN600G/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/H101860SFSUN600G/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/H101860SFSUN600G/H101860SF.A770.fw creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/H101812SFSUN1.2T/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/H101812SFSUN1.2T/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/H101812SFSUN1.2T/H101812SF.A770.fw creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/Oracle-NVMe-F160/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/Oracle-NVMe-F160/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/Oracle-NVMe-F160/8DV1RA13.bin inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/Oracle-NVMe-F160/8DV1RA11.bin creating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/Oracle_QDR_Infiniband_Adapter_M3/ inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/Oracle_QDR_Infiniband_Adapter_M3/metadata.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/Oracle_QDR_Infiniband_Adapter_M3/fw-ConnectX3-rel-2_11_1280-e0-7046442.bin inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/license.txt inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Oracle/platform.xml inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Versions.txt inflating: Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/readme.html [root@exalytics0 tmp]# cd /tmp/Oracle_Server_X5-4-1.0.3.84985-FIRMWARE_PACK/Firmware/Oracle-NVMe-F160/ [root@exalytics0 Oracle-NVMe-F160]# ls 8DV1RA11.bin 8DV1RA13.bin metadata.xml 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-F160 directory which contains the files 8DV1RA13.bin and metadata.xml. 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. After answering "y" the second time the system will reboot if for any reason you cannot reboot immediately then answer "n". [root@exalytics0 Oracle-NVMe-F160]# fwupdate update controller -x metadata.xml
The following components will be upgraded as shown: Verifying all priority 1 updates Execution Summary Broadcast message from root@exalytics0 The system is going down for reboot NOW! Allow the system to reboot (note that the reboot may take approximately 15 minutes to complete) After the system finishes rebooting login to the server and confirm that the cards now have the new firmware applied. The following example shows the expected output for cards with version 8DV1RA13 applied. [root@exalytics0 ~]# fwupdate list controller | grep NVMe
c1 NVMe Intel 0x0953 INTEL SSDPEDME016T4S 8DV1RA13 - - - - - N/A c2 NVMe Intel 0x0953 INTEL SSDPEDME016T4S 8DV1RA13 - - - - - N/A c3 NVMe Intel 0x0953 INTEL SSDPEDME016T4S 8DV1RA13 - - - - - N/A Attachments This solution has no attachment |
||||||||||||
|
||||||||||||