Last Modified: Oct 03, 2026
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1, 17.1.3.2, 17.1.3.4, 17.1.3.5, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 17.5.1.6, 17.5.1.8, 17.5.1.9, 21.0.0, 21.0.0.1, 21.0.0.2, 21.0.0.3, 21.1.0, 21.1.0.1, 21.1.0.2
Opened: Jun 26, 2026 Severity: 2-Critical Related Article:
K000161773
When Azure rescinds or re-presents an SR-IOV Virtual Function (VF) on a BIG-IP VE with Accelerated Networking, the data interface associated with that VF will stop forwarding traffic and will not recover automatically without manual intervention. Other interfaces remain unaffected. The Traffic Management Microkernel (TMM) does not crash, but you may see the following messages in the kernel logs: - pci_hyperv: PCI dom# 0x<N> has collision, using 0x<M> - mlx5_core <addr>: no netdev found for vf serial <N>
Traffic on the affected interface stops. Associated pool members and virtual servers become unavailable. Recovery requires restarting TMM or rebooting
- BIG-IP VE is deployed on Microsoft Azure - Accelerated Networking is enabled on the VM - The Azure platform may rescind and re-present the SR-IOV VF during host maintenance, platform servicing, or other internal Azure events that might not be visible to the tenant or reflected in scheduled event notifications - VF re-presentation results in a PCI domain collision in the guest kernel
Restart TMM to restore traffic forwarding: bigstart restart tmm or reboot the unit
None