Bug ID 1106489: GRO/LRO is disabled in environments using the TMM raw socket "sock" driver.

Last Modified: Dec 05, 2024

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

Known Affected Versions:
15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 17.0.0, 17.0.0.1, 17.0.0.2, 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

Fixed In:
16.1.4, 15.1.10

Opened: May 13, 2022

Severity: 3-Major

Symptoms

GRO/LRO packets are not received: "tmctl -d blade tmm/ndal_rx_stats" shows "0" in "lro". The linux host has GRO disabled: "ethtool -k eth1 | grep generic-receive-offload" shows "off".

Impact

Performance is degraded.

Conditions

-- BIG-IP is deployed in a Hyper-V environment. -- Any environment such that "tmctl -d blade tmm/device_probed" displays "sock" in "driver_in_use".

Workaround

Manually enable GRO on the device: ethtool -K eth1 gro on Check that it's enabled with: ethtool -k eth1 | grep generic-receive-offload

Fix Information

When sending large payload, "tmctl -d blade tmm/ndal_rx_stats" shows "1" in "lro". "tmctl -d blade tmm/ndal_dev_status" shows "y:y" (available:enabled) in "lro". The linux host indicates the device has GRO enabled: "ethtool -k eth1 | grep generic-receive-offload" shows "on".

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips