Last Modified: Nov 07, 2022
See more info
Known Affected Versions:
15.1.7, 184.108.40.206, 15.1.6, 220.127.116.11, 15.1.5, 18.104.22.168, 14.1.5, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.4, 22.214.171.124, 14.1.3
Opened: Jun 21, 2022
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.
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.
-- BIG-IP tenant running on VELOS or rSeries -- Virtual server that processes traffic over a tunnel, i.e. a VXLAN tunnel
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.