Bug ID 2098861: Single-NIC not supported on Azure Standard_Ds_v5 Series.

Last Modified: Dec 18, 2025

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3

Fixed In:
21.0.0

Opened: Oct 01, 2025

Severity: 3-Major

Symptoms

In Azure/HyperV single NIC VMs, tmm fails to attach to the 1.0 interface.

Impact

As tmm can't successfully attach to the 1nic instance, no data traffic passes.

Conditions

- HyperV or Azure VM that has a single SR-IOV NIC attached to the VM. - Affected instances show `getdb provision.1nic` value as "disable". For 1nic instances, this dbvar should have "enable" value to correctly configure tmm and mgmt networking. - This problem does not happen with 1nic instances using only a synthetic netvsc nic.

Workaround

Configure "provision.1nic" dbar value to "forced_enable" to override the automation behavior: setdb provision.1nic "forced_enable"

Fix Information

Both data connectivity through TMM works in Single-NIC instances deployed in Azure/HyperV.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips