Hi everyone,
I have a issue with a sticky method in ACE loadbalancer.
The ACE receives incoming connections which it sees as a single IP (proxy) and we have the following configuration:
rserver host BCHAPP140
ip address 10.20.36.30
inservice
serverfarm host FWORK_8011
failaction purge
predictor leastconns
probe PruebaHTTP
rserver BCHAPP140 8011
inservice
rserver BCHAPP140 8211
inservice
rserver BCHAPP140 8311
inservice
rserver BCHAPP141 8011
inservice
rserver BCHAPP141 8211
inservice
rserver BCHAPP141 8311
inservice
sticky ip-netmask 255.255.255.255 address source FWORK_8011_stickyIP
replicate sticky
serverfarm FWORK_8011
class-map match-all VIP_FWORK_8011
description FRAMEWORK_8011
2 match virtual-address 152.139.82.119 tcp eq 8011
policy-map type loadbalance first-match LB_POLICY_8011
class class-default
sticky-serverfarm FWORK_8011_stickyIP
policy-map multi-match POLICY-FWORK
class VIP_FWORK_8011
loadbalance vip inservice
loadbalance policy LB_POLICY_8011
loadbalance vip icmp-reply active
......
The problem we're seeing is that when it generate a lot of incoming connections, the balancer does not perform the load balance correctly, but sends most of the connections to a single server, for example: rserver BCHAPP140 8211.
We believe that the problem may be in the Source Sticky IP settings ... and we are considering making the change to sticky http-cookie.
I hope you can help me and explain how I could generate a correct configuration.
Thanks.
