Max Recommended Idle TCP timeout and Keep alive interval
I have a scenario where users are running scripts that run through a virtual server but are getting closed after the default 300 second idle timeout. The reason is the script sends commands to the VS to run and waits for a response. At times the jobs finish under five minutes but there are a lot of jobs that run longer which lead to false positives causing errors. I have increased the tcp idle timout and keep alive temporarily but main question is is there a "MAX" recommended setting for idle timeout and keep alive. I know it can be set to indefinite but I do not know if that is wise as it could lead to port exhaustion. Any tips would be great, Thanks
2 factor authentication with different timeouts
I have some APM policy working with one and two factor authentication. But now we need to have a two factor authentication with different timeouts for the second factor. Example: Client connect in the morning and have a full login with 2 factor. First is LDAP second is RSA over Radius. After 2 hours the client come back and need a re authentication but now we want to check only LDAP. But after one day we want both factors. Idea is to write an additional cookie with encoded string of username and last logon. Then the F5 can check this during the authentication and/or set. But I don’t know how. Thanks for our help
Application Logged Out when Idle . . .
Hey friends, I have a problem .... when we access application using a server directly, it is stabil (NOT LOGGED OUT), but when accessing it using the F5 application and idle, the application back to the login menu (LOGGED OUT), but if we click on the menu quickly (INTENS), is not logged OUT. We have already setting an "indefine" idle time out in tcp profile, and we have also tried giving an idle time out of more than 5 minutes, but the application is still logged out when we accessed less than 1 minute if idle. AnyOne Help for this case??Client Persistence Profile with Idle timeout
If you have a Client Persistence Profile with Idle timeout of 30 seconds, and if the client has been Idle for more then 35 Seconds. What happens to their next connection?. Will they have to be load balanced again or consequently sent to the same server again? etc. Thanks
Force Application logout?
I am trying to see if it is possible to have the F5 force a logout when the idle time has been met. We have a web application that is behind the F5 using LTM. I used the http iApp template to configure this virtual server. We are using SSL bridging and the application is providing the login page. In my testing I am not able to get any kind of idle timeout to happen and I am told the application doesn't have a timeout set. Am I wasting my time trying to get the F5 to logout when the connection is idle? I am running version 12.1.3.4 Thank you for your help!
Config option for default SNAT translation idle timeout?
SNAT translation addresses by default have an 'indefinite' timeout for TCP, UDP, and IP. This can be set on a per-object basis when the new translation address is configured. Is it possible to configure a 'global' value to apply to any new SNAT translation? I.e.: Set the TCP idle timeout to xxx seconds for new SNAT translation unless explicitly set otherwise? I checked through some locations (global settings, DB variables) and didn't see anything that appeared to allow this.