|
On Fri, 22 Sep 2000, Jeremy Hansen wrote:
>
> Ok. Here's a layout of basically how it setup
>
>
> internet
> |
> 64.204.99.1 (network providers router)
> |
> switch
> |
> real server 1 lvs machine real server 2
> RIP (10.100.50.247) RIP (64.204.99.249) RIP (10.100.50.246)
> lo:0 (64.204.99.240) VIP (64.204.99.240) lo:0 (64.204.99.240)
> default gw 64.204.99.1 default gw 64.204.99.1
> static arp entry static arp entry
> for the router, for the router,
> 64.204.99.1 64.204.99.1
>
> real server 3 (which is not to be load balanced)
> RIP (10.100.50.245)
>
> The problem is real server 1,2,3 cannot get to the internet which is a
> requirement. Basically because these machines don't really have a real ip
> address at all, so for them to get out, they need to be NAT's at some
> point.
With the VIP on lo:0 I assume you are now running VS-DR. If so, the
director doesn't have an IP on the 10.x.x.x network and can't talk
to the real-servers. (Or else you're tunning VS-Tun and the VIP should
be in tunl0 on each real-server).
real-server1 has a real IP of 64.204.99.240. It's as real an IP as you can
get. The router with an IP in the 64.204.99.x network will happily accept
packets from it. The only thing different about the VIP as far as being an
IP is that it won't reply to arp requests. (There is the extra wrinkle
that several machines in the LVS carry the VIP.)
You can get a VS-DR or VS-Tun LVS to work with an internal
betwork of 10.x.x.x and an external network of 64.204.99.x
I assume the problem is the your LVS isn't working. Can you set up for
telnet as your service and see what happens. If it doesn't work, try my
script. If that doesn't work, send me any messages from the startup script
and the output of ipvsadm, ifconfig -a and netstat -rn for all the machines.
Joe
--
Joseph Mack mack@xxxxxxxxxxx
|
