NVIDIA MBF2H516A-EENO DPU Firmware 24.43.1014

Firmware which is added at the time of manufacturing, is used to run user programs on the device and can be thought of as the software that allows hardware to run. Embedded firmware is used to control the functions of various hardware devices and systems, much like a computer’s operating system (OS) controls the function of software applications. Firmware may be written into read-only memory (ROM), erasable programmable read-only memory (EPROM) or flash memory.

NVIDIA BlueField-3 DPU provides innovative acceleration, security, and efficiency in every host. BlueField-3 data center infrastructure combines the power of the NVIDIA ConnectX-6 Dx with programmable Arm cores and hardware offloads for software-defined storage, networking, security, and management workloads.

NVIDIA BlueField-3 also delivers superior performance, security, and reduced TCO for cloud computing platforms, enabling organizations to efficiently build and operate virtualized, containerized, and bare-metal infrastructures at massive scale.

Changes and New Features:

- 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.
- Enabled hotplug/hotunplug during device's power off or power cycle to prevent the device from getting stuck.
- Added support for 2-steps-hotplug capability. The device is plugged with "free" status by default, and it will not appear on the bus until being modified to "hotplug" status.

Bug Fixes:

- Added a recovery step in case of CQ doorbell getting lost during VF migration.
- Fixed the query for FACTORY default NV configuration values. The firmware always returned the "next" value to be applied.
- Some pre-OS environments may fail when sensing a hot-plug operation during their boot stage.

Known Issues:

- When decapsulation on a packet occurs, the FCS indication is not calculated correctly.
- PHYless Reset is currently not supported.
- Unexpected system behavior might be observed if the driver is loaded while reset is in progress.
- When tx_port_ts is set to "true", due to a compensation mechanism in the Tx timestamp available in some hardware Rx timestamp errors, a symmetrical error and no clock offset occur when using the timestamps to synchronize the device clock. This might also cause an error while using timestamps for delay measurements (e,g., delay measurements reported by a PTP daemon) and even negative delay measurements in some cases.
- When unloading the network drivers on an external host, sync1 reset may be still reported as 'supported' although it is not. Thus, initiating the reset flow may result in reset failure after a few minutes.
- Disabling the Relaxed Ordered (RO) capability (relaxed_ordering_read_pci_enabled=0) using the vhca_resource_manager is currently not functional.
- fwreset is currently supported on PCI Gen 4 devices only.
- The firmware rollback fails for the signature retransmit flow if the QPN field is configured in the mkey (as it only allows the given QP to use this Mkey) as the firmware rollback flow relies on an internal QP that uses the mkey.
- MFS1S50-H003E cable supports only HDR rate when used as a split cable.
- CRC is included in the traffic byte counters as a port byte counter.
- The "max_shaper_rate" configuration query via QEEC mlxreg returns a value translated to hardware granularity.
- GTP encapsulation (flex parser profile 3) is limited to the NIC domain. Encapsulating in the FDB domain will render a 0-size length in GTP header.
- Some pre-OS environments may fail when sensing a hot plug operation during their boot stage.
- Servers do not recover after configuring PCI_SWITCH_EMULATION_NUM_PORT to 32 followed by power cycle.
- When working with 3rd party device (e.g., Paragon) in 25GbE speed, the 25GbE speed must be configured in force mode.
- Occasionally, when rising a logical link, the link recovery counter is increase by 1.
- Forward action for IPoIB is not supported on RX RDMA Flow Table.

About Network Adapter Drivers:

When connected, the operating system usually installs a generic driver that helps the computer to recognize the newly attached device.

However, proper software must be applied if you want to make use of all features that the network adapter has available. This task also allows computers to properly recognize all device characteristics such as manufacturer, chipset, technology, and others.

Updating the adapter's drivers and utilities version might improve overall performance and stability, increase transfer speeds, fix different compatibility problems and several network-related errors, as well as bring various other changes.

To install this release, simply get the package, extract it if necessary, run the setup, and follow the instructions displayed on-screen. When done, don't forget to perform a system restart and reconnect the network adapter to make sure that all changes take effect properly.

Without further ado, if you intend to apply this version, click the download button and install the package. Moreover, check with our website as often as possible so that you don't miss a single new release.