Forum Discussion
Bigip fastL4 Protocol
I have the following settings in the bigip and i figured out comparing another bigip using TCP protocol that the active connections showing in the performance data graphs became about 4 times more than the real connections taken from the bigip command line.
Also when i changed the Idle Timeout time from 300(default) to 60 the active connections showing in the performance data graphs became about 2 times more than the real connections taken from the bigip command line.
Protocol:fastL4
↓
Settings
↓
Idle Timeout:300
I think that the connections dependicity is on the server and Idle Timeout in the BigIp settings on the above example can set it to 0 without any problem.
Can you confirm if this is correct?
3 Replies
- i do not think it is good to set immediate idle timeout for a connection which needs to maintain state.
- Remember that the fastL4 profile will also by default send an RST to both ends of the connection when it expires. So if you set it too low, you will actually kill off valid connections. Which may not always be what you want (I often set low timeouts on fastL4 profiles attached to network virtual servers. But also disable RST and enable loose-open/loose-close which makes the VS more like a router.
- thank you for your response.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com