Bug ID 747585: TCP Analytics supports ANY protocol number

Last Modified: May 29, 2024

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

Known Affected Versions:
12.1.4, 12.1.4.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4

Fixed In:
15.1.0, 14.1.2.1, 13.1.3.4, 12.1.5

Opened: Oct 22, 2018

Severity: 4-Minor

Symptoms

No TCP analytics data is collected for an ANY virtual server.

Impact

No TCP analytics data is collected for TCP flows when a virtual server's protocol number is ANY.

Conditions

1. Provision AVR 2. Create a FastL4 server that accepts all protocols. 3. Attach a TCP Analytics profile 4. Try to run UDP traffic through it.

Workaround

There is no workaround this time.

Fix Information

TCP analytics now supports both ANY and TCP protocol numbers and would collect analytics for TCP flows if protocol number is ANY or TCP.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips