Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

CSS and stickieness

Hi,

I have two following content rules pointing to the same vip and port, but one of them is sticky on a specific URL.

For some reason the sticky part does not work. The question is, can you have two such rules together?

content web1

add service service1

add service service2

url "/*"

protocol tcp

port 81

vip address 10.6.229.16

active

content web1_Reporting

add service service1

add service service2

protocol tcp

port 81

url "/web/reporting/*"

advanced-balance sticky-srcip

vip address 10.6.229.16

active

Thanks

8 REPLIES
New Member

Re: CSS and stickieness

I would think that the content rules are parsed in order. I'd try removing content web1 and adding it in again after web1_Reporting. that gives you an if/then/else type of logic in your configuration.

Cisco Employee

Re: CSS and stickieness

like a list of static routes, the order has nothing to do here. The CSS selects the best match (longest match).

Gilles.

Cisco Employee

Re: CSS and stickieness

could you send us a sniffer trace showing the problem ?

Stickyness will work only if the request start with /web/reporting/

Any other url will match the other content rule.

So, even if the first request is a match for rule web1_reporting, if the next request inside the same tcp connection does not match that rule, the css will reloadbalance the connection.

Gilles.

New Member

Re: CSS and stickieness

Gilles, you could be right on the money.

I will check to see if this could be the issue.

Alec

New Member

Re: CSS and stickieness

Gilles,

You were right. There was a call outside "/web/reporting/*" thus load balancing to a different web server.

Is there anyway to combine two urls into one sticky session for example

url1: "/web/reporting1/*"

url2: "/web/reporting2/*"

Thanks again,

Alec

New Member

Re: CSS and stickieness

New Member

Re: CSS and stickieness

Brian,

URQL works if you have specific file names. I actually need to have a "*" (wildcard) and URQL does not support that.

Thanks,

Alec

Cisco Employee

Re: CSS and stickieness

you could do

url "/web/reporting*"

or create 2 content rules with the same services and use arrowpoint-cookie instead of sticky source-ip.

Gilles.

148
Views
0
Helpful
8
Replies
CreatePlease login to create content