Re: Forwarding client request to VIP1 to VIP2 to RIPs

Hi,

Thanks a lot for your answer. It did work in the end -- there was a
typo in the ldirectord.cf file which I did not see and was causing a
wrong selection of the forwarding method.

I only tried with NAT (mixing forwarding methods does not seem to
work). Not to abuse your time and kindness, but I am interested in
another aspect:

Do you think I could configure both VIPs in the same box on different
interfaces (e.g. eth0:0 for VIP 2, eth0:1 for VIP1). I tried and it
did not work yet. It seems to be a problem that the VIP2 is seen as
local when playing the role of a "real server".

Here is the ldirectord.cf:
#VIP1:
virtual=192.168.141.160:8000
	real=192.168.141.150:8000 masq
	service=none
	scheduler=rr
	protocol=tcp
	#checktype=connect
#VIP2
virtual=192.168.141.150:8000
	real=192.168.141.131:8000 masq 2
	real=192.168.141.132:8000 masq 1
	service=none
	scheduler=wrr
	protocol=tcp
	checktype=connect

This is the result of ipvsadm:

IP Virtual Server version 1.2.0 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
TCP  192.168.141.150:8000 wrr
  -> 192.168.141.131:8000         Masq    2      0          0
  -> 192.168.141.132:8000         Masq    1      0          0
TCP  192.168.141.160:8000 rr
  -> 192.168.141.150:8000         Local   1      0          0

I tried changing the mac for VIP2 (150), but it does not work. It
seems that it is not possible to change the mac on the alias
interface. So, maybe you have a suggestion on this?

I apologize for these questions -- I did not find info on such
configurations on the web.

Thanks,
Roxana.

On 7/3/06, Horms <[email protected]> wrote:
> Roxana Diaconescu wrote:
> > Hello Everyone,
> >
> > I am trying to use two layers VIPs between the client and the real servers.
> >
> > Idea:
> >
> > VIP1's ipvsadm output:
> >
> > TCP VIP1:xxxx rr
> >  -> VIP2:xxx  gate/tunnel  1    0    0
> >
> > VIP2's ipvsadm output:
> >
> > TCP VIP2:xxx wrr
> >  -> RIP1:xxxx  gate         1     0    0
> >  -> RIP2:xxxx  gate         1     0    0
> >
> > If I use gate for VIP1's "real server" (VIP2), I get connection
> > refused. If I use tunnel, the connection just hangs. I used ultra
> > monkey to configure everything. Layer 2 VIP works fine, but not VIP1
> > on top of it.
> >
> > Has anyone tried something similar? Intuitively seems that is should work:
> >
> > Client connects to VIP1:xxxx
> > VIP1:xxxx gets forwarded to VIP2:xxxx
> > VIP2:xxxx gets forwarded to RIP1/2.
> >
> > However, it doesn't. Any thoughts?
>
> I suspect in the gate->gate case you are running into some kind of ARP problem.
> You should use something like tcpdump, and examine the arp tables on
> each machine to get a better picture of what is going on.
>
> I'm not sure about tunnel, though this may end up being the first valid
> use of it ever.
>
> --
> Horms
> H: http://www.vergenet.net/~horms/          W: http://www.valinux.co.jp/en/
>
>


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.