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

san2hosh_306591's avatar
san2hosh_306591
Icon for Nimbostratus rankNimbostratus
Jul 14, 2017

Question on TCP and FastL4 idle timeouts.

We are using the TCP idle timeout as 3600 secs for most of our Virtual servers and recently we started using the Fast L4 for some new virtual servers with a timeout as 7200 secs. But we are in a dile...
application delivery
BIG-IP
LTM
Leonardo_Souza's avatar
Leonardo_Souza
Icon for Cirrocumulus rankCirrocumulus
Jul 14, 2017

The timeout in the TCP or fast L4 should have the same impact. Having 1 hour or 2 hours is not a good approach.

 

The side effect of that can be:

 

F5 - High memory, every open connection needs memory allocated. If you reach 85% you start to see an impact.

 

Server - Similar problem, as F5 keeps the pool member connection up.

 

This solution explains the memory problem:

 

https://support.f5.com/csp/article/K15740