Forum Discussion
How to avoid F5 BIGIP LTM close the connections?
My virtualserver in F5 LTM is: virtual VS_172.16.179.11_1521 { snat automap pool ORACLE_1521 destination 172.16.179.11:1521 ip protocol 6 } I need this kind of virtualserver because I need GTM too. The problem is F5 LTM closes the connection after some minutes, and Oracle needs the connections to stay open indefinitely, so What profile do I have to create and assign to this virtualserver, please? (profile in client side and/or server side?) Thx in advance.
3 Replies
- Mar_Kus_64551
Nimbostratus
Setting the tcp timeout value in the tcp profile to indefinite should be enough i think. Of course this should be done on client and serverside then.
- PeteWhite
Employee
Just one point here, you should create a new TCP profile with a parent of the main TCP profile and just make the changes required to your new profile. If you make major changes to the main TCP profile this will affect a number of virtual servers. Obviously, leaving connections open for a long period has an impact on the f5 so should be limited only to virtual servers where it is required, and use the shortest possible timeout. eg 1 hour rather than indefinite. There are a number of settings available, these should be considered for their benefits Look Here
- almudena_3796
Nimbostratus
thank both of you
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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