For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Introducing TCP Analytics

I'm pleased to announce that F5® TMOS® 12.1 is the first release to contain our TCP Analytics package. If you would like to measure how well TCP is delivering application data, perform A/B testing, o...
Published Aug 12, 2016
Version 1.0
application delivery
BIG-IP
LTM
series-the-tcp-profile
tcp
Martin_Duke's avatar
Ret. Employee
I work in the Office of the CTO on both F5's standards engagement process in general, and specifically on the application of transport-layer innovation to F5's product line. F5 sponsors my service as Transport Area Director at the Internet Engineering Task Force (IETF), where I help to administer standards development worldwide.
View Profile
Martin_Duke's avatar
Ret. Employee
I work in the Office of the CTO on both F5's standards engagement process in general, and specifically on the application of transport-layer innovation to F5's product line. F5 sponsors my service as Transport Area Director at the Internet Engineering Task Force (IETF), where I help to administer standards development worldwide.
View Profile
Ismael_Goncalv1's avatar
Ismael_Goncalv1
Historic F5 Account
Nov 21, 2017

It seems TCP Analytics are also supported by Forwarding Virtual Servers with FastL4 enabled (Forwarding or Performance L4). However, there is no way to use TCP::analytics to selectively enable/disable collection. Is there a workaround for that? Apparently TCP::analytics always require a TCP Profile on the VS.