Redundant CSS with ASR - stickiness replication?

Unanswered Question
Oct 1st, 2008
User Badges:


two 11501-SSL configured with ASR,

SSL termination on CSS,

Inter-switch link is up

Two servers on backend, advance-sticky-srcip

Should stickiness info be passed from Pri to standby CSS?

As a sample:

Right now user is logged to server1 via pri CSS,

after I failed over to sec, user may go to server1 or Server2, can't predict.

Looks like sec CSS makes its own decision and sticks with it.

Red-index on services and backend rules, red-vips etc are in place,

as per documentation

Thank you


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Gilles Dufour Thu, 10/02/2008 - 00:48
User Badges:
  • Cisco Employee,


I don't think we do sticky replication on the CSS.

You could try arrowpoint-cookies as a sticky method.

Since it does not require any sticky table, it may work.


a.gesse Fri, 10/03/2008 - 12:28
User Badges:


flow information is passed over from Pri to sec CSS, right?

And flow info should be linked to specific rule/service with appropriate red-indexes?

It actually includes "stickiness info", implicitly.

After failover this dormant flow should become active.

Is this logic above right?

For some reason Sec CSS ignores existing dormant flow and creates new one to another server.

Anyway, thanks for your response



This Discussion