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.

Forum Discussion

What_Lies_Benea's avatar
What_Lies_Benea
Icon for Altostratus rankAltostratus
May 07, 2015

I suppose there are at least three reasons;

 

1) The profile defines the initial options which would hopefully be tuned well for the majority of clients

 

2) MSS, Windows Scale and SACK can only be specified during initial connection setup and thus, you would want to set these to an optimal value based on your needs

 

3) The profile obviously allows you to enable or disable some features and settings and this ensures the adaptive optimisation does/does not make use of them; you are given control of what is or is not used

 

  • dragonflymr's avatar
    dragonflymr
    Icon for Cirrostratus rankCirrostratus
    May 07, 2015
    Thanks, seems thar I have to dig around a little more and do some test to understand all the nuances.
  • What_Lies_Benea's avatar
    What_Lies_Benea
    Icon for Altostratus rankAltostratus
    May 08, 2015
    Indeed, there are many ambiguous areas like this I've found. v11.6 certainly gives you more control via iRules, allowing you to change the congestion control algorithm for instance. See here for more: https://clouddocs.f5.com/api/irules/TCP.html. TCPExpress will only use the algorithm you specify in the profile. No doubt this is one of the 'extras' that AAM provides. You could do it manually now with iRules (checking the User-Agent for a mobile browser for example) but AAM makes it 'push button' easy.