fallback for sticky cookie on the ACE

Unanswered Question
May 22nd, 2009
User Badges:

Is possible to configure the following. The client does'nt send cookie in the request, use source ip adress sticky for him. When the client send cookie in the request, use cookie hash for sticky this client. For example when I will configure:

sticky http-cookie test cookie serverfarm SFARM1

sticky ip-netmask address source src

serverfarm SFARM1

is possible to prefer cookie before source sticky??

or I have to use predictor cookie with source ip sticky??

Thank you


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Gilles Dufour Fri, 05/22/2009 - 04:13
User Badges:
  • Cisco Employee,

Not possible.

The reason is that the first client requuest usually does not contain a cookie.

But the server will assign one.

To learn the cookie from the server, you need the connection to match the sticky cookie rule.

So even if the request has no cookie, you want to do cookie sticky so that we can learn the response from the server.

If your servers use static cookie, you could configure static entries and therefore the learning process is not required.

In this case, you could do a class-map to match the cookie name and any value.

If present, do cookie sticky.

If not, do src ip sticky.

This can be done with the following

class-map type http loadbalance match-all Cookie

2 match http cookie src cookie-value ".*"

policy-map type loadbalance http first SLB

class Cookie

sticky-serverfarm CookieSticky

class class-default

sticky-serverfarm IPSticky

Haven't tested however.

But this is how I would do it.



This Discussion