Bug ID 1267221: When TMM starts, Hyper-V shows no RX packets on the ethX interface

Last Modified: Jun 28, 2025

Affected Product(s):
BIG-IP Install/Upgrade, LTM, TMOS(all modules)

Known Affected Versions:
14.1.5.3, 14.1.5.4, 14.1.5.6, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6

Fixed In:
17.5.1

Opened: Mar 02, 2023

Severity: 2-Critical

Symptoms

BIG-IP Virtual Edition (VE) running on a Hyper-V host, when TMM starts, it sets the NIC queue count. When this happens, due to a bug in Hyper-V, ingress packets are no longer received on the data plane interfaces. Packets egressed from TMM are being correctly sent to peer devices on the network.

Impact

The data plane interfaces does not show ingress counters incrementing and no traffic is seen on the interface.

Conditions

- After upgrading from BIG-IP version 12, none of the data plane interfaces show ingress counters incrementing and no traffic is seen on the interface. The Management interface works properly.

Workaround

In Hyper-V manager, save the machine state and then start it back up or use a legacy network adapter.

Fix Information

This change provides a workaround to not set the NIC queue counts if they are already set properly. To utilize this workaround the amount of memory should be verified so that the number of TMMs equals the number of CPUs on the VM. A new log message in /var/log/tmm will log whether or not TMM changed the queue count.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips