service type of redirect.

rich.polyak · ‎09-21-2006

Hi, I'm being requested to setup the following with service type of redirect.

!**************************** DQL

dql xxxxxxx

domain x.x.x.x

!*************************** OWNER

content xxxxxxxx

protocol tcp

vip address x.x.x.x

balance weightedrr

vip-ping-response local-remote

advanced-balance sticky-srcip

redirect "please wait while you are redirected to xxxxxxxx"

port 80

url "/*" dql xxxxxxx

add service xxxxxxx1

add service xxxxxxx2 weight 5

active

!************************** SERVICE

service xxxxxxx1

ip address x.x.x.x

keepalive type http

keepalive port 50100

keepalive uri "/index.html"

port 50100

type redirect

redirect-string "x.x.x.x:50100/irj"

active

service xxxxxxx2

ip address x.x.x.x

keepalive type http

keepalive port 50100

keepalive uri "/index.html"

port 50100

redirect-string "x.x.x.x:50100/irj"

type redirect

active

My question is this,

Since all services are of type redirect,

1. advanced balance never comes into play?

2. Service ip address is only required only for the keepalive?

3. The clients will never have the full benifit of the CSS since they are being redirected? I.E. failover of services?

Is there any other benifits that they will not receive because of the service type of redirect?

Thx.

Gilles Dufour · ‎09-22-2006

1. advanced-balance does not care about the service type. So it should work.

2. yes, it will be used only for keepalive.

3. there will still be loadbalancing and upon server failover, the client should come back to the vip address and it will be redirected to the next available server. So, there is still a benefit when using such a solution.

Gilles.

rich.polyak · ‎09-22-2006

Gilles,

Thanks for the response.

On # 2. if the keepalive fails then nothing should be sent to this service correct?

# 3. I just need to let the Web Admin know that the client will need to go back to the vip address for after they get redirected they are off of the CSS.