Bug ID 1117637: FastL4 traffic traversing tunnel may fail on VELOS and rSeries tenants

Last Modified: Aug 16, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
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, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1_RELEASE

Opened: Jun 21, 2022
Severity: 3-Major

Symptoms

BIG-IP tenants running on an VELOS or rSeries system may incorrectly attempt to PVA accelerate traffic that goes through a tunnel, i.e. where the pool members are reachable through a VXLAN tunnel.

Impact

Connections fail. A packet capture from the F5OS layer shows packets arriving at the system, but not being forwarded through the tunnel. A packet capture in the tenant shows packets arriving at TMM, but with layer 3 and layer 4 headers rewritten to match the serverside connection information.

Conditions

-- BIG-IP tenant running on VELOS or rSeries -- Virtual server that processes traffic over a tunnel, i.e. a VXLAN tunnel

Workaround

FastL4 acceleration is not supposed to work for traffic being load-balanced over a tunnel. To mitigate this issue, disable PVA acceleration in the FastL4 profile for virtual servers that will load-balance traffic over a tunnel.

Fix Information

None

Behavior Change