Bug ID 845629: Hv_netvsc vmbus_17 timeout at boot causes reduced NIC performance

Last Modified: Jan 16, 2024

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1

Fixed In:
16.0.0, 15.1.4, 14.1.4.4

Opened: Nov 01, 2019

Severity: 2-Critical

Symptoms

-- Uneven unic channel distribution and transmit errors seen in /proc/unic. -- Packet loss and increased retransmissions under load. -- Errors reported in dmesg: hv_netvsc vmbus_17 (unregistered net_device): timeout before we got a set response....

Impact

-- Reduced throughput. -- Packet loss and increased retransmissions under load.

Conditions

BIG-IP Virtual Edition (VE) in Azure boots while the hypervisor is under high load.

Workaround

This condition occurs when a timeout occurs when booting, resulting in the NIC driver not getting necessary information from the hypervisor. Rebooting the BIG-IP VE may clear the condition if the hypervisor load has reduced.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips