Bug ID 747585: TCP Analytics supports ANY protocol number

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3,,,,,,,, 12.1.4,, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,, 14.1.0,,,,,, 14.1.2, 15.0.0, 15.0.1,,,,

Fixed In:
15.1.0,,, 12.1.5

Opened: Oct 22, 2018
Severity: 4-Minor


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


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


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.


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