F5 loadbalancer and session timeout in ASP application

Hello All,

I am having same issue, Load balancing is configured as Round robin, TCP connection profile time out is default which mean it is 1800 sec. I also have cookie based persistence. Don't have fallback persistence.

Do I need to configure fallback source address persistence ? Appreciate if anyone could brief me about source persistence.

Kindly consider my request to confirm this.

Regards Kalpak

Hi Kalpak, what exactly is your issue? If the sessions time out on the F5 before they do in the application you just need to create a custom TCP connection profile with the corresponding timeout values for TCP connections.

The source address persistence creates a persistence record for each client IP address. This means, when the same client IP is trying to access the same application within a short time range, he will get loadbalanced to the same node. Basically as a fallback for cookie persistence this would only affect browsers/applications who won't accept cookies, so this might not be related to your issue.

Cheers, Manuel

Hi Manuel,

I have published one application from F5 with URI redirection. On the same VIP we have configured cookie persistence. From last few days end users are facing session timeout . I mean user session getting timed out, they unable to complete certain steps which are mandatory for the application. For example you can consider Registration on website, users are able to put name, email id, mobile no but unable to put driving licence number at the portal, which is also one of the mandatory step for that specific application.

In my previous comment I was asking you, Do I need to configure fallback persistence as source address ?

Hope i have clarified your doubts.

In our F5, customized TCP profile already created, it is also properly applied to respective VIP and time out kept as default which mean timeout is 1800 sec. Am i right ?

Regards Kalpak

I don't think that a fallback persistence profile will help, as clients will probably already have a persistence record based on the cookie. In this case that change would have no effect.

I've just checked: the default idle timeout from the TCP profile is 300 seconds. If this service has a higher idle timeout, I can think about two solutions: x) get the application to send TCP keepalives regularly, or x) set the idle timeout value to, e.g. 1800 seconds (or higher) Probably the second solutions fits better for you :-)

Hope this helps, Manuel