This page lists changes in NVIDIA DOCA™ that affect compatibility, interfaces, or support for features, operating systems, and NVIDIA® BlueField® and NVIDIA® ConnectX® devices.
Changes in This Release
|
Component |
Version |
Description |
Customer Impact and Recommendation |
|---|---|---|---|
|
DOCA |
3.6.0 (Oct 2026) |
DOCA 3.6 is the last DOCA release to support ConnectX-4 Lx and ConnectX-5. DOCA 3.6 is a long-term support (LTS) release that receives bug fixes and CVE updates for 3 years. DOCA 4.0 (January 2027) does not support these devices. |
Customers who use ConnectX-4 Lx or ConnectX-5 adapters should stay on the DOCA 3.6 LTS branch, which receives bug fixes and CVE updates for 3 years. To use DOCA 4.0 or later, move to a supported adapter. |
|
DOCA Services and Libraries |
3.6.0 (Oct 2026) |
Support for App Shield, BlueMan, and Flow Inspector is discontinued. |
DOCA 3.6.0 no longer supports the DOCA Flow Inspector service, DOCA BlueMan service, or DOCA App Shield library. DOCA 3.5.0 is the last release that supports these components. |
|
BFB-Install |
3.6.0 (Oct 2026) |
DOCA 3.5.0 (July 2026) is the last release to support the BFB-Install tool. Starting with DOCA 3.6.0, DOCA-Installer replaces the functionality that BFB-Install provided. |
No recommendation is available yet. |
|
DOCA Flow |
3.6.0 (Oct 2026) |
Execution Order of VLAN Push and Field Modify: In pipes that combine a VLAN push with a field modify, DOCA 3.6 runs the push before the field modify and the pipe's action descriptors, as DOCA 3.4 and earlier did. DOCA 3.5 ran the push after them. Pipes that have a VLAN push but no field modify aren’t affected, because their action descriptors already run after the push. |
Starting with DOCA 3.6, a field modify or action descriptor on |
|
DOCA Flow |
3.6.0 (Oct 2026) |
Removal of the global CT configuration API: |
Code that calls those APIs would not compile. User should configure CT with the per-system, per-port and per-pipe CT setters; see the CT Configuration section of the DOCA Flow Connection Tracking guide and the |
|
DOCA Flow |
3.6.0 (Oct 2026) |
Deprecation of the CT flag |
Compiling source code that uses the flag now produces a deprecation warning. Runtime behavior and ABI compatibility are unchanged. Remove the flag from the value you pass to |
|
DOCA-Host |
3.6.0 (Oct 2026) |
Manual Enablement of SF Auxiliary Devices: With the new implementation, mlxdevm sub-functions are no longer probed automatically with all auxiliary sub-devices, such as Ethernet and RDMA. Previously, when an SF was created and activated, all relevant auxiliary sub-devices were probed by default. Now, the SF is initially probed without auxiliary sub-devices, and each required auxiliary device must be enabled manually. |
To manually enable each required auxiliary device, the user must:
For example:
|
|
DOCA-Host |
3.6.0 (Oct 2026) |
RoCE Configuration Interface Update: The sysfs interface previously used to configure the RoCE state ( |
Users should now use mlxdevm to enable or disable RoCE on a port. Example:
|
|
DOCA-Host |
3.6.0 (Oct 2026) |
MAC Address Configuration Interface Update: MAC address configuration through sysfs is deprecated. |
Use
|
|
DOCA-Host |
3.6.0 (Oct 2026) |
DOCA-Host 3.6.0 removes the
The |
You must update any automation, CI/CD pipelines, or custom scripts that call these components. Installations that use the DOCA Installer or a Linux package manager ( Replace the removed components as follows:
As a result of this change, the BMC on BlueField-2 and BlueField-3 no longer reports the OFED version. The |
|
DOCA Firefly |
3.6.0 (Oct 2026) |
DOCA Firefly and Driver Upgrade Dependency: On Linux kernel 7.0 or later, the driver reports fractional frequency offset (FFO) values in parts per trillion (PPT) through the dedicated PPT attribute. Earlier drivers sent them through the legacy parts per million (PPM) attribute. DOCA Firefly 1.7.8-doca3.6.0 reads the new attribute. |
If you use SyncE with the DPLL backend on Linux kernel 7.0 or later, upgrade DOCA Firefly to 1.7.8-doca3.6.0 and DOCA-HOST to 26.10 together. Using DOCA Firefly 1.7.8-doca3.6.0 with an earlier driver, or DOCA-HOST 26.10 with a DOCA Firefly version earlier than 1.7.8, results in incorrect FFO reporting. Deployments that do not use SyncE are not affected. |
|
DOCA HBN |
3.6.0 (Oct 2026) |
In the HBN preparation script ( |
Scripts and automation that provide plaintext passwords continue to work but produce a deprecation warning. Plaintext support is planned for removal in a future major release (no earlier than 2027 H1). Generate a SHA-512 hashed password with |
|
DOCA HBN |
3.6.0 (Oct 2026) |
The HBN preparation script ( |
User creation that passes an empty string to |
Changes Planned for Future Releases
|
Component |
Version |
Description |
Customer Impact and Recommendation |
|---|---|---|---|
|
DOCA Flow |
4.0 (Jan 2027) |
In DOCA 4.0, support for Crypto and NAT64 actions is removed from the Basic pipe. |
For Crypto and NAT64 functionality customers should use |
|
DOCA Flow |
4.0 (Jan 2027) |
Removal of system-wide resource APIs: In DOCA 4.0, the declarations for the following system-wide shared-resource APIs are removed from
The declaration for |
Existing binaries are unaffected. Applications built against pre-4.0 headers continue to link and run against DOCA 4.0 without relinking or behavior changes. The legacy symbols remain exported, and the system-wide resource behavior is preserved for these binaries. Source migration is required. Code rebuilt against the DOCA 4.0 headers no longer compiles if it calls the removed APIs or references Use the following replacements:
Migration requirements:
For implementation examples, see |
|
DOCA-Host |
4.0 (Jan 2027) |
DOCA-Host introduces new Host Packs to replace current DOCA-Host Profiles. DOCA-Host-Packs allows better resolution of DOCA installation, where each Pack includes a smaller part of DOCA libs. Packs can be installed alone, or more than one on a host. DOCA-Host-Packs include:
|
Customer automation and installation flows must be updates with the new DOCA-Host-Packs. To align with existing DOCA-Host Profiles, users should install:
|
|
DOCA-Host |
4.0 (Jan 2027) |
DOCA-Host remove support for kernels older than 5.14, meaning support for Host OS with kernel 4.18 and 5.10 will be dropped. Customers who want to keep using such OS can keep using DOCA 3.6 LTS for 3 years. |
|
|
DOCA HBN |
4.0 (Jan 2027) |
Alignment of the NVUE CLI with the Common Object Model: DOCA Host-Based Networking (HBN) 4.0.0 aligns the NVIDIA User Experience (NVUE) command-line interface and object model with the Common Object Model (Common-OM). This keeps configuration consistent across HBN, Cumulus Linux, and other NVUE implementations. The change isn't backward compatible. It affects configuration paths, accepted values, the hierarchy of
|
Before upgrading to HBN 4.0.0, update any configuration templates, provisioning and operational scripts, NVUE API integrations, and To migrate:
For the complete list of changed commands, see HBN 4.0.0 NVUE Command Changes. |
|
DOCA |
4.3 (Oct 2027) |
ConnectX-6 Adapters and BlueField-2 DPU Adapters End-of-Life: The October 2027 DOCA release is the last to support ConnectX-6 and BlueField-2. It is an LTS release supported for 3 years. The following release (January 2028) does not support these devices. |
No recommendation is available yet. |
|
DOCA |
4.0 (Jan 2027) |
DOCA 4.0 introduces the new SPX-ARC (Adaptive RDMA Connection) service, to support NVIDIA’s high‑performance, resilient multiplane networking service (Spectrum-X), local and remote link failure as well as future transport enhancement. This service replaces DOCA XPlane |
|
|
DOCA PCC |
4.0 (Jan 2027) |
DOCA 4.0 introduces fixes to undocumented PCC STABLE API return values |
Affects all user applications on top of DOCA PCC library |
Changes from Earlier Releases
This section provides a list of changes from the previous two releases that broke compatibility or interfaces, or discontinued support for features or operating system versions.
For older changes, consult the DOCA documentation archive.
|
Component |
Version |
Description |
Customer Impact and Recommendation |
|---|---|---|---|
|
DOCA Apps |
3.5.0 (Jul 2026) |
DPDK queue-count initialization in |
Apps/samples that set |
|
DOCA Flow |
3.5.0 (Jul 2026) |
Deprecation of system-wide resource APIs (stable): The following system-wide resource sizing and binding APIs are deprecated in DOCA 3.5: |
Compiling source code that uses the deprecated APIs now produces deprecation warnings. ABI compatibility is unchanged in this release, and the corresponding symbols remain exported, so existing binaries continue to link and run without modification. Migrate applications to the per-port resource model by using the following APIs:
Before calling
In DOCA 3.5, the replacement APIs are experimental and produce an experimental-API compilation warning. Define During migration, define |
|
DOCA Pipeline Language |
3.5.0 (Jul 2026) |
Support for DOCA Pipeline Language (DPL) has been discontinued in NVIDIA DOCA 3.5.0 and later releases. DPL is not supported on BlueField-4 platforms. DPL remains in maintenance mode for BlueField-3 devices on the 3.2.x, 3.3.x, and 3.4.x release branch. |
Customers that require DPL must remain on a supported BlueField-3 release. Before upgrading to NVIDIA DOCA 3.5.0 or later or moving to BlueField-4, migrate DPL-based applications to the DOCA Flow library. Do not use DPL for new deployments. |
|
DOCA |
3.4.0 (Apr 2026) |
Virtio-net and virtio-blk support for BlueField-2 devices will be removed from DOCA GA release. BlueField-2 virtio-net will continue to be available in the current LTS branches (DOCA 2.9.x and DOCA 3.2.x). |
BlueField-2 customers interested in using virtio-net should use one of the LTS branches. |
Discontinued Features
List of features which are supported in previous generations of hardware devices:
-
N/A
Last updated: