Networking DOCA SDK Documentation

Customer Affecting Changes

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 outer.eth_vlan[0].tci in these pipes edits the pushed tag, on both tagged and untagged packets. In DOCA 3.5, it edited the packet’s original tag instead, and it had no effect on untagged packets. This change restores the DOCA 3.4 behavior, so only applications written for the DOCA 3.5 order are affected. To edit the packet's original tag, do it in a preceding pipe.

DOCA Flow

3.6.0 (Oct 2026)

Removal of the global CT configuration API: doca_flow_ct_init(), doca_flow_ct_destroy(), doca_flow_ct_cfg_create() / doca_flow_ct_cfg_destroy() and the doca_flow_ct_cfg_set_*() setters no longer exist.

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 flow_ct samples.

DOCA Flow

3.6.0 (Oct 2026)

Deprecation of the CT flag DOCA_FLOW_CT_FLAG_WORKER_STATS: The flag in enum doca_flow_ct_flags no longer has any effect.

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_flow_port_cfg_set_ct_flags(). The flag is planned for removal in the next major release.

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:

  1. Create and activate the SF.

  2. Enable the Ethernet auxiliary device.

  3. Reload the auxiliary device to fully probe the SF after enabling the required auxiliary device.

For example:

  1. Create and activate the SF.

    /opt/mellanox/iproute2/sbin/mlxdevm port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 11
    /opt/mellanox/iproute2/sbin/mlxdevm port function set pci/0000:08:00.0/32768 state active
    
  2. Enable the Ethernet auxiliary device.

    /opt/mellanox/iproute2/sbin/mlxdevm dev param set auxiliary/mlx5_core.sf.1 name enable_eth value true cmode driverinit
    
  3. Reload the auxiliary device to fully probe the SF after enabling the required auxiliary device.

    /opt/mellanox/iproute2/sbin/devlink dev reload auxiliary/mlx5_core.sf.1
    

DOCA-Host

3.6.0 (Oct 2026)

RoCE Configuration Interface Update: The sysfs interface previously used to configure the RoCE state (/sys/bus/pci/devices/0000:00:08.0/roce_enable) is no longer supported.

Users should now use mlxdevm to enable or disable RoCE on a port.

Example:

mlxdevm dev param set pci/0000:08:00.0 roce <enable|disable>

DOCA-Host

3.6.0 (Oct 2026)

MAC Address Configuration Interface Update: MAC address configuration through sysfs is deprecated.

Use devlink or mlxdevm to configure the MAC address for the ECPF, PF vport, or VF vport:

  1. Discover the relevant port index.

    devlink port show
    

    Example:

    pci/0000:03:00.0/65536: flavour pci_pf controller 1 pf 0 external
    pci/0000:03:00.0/65537: flavour pci_vf controller 1 pf 0 vf 0 external
    pci/0000:03:00.0/65538: flavour pci_vf controller 1 pf 0 vf 1 external
    
  2. Set the MAC address using the relevant port index.

    devlink port function set pci/0000:03:00.0/<port_index> hw_addr <mac>
    

    Example mappings:

    Host PF    vport 0 → pci/0000:03:00.0/65536
    Host VF 0  vport 1 → pci/0000:03:00.0/65537
    Host VF 1  vport 2 → pci/0000:03:00.0/65538
    

DOCA-Host

3.6.0 (Oct 2026)

DOCA-Host 3.6.0 removes the ofed_scripts package from all DOCA-Host profiles. The following components are no longer available:

  • ofed_info and ofed_rpm_info

  • ofed_uninstall.sh

  • sysinfo-snapshot.py

  • install.pl

  • vendor_pre_uninstall.sh and vendor_post_uninstall.sh

The openibd script is not part of ofed_scripts and isn't affected by this change.

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 (apt or yum) aren't affected.

Replace the removed components as follows:

  • ofed_info: Query DOCA-Host meta-package information with the package manager:

    • Ubuntu/Debian:

      apt info doca-networking
      
    • RHEL/Rocky:

      yum info doca-networking
      
  • sysinfo-snapshot.py: Use doca-sosreport.

  • ofed_uninstall.sh: Older MLNX_OFED and DOCA-Host versions still include this script for backward compatibility, and you can use it to uninstall MLNX_OFED as part of a DOCA-Host installation. Upgrades between DOCA-Host versions (2.6 and later) don't use it.

As a result of this change, the BMC on BlueField-2 and BlueField-3 no longer reports the OFED version. The Version property of the Redfish DPU_OFED firmware inventory resource (/redfish/v1/UpdateService/FirmwareInventory/DPU_OFED) returns N/A.

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 (hbn-dpu-setup.sh), plaintext password provisioning through -p|--password or through the interactive password prompt is deprecated. Both methods still work in this release, but the script prints a DEPRECATION WARNING to stderr each time they are used.

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 openssl passwd -6 and pass it with -H|--hashed_password instead. For more information, see “Running HBN Preparation Script” in HBN Service Deployment.

DOCA HBN

3.6.0 (Oct 2026)

The HBN preparation script (hbn-dpu-setup.sh) rejects an empty -H|--hashed_password value.

User creation that passes an empty string to -H fails. Before upgrading, update scripts and automation to pass a valid SHA-512 crypt hash ($6$...), for example one generated with openssl passwd -6.

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 Ordered_List pipe.

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 doca_flow.h:

  • doca_flow_cfg_set_nr_counters()

  • doca_flow_cfg_set_nr_meters()

  • doca_flow_cfg_set_nr_shared_resource()

  • doca_flow_shared_resources_bind()

  • doca_flow_shared_resource_set_cfg()

  • doca_flow_shared_resources_query()

The declaration for doca_flow_cfg_set_resource_mode() and the definition of enum doca_flow_resource_mode are also removed. The corresponding symbols remain in the library to preserve binary compatibility for applications built against earlier headers. For applications compiled against the DOCA 4.0 headers, per-port shared resources are the default and only supported resource model.

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 enum doca_flow_resource_mode or DOCA_FLOW_RESOURCE_MODE_*. Migrate the source code to the per-port APIs before rebuilding it against DOCA 4.0. Per-port resource management is the default and only supported model in DOCA 4.0, so remove calls to doca_flow_cfg_set_resource_mode() and all related resource-mode references.

Use the following replacements:

  • doca_flow_cfg_set_nr_counters(), doca_flow_cfg_set_nr_meters(), and doca_flow_cfg_set_nr_shared_resource() → doca_flow_port_cfg_set_nr_resources()

  • doca_flow_shared_resources_bind() → doca_flow_port_shared_resource_get() and doca_flow_port_shared_resource_put()

  • doca_flow_shared_resource_set_cfg() → doca_flow_port_shared_resource_set_cfg()

  • doca_flow_shared_resources_query() → doca_flow_port_shared_resources_query()

  • doca_flow_cfg_set_resource_mode() and enum doca_flow_resource_mode → no replacement; remove the call and any DOCA_FLOW_RESOURCE_MODE_* references

Migration requirements:

  • Configure resource capacity on the port configuration before calling doca_flow_port_start().

  • After the port starts, allocate resource IDs with doca_flow_port_shared_resource_get(), configure and query the resources through the corresponding per-port APIs, and release the IDs with doca_flow_port_shared_resource_put().

  • Translate resource types by name rather than by numeric value. enum doca_flow_resource and enum doca_flow_shared_resource_type are not numerically aligned; DOCA_FLOW_RESOURCE_COUNTER_CT shifts the values that follow IPSEC_SA.

  • Resource IDs are scoped by port and resource type. They start at 0, may be reused after release, and are not guaranteed to increase monotonically. doca_flow_port_shared_resource_get() returns DOCA_ERROR_EMPTY when the configured capacity for that resource type is exhausted.

  • In DOCA 3.5.0, the per-port APIs require calling doca_flow_cfg_set_resource_mode(cfg, DOCA_FLOW_RESOURCE_MODE_PORT) before doca_flow_init(). This call is not required in DOCA 4.0. Isolate it if the source must support both releases.

For implementation examples, see samples/doca_flow/flow_shared_counter and samples/doca_flow/flow_shared_meter.

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:

  • DOCA-Host-Base

  • DOCA-Networking-Core

  • DOCA-GPU-Net

  • DOCA-Storage

  • DOCA-Scientific-AI

  • DOCA-All

  • DOCA-Tools

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-OFED – install DOCA-Host-Base + DOCA-Tools

  • DOCA-Networking – install DOCA-Networking-Core + DOCA Tools

  • DOCA-All – install DOCA-All

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 show output, and ACL validation across routing, EVPN/VXLAN, bridge, system, and service commands:

  • Interface IP hierarchy: The shared interface <interface-id> ip path is split into separate ipv4 and ipv6 branches for addresses, gateways, neighbors, virtual router redundancy (VRR), forwarding, and IPv6 state. VRR operational state moves to vrr-state (up|down).

  • ACL port matching: source-port and dest-port move under match ip tcp or match ip udp. Rules must specify the IP protocol explicitly.

  • State controls: enable (on|off) leaves become state (enabled|disabled). Other affected leaves keep their names but accept enabled and disabled instead of on and off.

Before upgrading to HBN 4.0.0, update any configuration templates, provisioning and operational scripts, NVUE API integrations, and show output parsers that use the affected commands. Commands that use the previous syntax may fail. ACL rules that don't meet the new protocol requirements fail validation.

To migrate:

  1. Replace the ip path in interface commands with the matching ipv4 or ipv6 path. For example, nv set interface <interface-id> ip address <ip-prefix-id> becomes nv set interface <interface-id> ipv4 address <ipv4-prefix-id>.

  2. Move ACL port criteria under match ip tcp or match ip udp, and specify a matching protocol.

  3. Replace enable (on|off) with state (enabled|disabled), and replace other on and off values with enabled and disabled. For example, nv set router bgp enable on becomes nv set router bgp state enabled.

  4. Update the affected nv show and nv unset operations, and the scripts that parse their output.

  5. In a staging environment, validate the migrated configuration, provisioning flows, and automation against HBN 4.0.0.

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

  1. Service name change: DOCA XPlane => DOCA SPX-ARC

  2. SPX congestion control moves from DPA (binary) to run under the new SPX-ARC service, as a service (launch service and tunning params are being changed)

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 dpdk_queues_and_ports_init() is now strictly enforced; the configured queue count is no longer implicitly overridden by available lcores.

Apps/samples that set reserve_main_thread=true with nb_queues=1 fail to initialize. Either set reserve_main_thread=false or use nb_queues >= 2.

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: doca_flow_cfg_set_nr_counters(), doca_flow_cfg_set_nr_meters(), doca_flow_cfg_set_nr_shared_resource(), and doca_flow_shared_resources_bind(). These APIs configure a global resource pool.

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:

  • Use doca_flow_port_cfg_set_nr_resources() to configure resource capacity, such as DOCA_FLOW_RESOURCE_COUNTER and DOCA_FLOW_RESOURCE_METER.

  • Use doca_flow_port_shared_resource_get() and doca_flow_port_shared_resource_put() to allocate and release shared resources.

Before calling doca_flow_init(), enable the per-port resource model:

doca_flow_cfg_set_resource_mode(cfg, DOCA_FLOW_RESOURCE_MODE_PORT)

In DOCA 3.5, the replacement APIs are experimental and produce an experimental-API compilation warning. Define DOCA_ALLOW_EXPERIMENTAL_API to acknowledge and suppress this warning. These APIs may change until they are promoted to stable.

During migration, define DOCA_ALLOW_DEPRECATED_API to suppress warnings from the legacy APIs temporarily.

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: