Bug ID 1411365: CMP forwarded flows can be removed by other CMP forwarded flows incorrectly

Last Modified: Mar 12, 2025

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

Known Affected Versions:
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, 15.1.7, 15.1.8, 15.1.8.1, 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, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1

Opened: Dec 07, 2023

Severity: 3-Major

Symptoms

BIG-IP may fail to forward server-side traffic if flow forwarding occurs due to an overload scenario, specifically due to flow collisions on the server-side connection when using the source-port preserve-strict option with UDP virtual configuration.

Impact

Forwarding flow removes the existing flow and causes traffic to be dropped.

Conditions

BIG-IP configured with UDP virtual configuration with source-port preserve-strict. - CMP forwarding occurs when traffic on ingress is managed by a different TMM on egress. - Overload condition occurs on TMM that leads to forwarding the flow by keeping server-side connection. - Forwarded flow causes existing connection flow to be removed and interrupts current traffic flow.

Workaround

Clear the existing connection from the connection table. For more information, refer to the article K53851362: Displaying and deleting BIG-IP connection table entries from the command line.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips