03-18-2004 09:46 AM
Does this config seem kosher? Using arrowpoint-cookie for
a vip with url http://web1, but we also want to redirect anything
to http://web1/static/ to separate content which is also using
arrowpoint-cookie, load balancing to two other services. It seems like
the css is doing the right thing, issuing an arrowpoint cookie for
http://web1, then it will modify the cookie when I hit http://web1/static/
but haven't seen anything like this in the docs so I'm wondering if
I'm asking for trouble.
We are using a css 11151 with version 5.00 Build 105.
Here is the config:
content web1-80
vip address 10.0.1.10
balance weightedrr
add service server1-80 weight 4
add service server2-80 weight 4
add service server3-80 weight 2
add service server4-80 weight 4
add service server5-80 weight 4
advanced-balance arrowpoint-cookie
protocol tcp
port 80
url "/*"
active
content web1-static-80
vip address 10.0.1.10
add service server4-7084
add service server5-7085
advanced-balance arrowpoint-cookie
protocol tcp
port 80
url "/static/*"
active
service server1-80
ip address 192.168.1.1
port 80
keepalive type tcp
keepalive port 80
keepalive frequency 60
string 111p801111
act
service server2-80
ip address 192.168.1.2
port 80
keepalive type tcp
keepalive port 80
keepalive frequency 60
string 222p802222
act
service server3-80
ip address 192.168.1.3
port 80
keepalive type tcp
keepalive port 80
keepalive frequency 60
string 333p803333
act
service server4-80
ip address 192.168.1.4
port 80
keepalive type tcp
keepalive port 80
keepalive frequency 60
string 444p804444
act
service server5-80
ip address 192.168.1.5
port 80
keepalive type tcp
keepalive port 80
keepalive frequency 60
string 555p805555
act
service server4-7084
ip address 192.168.1.4
port 7084
keepalive type tcp
keepalive port 7084
keepalive frequency 60
string 444p7084444
act
service server5-7085
ip address 192.168.1.5
port 7085
keepalive type tcp
keepalive port 7085
keepalive frequency 60
string 555p7085555
act
Thanks
-Dan
03-22-2004 01:58 PM
Dan,
That should work. The users that go to /static/* then go back to the main rule will present the static page cookie and the CSS will re-issue the cookie.
You may want to use the "arrowpoint-cookie path" command to set the path to "/static/" for the static cookie.
Also, in version 7.30 there is a new command called "arrowpoint-cookie name". Using that, you can have each content rule have a different cookie name. This would be preferable, looking at what you are doing.
Hope this helps
-Steve
03-28-2004 01:12 PM
Dan, I believe that you should add an 'arrowpoint-cookie path' for the web1-static-80 content rule. This will allow a different cookie to be presented if when a user hits this rule. The browser should then present the proper cookie a users attempts to connect with a URL that includes /static/. Here's a quick link to the documentation for this feature: http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/css_500/advcfggd/sticky.htm#xtocid27
Hope this helps.
-Chip
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide