Tuning the TCP Profile, Part One

A few months ago I pointed out some problems with the existing F5-provided TCP profiles, especially the default one. Today I'll begin a pass through the (long) TCP profile to point out the latest thi...
Published Jan 29, 2016
Version 1.0
application delivery
LTM
management
performance
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
tomas_prosecky_'s avatar
tomas_prosecky_
Icon for Nimbostratus rankNimbostratus
Nov 24, 2017

And what is the reason the default tcp profile buffer rules predefined on F5 is against the rules mentioned ?

 

tcp: Proxy buffer high: 49152 bytes Proxy buffer low: 32768 bytes Receive window: 65535 bytes Send buffer: 65535 bytes

 

Also the tcp wan optimized and tcp lan optimized does not follow the last mentioned?

 

Proxy Buffer High should be significantly larger than Proxy Buffer Low (we like to use a 64 KB gap) to avoid constant flapping to and from the zero-window state on the receive side.