Persistent connections on Cisco ACE

[nlkarthik]

Hello Team,

Currently I have the below persistence settings for the vips and they are set as cookie based which would match where a session cookie is used.The cookie is set for "browser-expire" . So, this will allow the clients browser to expire the cookie when the session ends.

ASH

====

sticky http-cookie http-cookie-default 206.80.50.110:80

cookie insert browser-expire

serverfarm 206.80.50.110:80

sticky http-cookie http-cookie-default 206.80.50.110:443

cookie insert browser-expire

serverfarm 206.80.50.110:443

Please see the following snippet of information from Akamai:

============================================

"It has come to our attention that your Origin does not support pconns. This may possibly result in a significant overhead. Can you enable pconns on the load balancer and also back to the Origin with a idle timeout of 301 or 302 seconds? Our default is 300 secs of idling before terminating a pconn, so one sec more will avoid a race condition (assuming your server and NLB clock is sync'ed using NTP)"

I am assuming that this refers to TCP connections from the Akamai Edge Server to our end Load Balancer

I am presuming that they make a TCP connection(s) to the LB from the Akamai Edge Server and use it for multiple requests from clients and they would need ties connections to remain active for at least 301 seconds

Can this request be made possible. Pls assist. Thanks !!

regards,

Karthik

[Daniel Arrondo Ostiz]

Hi Karthik,

I believe you are confusing persistence with stickiness. What they mean by a persistent connection is one in which multiple HTTP requests are sent inside the same TCP flow, and ACE will always accept those.

I would suggest you to go back to Akamai and clarify what exactly is the issue, along with some more details on how they reached that conclussion, and then we can see if there is any way to avoid the problems.

Regards

Daniel