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

Lazar_92526's avatar
Lazar_92526
Icon for Nimbostratus rankNimbostratus
Jan 29, 2014

Effect of changing timeouts to 3 hours

All, can anyone provide information as to what the effects of changing protocol timeouts and persistence timeouts to a value of three hours may have in a BIGIP LTM 11.3 environment. Looking for any t...
Russell_Moore_8's avatar
Russell_Moore_8
Icon for Nimbostratus rankNimbostratus
Jan 29, 2014

Avoid using excess timeout values if possible. Often longer values are requested because users complain of being on a system idle for a long time and the LTM drops their connections because they were idle. If this is the case then it is better to have the client send some sort of keep-alive regularly so that the entries do not expire.

 

Two examples I would point to is SSH can have keep-alives enabled and HTTP can have a very small java script embedded that does a request for a very small object every so often.

 

Changing the timeout values significantly will mean you are always using those resources where fixing the problem with some sort of keep alive fixes only for those that have long idle sessions and keeps your resources allocated to current clients.