topic Re: CSS to ACE - rserver range loadbalance issue? in Application Networking

CSS to ACE - rserver range loadbalance issue?

ctopaloglu — Wed, 27 Aug 2008 11:54:42 GMT

We are replacing CSS with ACE.

--------------

CSS_Config

--------------

service apps1

ip address 10.4.11.1 range 3

keepalive type http

keepalive frequency 15

active

service apps2

ip address 10.4.12.1 range 3

keepalive type http

keepalive frequency 15

active

owner webapps

content webapps-rule

add service apps1

add service apps2

advanced-balance sticky-srcip

sticky-inact-timeout 480

vip address 10.4.10.1 range 3

balance leastconn

sticky-serverdown-failover redirect

--------------

ACE_Config

--------------

rserver host APPS1-01

inservice

ip address 10.4.11.1

rserver host APPS1-02

inservice

ip address 10.4.11.2

rserver host APPS1-03

inservice

ip address 10.4.11.3

rserver host APPS2-01

inservice

ip address 10.4.12.1

rserver host APPS2-02

inservice

ip address 10.4.12.2

rserver host APPS2-03

inservice

ip address 10.4.12.3

serverfarm host APPS

rserver APPS1-01

inservice

rserver APPS1-02

inservice

rserver APPS1-03

inservice

rserver APPS2-01

inservice

rserver APPS2-02

inservice

rserver APPS2-03

inservice

class-map match-any WEBAPPS_CLASS

match virtual-address 10.4.10.1 tcp any

match virtual-address 10.4.10.2 tcp any

match virtual-address 10.4.10.3 tcp any

Note: The real range is 99 not 3.

They have two rservers (apps1 and apps2). Each one has 3 virtual address.

Here is the problem...

Client wants to go 10.4.10.(2) and CSS loadbalance two real servers according to last subnet bit x.x.x.(2) Then it goes 10.4.11.(2) or 10.4.12.(2)

In CSS I think this is the default prediction method when range is used. But I can't find it in ACE 1.1(a). Is there any way to guarantee that the ACE loadbalance like CSS did? I realy need your advice. Thanks in advance.

Re: CSS to ACE - rserver range loadbalance issue?

ciscocsoc — Wed, 27 Aug 2008 12:43:38 GMT

Hi,

If I've understood your requirement and you really need to carry the CSS implementation across then I think you need to create multiple rservers into multiple serverfarms. Then a class-map for each VIP with an associated loadbalance policy-map: Something like -

rserver host x01

ip address 10.4.11.1

inservice

rserver host x02

ip address 10.4.11.2

inservice

rserver host x03

ip address 10.4.11.3

inservice

rserver host y01

ip address 10.4.12.1

inservice

rserver host y02

ip address 10.4.12.2

inservice

rserver host y03

ip address 10.4.12.3

inservice

serverfarm host FARM-01

rserver x01

inservice

rserver y01

inservice

serverfarm host FARM-02

rserver x02

inservice

rserver y02

inservice

serverfarm host FARM-03

rserver x03

inservice

rserver y03

inservice

class-map match-any L4VIPCLASS-01

2 match virtual-address 10.4.10.1 tcp any

class-map match-any L4VIPCLASS-02

2 match virtual-address 10.4.10.2 tcp any

class-map match-any L4VIPCLASS-03

2 match virtual-address 10.4.10.3 tcp any

policy-map type loadbalance first-match LB-POLICY-01

class class-default

serverfarm FARM-01

policy-map type loadbalance first-match LB-POLICY-02

class class-default

serverfarm FARM-02

policy-map type loadbalance first-match LB-POLICY-03

class class-default

serverfarm FARM-03

policy-map multi-match L4POLICY

class L4VIPCLASS-01

loadbalance vip inservice

loadbalance policy LB-POLICY-01

class L4VIPCLASS-02

loadbalance vip inservice

loadbalance policy LB-POLICY-02

class L4VIPCLASS-03

loadbalance vip inservice

loadbalance policy LB-POLICY-03

There might be a slicker way of achieving what you want and I'm sure one of the ACE gurus will point it out if it exists.

Did you use the conversion tool on the ACE? It should have highlighted any parts of the config it couldn't cope with.

HTH

Cathy

Re: CSS to ACE - rserver range loadbalance issue?

ctopaloglu — Thu, 28 Aug 2008 17:13:34 GMT

First of all, Thanks for your quick reply.

I use CSStoACE conversion tool. And it says...

The range option of the ip address subcommand under service configuration is not converted. Only the first ip address would be converted. For each of the remaining ip addresses in the range, rservers will have to be created manually and such rservers will have to be added to the appropriate serverfarm also manually.

I aggree it can be done manually. But the range is 99 not 3. If CSS can do it without any additional configuration and if ACE is newer and better than CSS it should be a better way do it.