09-13-2011 12:03 PM
Hello All,
I am using the option of Cookie-insert and I can see the HTTP session is working fine and clients are using the same server as expected.
When the client is switching the session to HTTPS the ACE is changing the session to a different server.
See below my basic configuration:
probe http Rebranding-Stage--http
port 5120
interval 10
passdetect interval 5
passdetect count 5
request method get url /keepalive1.htm
expect status 200 200
probe https Rebranding-Stage-https
port 5123
interval 10
passdetect interval 5
passdetect count 5
request method get url /keepalive1.htm
expect status 200 200
serverfarm host SF-Rebranding-Stage-https
probe Rebranding-Stage--https
rserver luw-wstg1 5123
inservice
rserver luw-wstg2 5123
inservice
serverfarm host SF-SF-Rebranding-Stage-http
probe Rebranding-Stage-http
rserver luw-wstg1 5120
inservice
rserver luw-wstg2 5120
inservice
sticky http-cookie MyCookie Rebranding-Stage-https
cookie insert
timeout 60
replicate sticky
serverfarm SF-Rebranding-Stage-https
sticky http-cookie MyCookie Rebranding-Stage-https
cookie insert
timeout 60
replicate sticky
serverfarm SF-Rebranding-Stage-https
class-map match-all CM-Rebranding-Stage-https
2 match virtual-address 10.4.0.2 tcp eq https
class-map match-all CM-Rebranding-Stage-http
2 match virtual-address 10.4.0.2 tcp eq http
policy-map type loadbalance first-match PM-Rebranding-Stage-https
class class-default
sticky-serverfarm Rebranding-Stage-https
policy-map type loadbalance first-match PM-Rebranding-Stage-http
class class-default
sticky-serverfarm Rebranding-Stage-https
policy-map multi-match Rebranding-Stage
class CM-Rebranding-Stage-https
loadbalance vip inservice
loadbalance policy PM-Rebranding-Stage-https
connection advanced-options Idle-Time
class CM-Rebranding-Stage-888casino-http
loadbalance vip inservice
loadbalance policy PM-Rebranding-Stage-888casino-http
connection advanced-options Idle-Time
Is it because I am using 2 different serverfarms , one for HTTP and one for HTTPS?
If I will use the same serverfarms for both protocols with differet internal port is this will keep it in the same server?
Any adea?
Thanks,
Reuven Elkabetz
09-13-2011 02:04 PM
Hi Reuven,
Yes, you are right the problem is because you are using two sticky groups. You can use just one sticky group with the same servefarm for HTTP and HTTPS.
However, the problem here is that you need to send the traffic to different ports depending if is HTTP or HTTPS and this is not possible with only one serverfarm.
Cesar R
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