Stop Using the Base TCP Profile!
[Update 1 Mar 2017: F5 has new built-in profiles in TMOS v13.0. Although the default profile settings still haven't changed, there is good news on that from as well.]
If the customer data ...
Published Oct 14, 2015
Version 1.0Martin_Duke
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.Ret. Employee
Martin_Duke
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.Ret. Employee
MarS_269999
Nimbostratus
Feb 28, 2018Why not make a TCP profile per services publishing. Example is tcp-ms-share-point. In my opinion is this the best option. For example, I have a share point with large file transfer. Without F5 the download to the client is 60Mbps and through F5 is max 40Mbps. This is really frustrating to tune. In my case on 13.1.0.3 is the best option tcp-lan-optimized with some tuning. I have tried mptcp-mobile-optimized and in my case is really not an option. The worst thing is that a costumer won't switch to F5 ADC as work better directly on MS.