cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
956
Views
0
Helpful
1
Replies

ACE 4710 load balancing HTTP cookie pattern not working

sololuke2013
Level 1
Level 1

Hi,

I try to configure ACE 4710 LB A5(2.1) LB to do following:

1. client send a http request for login to WEB srv

2.  server response and send a cookie Set-Cookie with following pattern  JSESSIONID=C333C37FCF083D210A639ABB8BB9DB21.S01 (33 random body 3 char  string server ID)

3. Client send authorize http request to other server with the cookie in  URI (traffic not go via LB)

4. Authorize server send to WEB srv a request containing that cookie and wait for answer.

Client ----> ACE LB VIP ---> WEB server

Client -----> Authorize SRV ----> ACE LB VIP ----> WEB server

There are 4 WEB srv which have sessions ending in . S01 S02 S03 S04

I  want that all login request to be round robin balanced, and authorize  request to be forwarded to right WEB srv based on cookie termination S01  or .....

Configuration:

1. server farm probing

probe http http_8080

   port 8080

   interval 7

   passdetect interval 3

   passdetect count 4

   receive 2

   expect status 200 200

   open 3

2. cookie stickiness settings

sticky http-cookie JSESSIONID web-pro-srv-8080-stk

   cookie offset 33 length 3

   serverfarm WEB-pro-8080

   timeout 5

   replicate sticky

3. Traffic policy

class-map match-all WEB-pro-8080

   2 match virtual-address 192.168.123.100 tcp eq 8080

policy-map type loadbalance first-match WEB-pro-8080

   class class-default

     sticky-serverfarm web-pro-srv-8080-stk

policy-map multi-match EXTERNAL

  class WEB-pro-8080

     loadbalance vip inservice

     loadbalance policy WEB-pro-8080

     loadbalance vip icmp-reply active primary-inservice

Issue: Some sessions obtained at login are forwarded by LB      to wrong WEB srv

Can you please help me?

duplicate on

https://supportforums.cisco.com/message/4078336#4078336

1 Reply 1

rajsures
Cisco Employee
Cisco Employee

Hi Luke,

I am not sure why "cookie offset 33 length 3" is required here. Again the offset value 33 and length value 3 is actually configured in bytes and not exactly based on number of characters in the cookie value. What happens if you remove the

"cookie offset 33 length 3" from the sticky configuration ? can you try removing this command and check if it works ?

Thanks,

Rajesh.

Review Cisco Networking for a $25 gift card