Intel RMSP3HD080E RAID Module Trimode RAID Firmware 51.14.0-3514

Version Numbers:

- Firmware Package: 51.14.0-3514 (MR 7.14 Point)
- Firmware 5.140.00-3247
- MR PL 14.25.07.00
- BootBlock 7.02.00.00-0021
- NVDATA (5.1400.00-0005)
- UEFI_Driver v0x070E0202 (Signed X64)
- Hii v07.14.06.02 (SIGNED)
- BIOS 7.14.00.0
- SBR: 5.1400.00-0465

FW Changes:

- DCSG00117832 - SPDMLIB: Add change to SConstruct to copy library output file ( .a) to release folder
- DCSG00216908 - NVRAM changes for supporting dynamic recon ghost tgtId
- DCSG00225192 - SPDM LIB: Set ECDSA signature with correct size in Signature field of SPDM Challenge response buffer before sending to BMC server
- DCSG00225977 - Implicitly error when converting an expression to a narrower type
- DCSG00231422 - PL NVMe : PCI task management is not getting completed.
- DCSG00297592 - Auto config RAID0 in HII did not work as expected
- DCSG00225219 - Unused phys are managed by VSes in SGPIO BP mode
- DCSG00237478 - [NVMe] SCSI log sense command timeouts seen while running 1MB IOs to NVMe drive
- DCSG00240573 - Use script to upgrade SAS SSD firmware will fail
- DCSG00240942 - In JBOD profile, set VD Write Cache to AWB shows success even though WB Supported is set to NO
- DCSG00242574 - NvmeAdmin: 'Exception handler called' observed while converting drive to Non RAID preceded by Export Log from OM
- DCSG00242613 - Correct Nvme Double Buffer module for multiple double buffer cases.
- DCSG00242940 - supportEPDWithAutoConfigOff supported bit is set as 1
- DCSG00243640 - Out of bound memory access when assigning dma group for controller devices.
- DCSG00244898 - controller FW printed ‘Assertion failure in fwcpuarmexceptions.c at line 1006: 0 during fio issue verify(2F) commands to sas hdd(JBOD) ’
- DCSG00246022 - CTRL_MFC_DEFAULTS_SET DCMD returning error when controller is in eHBA mode
- DCSG00249465 - Low risk temporary solution for preventing duplicate target Ids
- DCSG00255321 - User disabled PTB not reflected, hence PTB.txt is part of OnDemand SnapDump
- DCSG00255322 - PTB switch to Enabled and Save. No PoP up message reboot required/PTB.txt not part of Snapdump.
- DCSG00255323 - Controller Bios never sent the printing-has-completed DCMD
- DCSG00257908 - Last LDBBM entry in the list is not cleared after VD Deletion
- DCSG00258052 - Controller crash and resets on attempt to boot to windows OS
- DCSG00258546 - VSES: Incorrect linkup failed elements status reported on certain slots of the UBM backplane
- DCSG00263186 - UNMAP support is blocked and disabled
- DCSG00269097 - PRP-List overwritten in Double-Buffer-Copy-To-Host for response size > 8K
- DCSG00214352 - SMART Polling Improvement- API Changes
- DCSG00222915 - API change to add DCMD MR_DCMD_CTRL_LOCK_KEY_SECRET_KEY_APPLY and associated MFI STAT
- DCSG00223408 - Update mr_configpage.h file for New fields 'predFailPollDAInterval' and 'predFailPollInterval' in MPI2_MR_PARAMS_PAGE_0
- DCSG00225175 - SPDM_LIB: Support to build Challenge buffer with multiple GET_CERTIFICATE/CERTIFICATE_RESPONSE
- DCSG00226286 - Preboot Trace Buffer [PTB] for Ventura/Aero - add a switch - MR API
- DCSG00228248 - Preboot Trace Buffer [PTB] for Ventura/Aero - add a switch - nvram
- DCSG00229416 - New MFI Stat for the updated recon behavior
- DCSG00231443 - MR7 API: Add package incompatibility reporting
- DCSG00234391 - BST setup with Channel HBA + Elrond
- DCSG00237302 - Make necessary changes to atlas_bst in valscripts to enable BST
- DCSG00237413 - Persisting secureLD targetId bitmap
- DCSG00246317 - SMART Polling Improvement - API Changes
- DCSG00248087 - SMART Polling Improvement -New Dynamic Section to save New Controller properties structure in NVSRAM
- DCSG00256271 - To add return status MFI_STAT_OK_REBOOT_REQUIRED to MR_DCMD_LD_SET_PROPERTIES in mr.h
- DCSG00257777 - MFI SMP Port Num API changes
- DCSG00216966 - Execute once Auto configure option needs to be allowed for EPD-PT behaviour mode for certain controllers.
- DCSG00227036 - Preboot Trace Buffer [PTB] for Ventura/Aero - add a switch - MR firmware

MR PL:

- DCSG00212793 - BST: BST cancellations on cable breaker comm port unavailability
- DCSG00216461 - BST: UBM BST funtonality is broken on latest BST code.
- DCSG00228186 - Aero BST: Manage NVMe drive link up timing
- DCSG00231422 - PL NVMe : PCI task management is not getting completed.
- DCSG00239268 - BST: SAL reports unknown device type for drives
- DCSG00225219 - Unused phys are managed by VSes in SGPIO BP mode
- DCSG00237478 - [NVMe] SCSI log sense command timeouts seen while running 1MB IOs to NVMe drive
- DCSG00243640 - Out of bound memory access when assigning dma group for controller devices.
- DCSG00258546 - VSES: Incorrect linkup failed elements status reported on certain slots of the UBM backplane
- DCSG00023491 - Implemented secureSignCNG.exe CLI signing tool for Windows Signing.
- DCSG00030211 - Implement support for Cross certificate and command - Windows signing using CNG Provider with HSM Protected Key
- DCSG00040377 - Port secureSignBin.exe for MARGAY signing to GCP server environment
- DCSG00048670 - Aero multi-party signing partial signing of images
- DCSG00077215 - Signing Linux executables via GPG method in HSM
- DCSG00105430 - Implement changes to secureSign signing tool and infrastructure to support mixed list of PublicKeys that are from SCGCQ and DCSG.
- DCSG00129388 - Implemented change to use FTP instead of UNC for upload / download of unsigned / signed artifacts to workaround firewall issue.
- DCSG00143847 - Add support for signing MegaRAID Legacy BIOS CU Images (CTLR) images
- DCSG00234646 - Implement customSign.exe CLI wrapper utility to help customers sign with their private key

UEFI:

- DCSG00152527 - RSOD in UEFI environment during VMware 6.7, WMware 7.0 and RHEL 8.0 installs
- DCSG00217584 - Increase Stall() interval and reduce total number of loops accordingly

UEFI shell instructions for updating RAID Firmware:
- Download and extract all files to a USB flash drive.
- Boot the target system to EFI shell.
- Change directory to the local drive and directory containing the flash update files and the firmware image file.
- Type the name of the .nsh file matching the controller to update (e.g. "RMSP3HD080E.nsh" and press <Enter> to execute the command
- The storcli command line in the .nsh command will default to the first logical RAID contoller ("/c0"). If this there are multiple controllers, the value of controller parameter ("/Cx") will need to be modified to match the specific controller intended for update.
- Wait for the flash to complete. Do NOT reboot the system during the update.
- You can also use RAID Web Console 3 or OS version of StorCLI to update the RAID firmware.

Attention!

- Intel recommends to loading Factory Default setting after the firmware upgrade which will not affect data on any existing array.
- Reboot the system and login to the RAID BIOS Console.
- Select the controller and select 'Adapter Properties'->'Next'
- Set the 'Set Factory Defaults' setting to 'Yes' and submit the change.
- Reboot the system (the default settings are applied).
- Re-configure to the desired settings in RAID Web Console3.

Firmware downgrade notice

- Intel does not recommend to downgrade the factory installed firmware on your RAID module or controller, it has important enhancements and bug fixes you may lose when going to a previous version.
- If you need to install an older firmware version, please contact Intel for instructions on how to perform this action.

About Firmware Updates:

Applying a newer firmware version than the one already installed on your unit can bring various enhancements, include workarounds for diverse problems encountered by the device, and improve or add newly developed features.

On the other hand, downgrading the firmware version can recover the device's functionality in the event of a software update either turning up faulty or causing the unit's overall performance to drop. However, bear in mind that applying an older firmware isn't recommended and might not always be possible.

When it comes to the update steps, due to the large variety of devices and numerous ways for installing a new firmware, it is recommended that you carefully read and understand the upgrade steps, and consider applying a different firmware only when you have familiarized yourself with the update method.

As the installation process is most of the times quite risky, this step should be taken by users that have the ability to successfully complete the update; regular users may initiate it at their own risk. Moreover, it's best that this task be performed in a steady power environment such as the one ensured by a UPS unit.

Therefore, if you consider applying this release, hit the download button, take into account all the aforementioned aspects, and update the device's firmware. Also make sure you constantly check with our website to ensure that you don't miss a single new release.