The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.  Use this command:

    elxdrvr-fc-version.exe /q2 extract=2

The extracted files are located:

    C:\Users\Administrator\Documents\Emulex\Drivers\FC-version

Each kit folder has subsequent architecture folders with subsequent OS folders.  For example,

    C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022

This Component is FIPs enabled.

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will be failed because a secure volume cannot be changed to an unsecure volume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume[Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.
• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress: changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete: changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14
• Added HPE ProLiant Compute DL380a Gen12 Server
• Support Decouple metadata 

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will befailed because a secure volume cannot be changed to an unsecurevolume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume [Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.

• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified  number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress:changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete:changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14

• Increased the RX lossless buffer size to delay the transmission of Pause/PFC frames during NIC congestion.
• Added support for SyncE at 1G link speed.
• Added a new mechanism for allocations and deallocations flows to enhance parallelism.
• When using a multi-host deployment, each host is assigned unique ports and PFs and manages its own LAG.
• Added support for a new synchronized flow, including a tool and driver, to perform a fwreset on setups with a PCIe switch configuration.
• Unified PTP is now supported across different VFs on the same PF.
• Added support for new MADs: PortRecoveryPolicyConfig and PortRecoveryPolicyCounters . During the PHY recovery process, the firmware core will indicate the  port_logical_state as Active.
• Added a new NV config (SM_DISABLE, default 0) which, when enabled, blocks SMP traffic that does not originate from the SM.
• Added the ability to set cable length as a parameter in the PFCC access register. The cable length is used in the calculation of RX lossless buffer parameters, including size, Xoff, and Xon thresholds.

• Added support for PCIe Telemetry (NSM Type 2).
• Migrated PCC NP solution from ACE hardware platform to DPA hardware platform. The new capability is applicable to the following modes: 1) PCC_INT_EN=True and PCC_INT_NP_RTT_DATA_MODE=INGRESS_BYTE 2) PCC_INT_EN=True and PCC_INT_NP_RTT_DATA_MODE=NO_DATA. The first mode is used to support ZTRCC RX bytes in RTT response.
• Added the option to indicate an error CQE event on every selected function per eSwitch manager. This indication is defined as a new WQE including the relevant information about the error (such as: syndrome, function_id, timestamp, QPs num etc.).
• Extended kernel lockdown permission set. The following sub-operations can now be called by tools (permission TOOLS_RESORCES) using new HCA capability bitmask field: tool_partial_cap.

The 5 sub-operations are:

• QUERY_HCA_CAP with other function
• QUERY_VUID with direct data
• QUERY_ROCE_ADDRESS with other vport
• SET_HCA_CAP with other function
• POSTPONE_CONNECTED_QP_TIMEOUT with other vport

The new added caps are:

• tool_partial_cap.postpone_conn_qp_timeout_other_vport,
• tool_partial_cap.set_hca_cap_other_func
• tool_partial_cap.query_roce_addr_other_vport
• tool_partial_cap.query_vuid_direct_data
• tool_partial_cap.query_hca_cap_other_func

• Added support for QoS scheduling across multiple E-Switches grouped in a LAG. VPort members of a Physical Function can be added to a rate group from another Physical Function and rate limits of the group will apply to those VPort members as well.
• Added 'table_type_valid' and 'table_type' fields to the steering action (STC) "Jump To Flow" table parameters to enable the user to jump from NIC_TX to FDB_TX and bypass the ACL table.
• Enabled hop reduction by bypassing NIC domain in various use cases. Such action reduces the number of hops (improves PPS) to deal with mass number of flows and devices. To enable this new capability, a new STC action type "JUMP_TO_FDB_RX" was added to allow jumping into the RX side of a table.
• Increased the maximum number of supported "ARC-IN" from 1 to 8 and "ARC-OUT" from 3 to 8 for the dynamic flex parser.
• Added histogram support for rate and Round-Trip Time (RTT) in PCC ZTR_RTTC.
• Added a recovery step in case of CQ doorbell getting lost during VF migration.
• Changed PCIe Gen4/5 new static configuration for VGA gain and CTLE.
• Changed the CTLE and VGA gain for Gen4/5 starting point.
• Increased SPDM's RDT value.

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will be failed because a secure volume cannot be changed to an unsecure volume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume[Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.
• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress: changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete: changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14
• Added HPE ProLiant Compute DL380a Gen12 Server
• Support Decouple metadata 

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will befailed because a secure volume cannot be changed to an unsecurevolume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume [Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.

• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified  number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress:changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete:changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14

New features and changes included in version 26.43.1014:

• Added a recovery step in case of CQ doorbell getting lost during VF migration.
• Added the option to indicate an error CQE event on every selected function per eSwitch manager. This indication is defined as a new WQE including the relevant information about the error (such as: syndrome, function_id, timestamp, QPs num etc.). The feature is configured using a new general object: RDMA-Telemetry object, and depends on the following new caps:

HCA_CAP.rdma_telemetry_notification_types and HCA_CAP.rdma_telemetry.

• Extended kernel lockdown permission set. The following sub-operations can now be called by tools (permission TOOLS_RESORCES) using new HCA capability bitmask field: tool_partial_cap.

The 5 sub-operations are:

• QUERY_HCA_CAP with other function
• QUERY_VUID with direct data
• QUERY_ROCE_ADDRESS with other vport
• SET_HCA_CAP with other function
• POSTPONE_CONNECTED_QP_TIMEOUT with other vport

The new added caps are:

• tool_partial_cap.postpone_conn_qp_timeout_other_vport,
• tool_partial_cap.set_hca_cap_other_func
• tool_partial_cap.query_roce_addr_other_vport
• tool_partial_cap.query_vuid_direct_data
• tool_partial_cap.query_hca_cap_other_func

• Added 'table_type_valid' and 'table_type' fields to the steering action (STC) "Jump To Flow" table parameters to enable the user to jump from NIC_TX to FDB_TX and bypass the ACL table.
• Enabled hop reduction by bypassing NIC domain in various use cases. Such action r educes the number of hops (improves PPS) to deal with mass number of flows and devices. To enable this new capability, a new STC action type "JUMP_TO_FDB_RX" was added to allow jumping into the RX side of a table.

New features and changes included in version 26.42.1000:

• Prevented HCA_CAP from allowing rogue drivers to create more EQs than the number allowed in the HCA_CAP.max_num_eqs.
• Removed the logical port rate limiter to prevent the internal loopback traffic from exceeding the physical port network link speed when using the esw scheduling feature.
• Added a new command interface "Memory slow release" to enable/disable holding memory pages for a defined period of time. Once the timer expires, the firmware will return the pages to the driver.
• Added support for MVTS register via a miscellaneous driver using the access_register PRM command.

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will be failed because a secure volume cannot be changed to an unsecure volume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume[Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.
• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress: changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete: changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14
• Added HPE ProLiant Compute DL380a Gen12 Server
• Support Decouple metadata 

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will be failed because a secure volume cannot be changed to an unsecure volume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume[Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.
• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress: changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete: changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14

New features and changes included in version 26.43.1014:

• Added a recovery step in case of CQ doorbell getting lost during VF migration.
• Added the option to indicate an error CQE event on every selected function per eSwitch manager. This indication is defined as a new WQE including the relevant information about the error (such as: syndrome, function_id, timestamp, QPs num etc.). The feature is configured using a new general object: RDMA-Telemetry object, and depends on the following new caps:

HCA_CAP.rdma_telemetry_notification_types and HCA_CAP.rdma_telemetry.

• Extended kernel lockdown permission set. The following sub-operations can now be called by tools (permission TOOLS_RESORCES) using new HCA capability bitmask field: tool_partial_cap.

The 5 sub-operations are:

• QUERY_HCA_CAP with other function
• QUERY_VUID with direct data
• QUERY_ROCE_ADDRESS with other vport
• SET_HCA_CAP with other function
• POSTPONE_CONNECTED_QP_TIMEOUT with other vport

The new added caps are:

• tool_partial_cap.postpone_conn_qp_timeout_other_vport,
• tool_partial_cap.set_hca_cap_other_func
• tool_partial_cap.query_roce_addr_other_vport
• tool_partial_cap.query_vuid_direct_data
• tool_partial_cap.query_hca_cap_other_func

• Added 'table_type_valid' and 'table_type' fields to the steering action (STC) "Jump To Flow" table parameters to enable the user to jump from NIC_TX to FDB_TX and bypass the ACL table.
• Enabled hop reduction by bypassing NIC domain in various use cases. Such action r educes the number of hops (improves PPS) to deal with mass number of flows and devices. To enable this new capability, a new STC action type "JUMP_TO_FDB_RX" was added to allow jumping into the RX side of a table.

New features and changes included in version 26.42.1000:

• Prevented HCA_CAP from allowing rogue drivers to create more EQs than the number allowed in the HCA_CAP.max_num_eqs.
• Removed the logical port rate limiter to prevent the internal loopback traffic from exceeding the physical port network link speed when using the esw scheduling feature.
• Added a new command interface "Memory slow release" to enable/disable holding memory pages for a defined period of time. Once the timer expires, the firmware will return the pages to the driver.
• Added support for MVTS register via a miscellaneous driver using the access_register PRM command.

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will be failed because a secure volume cannot be changed to an unsecure volume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume[Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.
• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress: changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete: changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14
• Added HPE ProLiant Compute DL380a Gen12 Server
• Support Decouple metadata 

o POST Storage.SetEncryptionKey
o PATCH Storage[EncryptionMode]
o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable
o POST Drive.RevertToOriginalFactoryState
o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will be failed because a secure volume cannot be changed to an unsecure volume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume[Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.
• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress:changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14

• Increased the RX lossless buffer size to delay the transmission of Pause/PFC frames during NIC congestion.
• Added support for SyncE at 1G link speed.
• Added a new mechanism for allocations and deallocations flows to enhance parallelism.
• When using a multi-host deployment, each host is assigned unique ports and PFs and manages its own LAG.
• Added support for a new synchronized flow, including a tool and driver, to perform a fwreset on setups with a PCIe switch configuration.
• Unified PTP is now supported across different VFs on the same PF.
• Added support for new MADs: PortRecoveryPolicyConfig and PortRecoveryPolicyCounters . During the PHY recovery process, the firmware core will indicate the  port_logical_state as Active.
• Added a new NV config (SM_DISABLE, default 0) which, when enabled, blocks SMP traffic that does not originate from the SM.
• Added the ability to set cable length as a parameter in the PFCC access register. The cable length is used in the calculation of RX lossless buffer parameters, including size, Xoff, and Xon thresholds.

• Added support for PCIe Telemetry (NSM Type 2).
• Migrated PCC NP solution from ACE hardware platform to DPA hardware platform. The new capability is applicable to the following modes: 1) PCC_INT_EN=True and PCC_INT_NP_RTT_DATA_MODE=INGRESS_BYTE 2) PCC_INT_EN=True and PCC_INT_NP_RTT_DATA_MODE=NO_DATA. The first mode is used to support ZTRCC RX bytes in RTT response.
• Added the option to indicate an error CQE event on every selected function per eSwitch manager. This indication is defined as a new WQE including the relevant information about the error (such as: syndrome, function_id, timestamp, QPs num etc.).
• Extended kernel lockdown permission set. The following sub-operations can now be called by tools (permission TOOLS_RESORCES) using new HCA capability bitmask field: tool_partial_cap.

The 5 sub-operations are:

• QUERY_HCA_CAP with other function
• QUERY_VUID with direct data
• QUERY_ROCE_ADDRESS with other vport
• SET_HCA_CAP with other function
• POSTPONE_CONNECTED_QP_TIMEOUT with other vport

The new added caps are:

• tool_partial_cap.postpone_conn_qp_timeout_other_vport,
• tool_partial_cap.set_hca_cap_other_func
• tool_partial_cap.query_roce_addr_other_vport
• tool_partial_cap.query_vuid_direct_data
• tool_partial_cap.query_hca_cap_other_func

• Added support for QoS scheduling across multiple E-Switches grouped in a LAG. VPort members of a Physical Function can be added to a rate group from another Physical Function and rate limits of the group will apply to those VPort members as well.
• Added 'table_type_valid' and 'table_type' fields to the steering action (STC) "Jump To Flow" table parameters to enable the user to jump from NIC_TX to FDB_TX and bypass the ACL table.
• Enabled hop reduction by bypassing NIC domain in various use cases. Such action reduces the number of hops (improves PPS) to deal with mass number of flows and devices. To enable this new capability, a new STC action type "JUMP_TO_FDB_RX" was added to allow jumping into the RX side of a table.
• Increased the maximum number of supported "ARC-IN" from 1 to 8 and "ARC-OUT" from 3 to 8 for the dynamic flex parser.
• Added histogram support for rate and Round-Trip Time (RTT) in PCC ZTR_RTTC.
• Added a recovery step in case of CQ doorbell getting lost during VF migration.
• Changed PCIe Gen4/5 new static configuration for VGA gain and CTLE.
• Changed the CTLE and VGA gain for Gen4/5 starting point.
• Increased SPDM's RDT value.

• [Beta] Added support for QoS scheduling across multiple E-Switches grouped in a LAG. VPort members of a Physical Function can be added to a rate group from another Physical Function and rate limits of the group will apply to those VPort members as well.
• Added kernel support for monitoring RDMA events from userspace. Using the netlink or the RDMA tool, users will be able to monitor the InfiniBand device events and changes such as device register, device unregister and netdev attachment/detachment.
• Added the “irqs” directory inside the SF sysfs directory to provide the users information about the mapping of SFs and their IRQs.
• Added support for setting a maximum number of completion EQs for SFs.
• Added support for up to 23 bits for uar_page_index in create_cq flow. This allows the user to perform create_cq with a uar_page_index larger than 2^16 as supported by the hardware/firmware.
• [Beta] Added support for specifying bandwidth proportions between traffic classes (TC) in the devlink-rate API. This new option allows users to allocate bandwidth across multiple traffic classes in a single command. This feature provides a more granular control over traffic management, especially for scenarios requiring Enhanced Transmission Selection. Users can now define a specific bandwidth share for each traffic class, such as allocating 20% for TC0 (TCP/UDP) and 80% for TC5 (RoCE).

• Changed the SF initiation/boot flow to avoid EQ creations. Now EQ will be created only when required by the user/system QPs.
• [Beta] fwctl is a new subsystem intended to bring some common rules and order to the growing pattern of exposing a secure firmware interface directly to the userspace. fwctl focuses on debugging, configuration and provisioning of the device. As fwctl is not installed by default, you can install it by adding "--fwctl" to the installation command.
• Exposes the req_transport_retries_exceeded counter (per QP counter). It can be seen using the RDMA statistics, and shows the number of times the requester detected transport retries exceed error.
• Creates a single netdev abstraction for multiple Socket-Direct PFs of the same port that run on multiple NUMA nodes. This single netdev handles traffic locally on each of the NUMA nodes without upper layer complexities. This improves the applications' locality and performance in a multi-NUMA system.
• Added devlink-nested option to show relationships between devlink instances through devlink dev show/devlink port show commands. The devlink port show is used to check when SFs are activated, and shows the relationship between SF auxiliary device devlink instance and the eSwitch representor devlink port. Devlink Scalable Function (SF) activate command is received before enabling a partial parallelization of the SFs activation, and reduces time.
• Extended the number of rules to be offloaded to all ports from 8 to 32. This allows greater flexibility when offloading temporary rules like VLAN traffic and ease the offload sharing between the ports.

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will be failed because a secure volume cannot be changed to an unsecure volume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume[Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.
• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress: changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete: changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14
• Added HPE ProLiant Compute DL380a Gen12 Server
• Support Decouple metadata 

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will befailed because a secure volume cannot be changed to an unsecurevolume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume [Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.
• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified number of days has been removed The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress:changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14

• Increased the RX lossless buffer size to delay the transmission of Pause/PFC frames during NIC congestion.
• Added support for SyncE at 1G link speed.
• Added a new mechanism for allocations and deallocations flows to enhance parallelism.
• When using a multi-host deployment, each host is assigned unique ports and PFs and manages its own LAG.
• Added support for a new synchronized flow, including a tool and driver, to perform a fwreset on setups with a PCIe switch configuration.
• Unified PTP is now supported across different VFs on the same PF.
• Added support for new MADs: PortRecoveryPolicyConfig and PortRecoveryPolicyCounters . During the PHY recovery process, the firmware core will indicate the  port_logical_state as Active.
• Added a new NV config (SM_DISABLE, default 0) which, when enabled, blocks SMP traffic that does not originate from the SM.
• Added the ability to set cable length as a parameter in the PFCC access register. The cable length is used in the calculation of RX lossless buffer parameters, including size, Xoff, and Xon thresholds.

• Added support for PCIe Telemetry (NSM Type 2).
• Migrated PCC NP solution from ACE hardware platform to DPA hardware platform. The new capability is applicable to the following modes: 1) PCC_INT_EN=True and PCC_INT_NP_RTT_DATA_MODE=INGRESS_BYTE 2) PCC_INT_EN=True and PCC_INT_NP_RTT_DATA_MODE=NO_DATA. The first mode is used to support ZTRCC RX bytes in RTT response.
• Added the option to indicate an error CQE event on every selected function per eSwitch manager. This indication is defined as a new WQE including the relevant information about the error (such as: syndrome, function_id, timestamp, QPs num etc.).
• Extended kernel lockdown permission set. The following sub-operations can now be called by tools (permission TOOLS_RESORCES) using new HCA capability bitmask field: tool_partial_cap.

The 5 sub-operations are:

• QUERY_HCA_CAP with other function
• QUERY_VUID with direct data
• QUERY_ROCE_ADDRESS with other vport
• SET_HCA_CAP with other function
• POSTPONE_CONNECTED_QP_TIMEOUT with other vport

The new added caps are:

• tool_partial_cap.postpone_conn_qp_timeout_other_vport,
• tool_partial_cap.set_hca_cap_other_func
• tool_partial_cap.query_roce_addr_other_vport
• tool_partial_cap.query_vuid_direct_data
• tool_partial_cap.query_hca_cap_other_func

• Added support for QoS scheduling across multiple E-Switches grouped in a LAG. VPort members of a Physical Function can be added to a rate group from another Physical Function and rate limits of the group will apply to those VPort members as well.
• Added 'table_type_valid' and 'table_type' fields to the steering action (STC) "Jump To Flow" table parameters to enable the user to jump from NIC_TX to FDB_TX and bypass the ACL table.
• Enabled hop reduction by bypassing NIC domain in various use cases. Such action reduces the number of hops (improves PPS) to deal with mass number of flows and devices. To enable this new capability, a new STC action type "JUMP_TO_FDB_RX" was added to allow jumping into the RX side of a table.
• Increased the maximum number of supported "ARC-IN" from 1 to 8 and "ARC-OUT" from 3 to 8 for the dynamic flex parser.
• Added histogram support for rate and Round-Trip Time (RTT) in PCC ZTR_RTTC.
• Added a recovery step in case of CQ doorbell getting lost during VF migration.
• Changed PCIe Gen4/5 new static configuration for VGA gain and CTLE.
• Changed the CTLE and VGA gain for Gen4/5 starting point.
• Increased SPDM's RDT value.

Enhanced Chinese translation support for some options. e.g. "core", "enabled", "disabled", "locked", etc.

Grayed out RBSU "pcie data link feature" option in "System Configuration > BIOS/Platform Configuration (RBSU) > PCIe Device Configuration > Advanced PCIe Configuration".

Added support for 2-DIMM and 4-DIMM population.

Added RBSU "HardwarePM Interrupt" option in "System Configuration > BIOS/Platform Configuration (RBSU) > Power and Performance Options > Advanced Power Options".

Added the "Smooth Cooling" selection to the Thermal Configuration option in the RBSU\Advanced Options\Fan and Thermal Options. This selection modifies the fan speed response to improve acoustics by reducing the rate of fan speed changes. This can improve acoustics for workloads which significantly vary CPU utilization. Note that this option can result in a small reduction in performance due to the short durations of CPU thermal throttling and some operating systems, such as Linux, may log CPU thermal throttling events. These events do not indicate an issue with the system and can be ignored.

New features and changes included in version 22.43.1014:

• Added a recovery step in case of CQ doorbell getting lost during VF migration.
• Added the option to indicate an error CQE event on every selected function per eSwitch manager. This indication is defined as a new WQE including the relevant information about the error (such as: syndrome, function_id, timestamp, QPs num etc.). The feature is configured using a new general object: RDMA-Telemetry object, and depends on the following new caps:

HCA_CAP.rdma_telemetry_notification_types and HCA_CAP.rdma_telemetry .

• Extended kernel lockdown permission set. The following sub-operations can now be called by tools (permission TOOLS_RESORCES) using new HCA capability bitmask field: tool_partial_cap.

The 5 sub-operations are:

• QUERY_HCA_CAP with other function
• QUERY_VUID with direct data
• QUERY_ROCE_ADDRESS with other vport
• SET_HCA_CAP with other function
• POSTPONE_CONNECTED_QP_TIMEOUT with other vport

The new added caps are:

• tool_partial_cap.postpone_conn_qp_timeout_other_vport,
• tool_partial_cap.set_hca_cap_other_func
• tool_partial_cap.query_roce_addr_other_vport
• tool_partial_cap.query_vuid_direct_data
• tool_partial_cap.query_hca_cap_other_func

• Added 'table_type_valid' and 'table_type' fields to the steering action (STC) "Jump To Flow" table parameters to enable the user to jump from NIC_TX to FDB_TX and bypass the ACL table.
• Enabled hop reduction by bypassing NIC domain in various use cases. Such action reduces the number of hops (improves PPS) to deal with mass number of flows and devices. To enable this new capability, a new STC action type "JUMP_TO_FDB_RX" was added to allow jumping into the RX side of a table.
• Added support for QoS scheduling across multiple E-Switches grouped in a LAG. VPort members of a Physical Function can be added to a rate group from another Physical Function and rate limits of the group will apply to those VPort members as well.
• Increased the maximum number of supported "ARC-IN" from 1 to 8 and "ARCOUT" from 3 to 8 for the dynamic flex parser.

New features and changes included in version 22.42.1000:

• Prevented HCA_CAP from allowing rogue drivers to create more EQs than the number allowed in the HCA_CAP.max_num_eqs.
• Added a new command interface "Memory slow release" to enable/disable holding memory pages for a defined period of time. Once the timer expires, the firmware will return the pages to the driver.
• Added support for MVTS register via a miscellaneous driver using the access_register PRM command.
• MSI-X on SF can be received now through the PF's MSI-X vector.

• [Beta] Added support for QoS scheduling across multiple E-Switches grouped in a LAG. VPort members of a Physical Function can be added to a rate group from another Physical Function and rate limits of the group will apply to those VPort members as well.
• Added kernel support for monitoring RDMA events from userspace. Using the netlink or the RDMA tool, users will be able to monitor the InfiniBand device events and changes such as device register, device unregister and netdev attachment/detachment.
• Added the “irqs” directory inside the SF sysfs directory to provide the users information about the mapping of SFs and their IRQs.
• Added support for setting a maximum number of completion EQs for SFs.
• Added support for up to 23 bits for uar_page_index in create_cq flow. This allows the user to perform create_cq with a uar_page_index larger than 2^16 as supported by the hardware/firmware.
• [Beta] Added support for specifying bandwidth proportions between traffic classes (TC) in the devlink-rate API. This new option allows users to allocate bandwidth across multiple traffic classes in a single command. This feature provides a more granular control over traffic management, especially for scenarios requiring Enhanced Transmission Selection. Users can now define a specific bandwidth share for each traffic class, such as allocating 20% for TC0 (TCP/UDP) and 80% for TC5 (RoCE).

• Enhanced firmware reset flow for Sync1 utilizing community-accepted hot reset kernel flow.

    o /cx show spindownatshutdown
    o /cx set spindownatshutdown {[sashdd=<on|off>] [satahdd=<on|off>]
        [sasssd=<on|off>] [satassd=<on|off>] [nvmessd=<on|off>]}

• Adjust the RAID1 consistency related error message
• Added HPE ProLiant Compute DL380a Gen12 Server support

    o /cx show spindownatshutdown
    o /cx set spindownatshutdown {[sashdd=<on|off>] [satahdd=<on|off>]
        [sasssd=<on|off>] [satassd=<on|off>] [nvmessd=<on|off>]}

• Adjust the RAID1 consistency related error message

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will be failed because a secure volume cannot be changed to an unsecure volume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume[Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.
• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress: changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete: changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14
• Added HPE ProLiant Compute DL380a Gen12 Server
• Support Decouple metadata 

o POST Storage.SetEncryptionKey

o PATCH Storage[EncryptionMode]

o PATCH/POST Volume[Encrypted]

• Note: MR controller support SED only. Therefore, Volume[EncryptionTypes] is not writeable during POST (Create) or PATCH (Update). Correspondingly the following Annotations are not populated:

a. EncryptionTypes@Redfish.AllowableValues (Volume Schema)

b. @Redfish.WriteableProperties[EncryptionTypes] (Volume Schema)

c. EncryptionTypes@Redfish.OptionalOnCreate (Volume Capabilities)

d. EncryptionTypes@Redfish.AllowableValues (Volume Capabilities)

e. EncryptionTypes@Redfish.UpdatableAfterCreate (Volume Capabilities)

o POST Volume.ForceEnable

o POST Drive.RevertToOriginalFactoryState

o Note:

• PATCH Volume[Encrypted] can be issued only with option ‘true’ on eligible volumes. PATCH Volume[Encrypted] with option ‘false’ will befailed because a secure volume cannot be changed to an unsecurevolume in MR firmware.
• During POST (Create) ‘Encrypted’ option is not allowed for creating a volume with RAIDType=None. This is because MR does not support creating a secure JBOD in one step. After creating the JBOD, PATCH Volume [Encrypted = true] can be issued to create a secure JBOD.
• Whenever user requests to change to EKM, a reboot is a must to obtain the key via UEFI driver.

• Add MR408i-p support
• Added support for UBM10 backplanes
• Support UBM backplane FW version display and FW update when UBM controller is in bootloader state if there is an interruption during FW update
• Support NVMe SSD for Unmap capable Logical Drive. Please note that SATA SSD is not supported for Unmap capable Logical Drive.
• NAND flash refresh improvements

o The algorithm that posts the event "System reset required" after a specified  number of days has been removed. The refresh happens after the same specified time and the new events are populated as below:

• Before starting the Nand flash refresh: “NAND refresh in progress:changing WB Logical Drives to WT”
• After the completion of Nand flash refresh: “NAND refresh complete:changing WT virtual disks to WB”
• The above behaviors are applicable only to MR400 controllers and are not applicable to MR200 controllers
• RAID1 Consistency Check Event String Change

o The Event String has been changed from "Consistency Check found inconsistent parity on LD <Ld Id> at strip <Strip Number>" to "Consistency Check found inconsistency on LD <Ld Id> at strip <Strip Number>".

• Support a new controller property, "Spin Down Drives At Shutdown", to control spindown of configured drives during shutdown
• Support for SCSI NVMe Translation Layer Specification version 1.14

The raw driver files can be obtained by extracting the Smart Component and then extracting the Emulex installer.  Use this command:

    elxdrvr-fc-version.exe /q2 extract=2

The extracted files are located:

    C:\Users\Administrator\Documents\Emulex\Drivers\FC-version

Each kit folder has subsequent architecture folders with subsequent OS folders.  For example,

    C:\Users\Administrator\Documents\Emulex\Drivers\FC-version\x64\win2022

Enhanced Chinese translation support for some options. e.g. "core", "enabled", "disabled", "locked", etc.

Grayed out RBSU "pcie data link feature" option in "System Configuration > BIOS/Platform Configuration (RBSU) > PCIe Device Configuration > Advanced PCIe Configuration".

Added support for 2-DIMM and 4-DIMM population.

Added RBSU "HardwarePM Interrupt" option in "System Configuration > BIOS/Platform Configuration (RBSU) > Power and Performance Options > Advanced Power Options".

Added the "Smooth Cooling" selection to the Thermal Configuration option in the RBSU\Advanced Options\Fan and Thermal Options. This selection modifies the fan speed response to improve acoustics by reducing the rate of fan speed changes. This can improve acoustics for workloads which significantly vary CPU utilization. Note that this option can result in a small reduction in performance due to the short durations of CPU thermal throttling and some operating systems, such as Linux, may log CPU thermal throttling events. These events do not indicate an issue with the system and can be ignored.

Added Secure Boot Key Microsoft Option Rom UEFI CA 2023.

    o /cx show spindownatshutdown
    o /cx set spindownatshutdown {[sashdd=<on|off>] [satahdd=<on|off>]
        [sasssd=<on|off>] [satassd=<on|off>] [nvmessd=<on|off>]}

• Adjust the RAID1 consistency related error message
• Added HPE ProLiant Compute DL380a Gen12 Server support

    o /cx show spindownatshutdown
    o /cx set spindownatshutdown {[sashdd=<on|off>] [satahdd=<on|off>]
        [sasssd=<on|off>] [satassd=<on|off>] [nvmessd=<on|off>]}

• Adjust the RAID1 consistency related error message

    o /cx show spindownatshutdown
    o /cx set spindownatshutdown {[sashdd=<on|off>] [satahdd=<on|off>]
        [sasssd=<on|off>] [satassd=<on|off>] [nvmessd=<on|off>]}

• Adjust the RAID1 consistency related error message
• Added HPE ProLiant Compute DL380a Gen12 Server support

    o /cx show spindownatshutdown
    o /cx set spindownatshutdown {[sashdd=<on|off>] [satahdd=<on|off>]
        [sasssd=<on|off>] [satassd=<on|off>] [nvmessd=<on|off>]}

• Adjust the RAID1 consistency related error message

Firmware Dependencies:

Enhancements/New Features:

This is the initial version of the firmware.

Known Issues: