Solved: ACE xml/soap loadbalancing

Heine Maring · ‎03-21-2013

Hi,

I am looking for a solution for loadbalang xml/soap requests on port tcp/7103 from 1 source to 5 realservers. Every soap request should be send to the next realserver (predictor roundrobin). Can I solve this with the persistence-rebalance parameter?

Below the current configuration, which sends all traffic from 1 source to 1 realserver.

serverfarm host SOAP

rserver SMP-A-1

inservice

rserver SMP-A-2

inservice

rserver SMP-A-3

inservice

rserver SMP-B-1

inservice

rserver SMP-B-2

inservice

class-map match-any SOAP

2 match virtual-address 10.94.201.248 tcp eq 7103

policy-map type loadbalance first-match SOAP

class class-default

serverfarm SOAP

policy-map multi-match LB-POLICY-ALL

class LB-NP-ODSI

loadbalance vip inservice

loadbalance policy SOAP

loadbalance vip icmp-reply active

loadbalance vip advertise active

With regards,

Heine

Message was edited by: HEINE MARING Or should I use the predictor hash content option? Does anyone have experience with this?

Kanwaljeet Singh · ‎03-22-2013

Hi Heine,

Please use Persistence Rebalance Strict.

Below is the explanation:

When the first HTTP request comes in, the ACE will match the request to a layer-7 class-map

and load balance it to one of the servers within the serverfarm associated with that class-map.

The ACE will then also match all subsequent requests on the same TCP connection to a layer 7

class-map. Even if the subsequent request matches the same layer 7 class-map as the previous

request, then it will still be load balanced across the servers within the same serverfarm

according to the predictor, so it may go to a different server in the farm. If it matches a

different layer 7 class-map, then it will be load balanced to one of the servers within the

serverfarm of the newly matched layer-7 class-map. With the Strict feature, EVERY request will

be load balanced, whether it is using the same serverfarm as the previous request or not.

Regards,

Kanwal

View solution in original post

Jorge Bejarano · ‎03-22-2013

Heine,

I agree with the post which Kanwal uploaded, please take a look.

Jorge

View solution in original post

Jorge Bejarano · ‎03-22-2013

Heine,

I assume this is an ACE module, correct?

Probably, you may try the persistence rebalance feature.

In relation with hash content, with that you will configure the ACE to load balance client requests based on a hash value of the content string of the HTTP packet body, then at some point you may see that many users are sent to the same server.

Are you testing with a bunch of connections at the same time or a just few?

Based on what you have said, the round robin method would be the option which you may need.

Do all these servers have the same features, speed, capacity,etc?

Jorge

Heine Maring · ‎03-22-2013

Jorge,

Thanks for your reply. The problem solved itself, because it turns out to be some proprietary protocol, not XML. So the ACE cannot do anything with the http content.

I still have a question about the presistence-rebalance feature. I'm trying to understand this feature. In de configuration maunual it is stated:

If the subsequent request matches the same Layer 7 class map as the previous request, then the ACE sends the request to the same server as the previous request. This behavior produces less overhead and better performance.

But that's is just NOT what I want. I want every subsequent request going to a different server. Because my L7 class map will look like this.

class-map SOAP

match http content *

So every request matches the same L7 class map and hence goes to the same server. How can I configure that every subsequent request goes to a different server?

Heine

Kanwaljeet Singh · ‎03-22-2013