First-time LVS user, having problem with LVS-DR

[Joseph Mack NA3T]

On Fri, 3 Nov 2006, David Fix wrote:

> Hey guys...  :)  As the subject says, I'm a first-time LVS user, and I'm
> having problems with DR...
>
> Here's my network setup:
>
>                        ________
>                       |        |
>                       | client | (Me, at home)
>                       |________| IP = x.99.97.254
>                           |
>                        ________
>                       |        |
>                       |Internet|
>                       |________|
>                           |
>                    VIP = x.2.119.227 (eth0)
>                        ________
>                       |        |
>                       |Director|
>                       |________|
>                    DIP = 192.168.0.1 (eth 1)
>                           |
>                           |
>          --------------------------------------
>          |                                    |
>          |                                    |
> RIP = x.2.119.9 (eth0)               RIP = x.2.119.15

you don't need the x.2.119.y addresses here. I assume you 
have these only for testing purposes. They should go in the 
production version.

> RIP = 192.168.0.2 (eth1)             RIP = 192.168.0.3 (eth1)
> VIP = x.2.119.227 (lo:0)             VIP = x.2.119.227 (lo:0)
>     ______________                       ______________
>    |              |                     |              |
>    | realserver 1 |                     | realserver 2 |
>    |______________|                     |______________|
>
>
> I've only tried to set it up with realserver1 to start...
>
> Alright...  I've put in the patches for hiding the arps on realservers 2 and
> 3.
> They don't arp on interface lo:
> realserver1# cat /proc/sys/net/ipv4/conf/all/hidden
> 1
> realserver1# cat /proc/sys/net/ipv4/conf/lo/hidden
> 1

arp_ignore is the preferred method for new setups, but 
hiding will work fine.

> I've added the VIP to the director:
> director# ipvsadm -A -t x.2.119.227:80 -s rr
>
> Then to redirect it to realserver1:
> director# ipvsadm -a -t x.2.119.227:80 -r 192.168.0.2 -g
>
> Verified:
> director# ipvsadm
> IP Virtual Server version 1.2.1 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
>  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
> TCP  x.2.119.227:http rr
>  -> 192.168.0.2:http             Route   1      0          0
>
> The httpd is up and running on realserver1, and listening to the VIP.
> The routing is set up on realserver1:
> realserver1# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> x.2.119.227     *               255.255.255.255 UH    0      0        0 lo
> x.2.119.0       *               255.255.255.0   U     0      0        0 eth0
> 192.168.0.0     *               255.255.255.0   U     0      0        0 eth1
> loopback        *               255.0.0.0       U     0      0        0 lo
> default         x.2.119.1       0.0.0.0         UG    0      0        0 eth0

hmm. I see your router has a public IP on the inside facing 
your LVS, which is running on 192.168.x.x. All the inside 
addresses (ie all except the VIP) should not be routable to 
the outside world. (This isn't causing your problem.)

> I've done a tcpdump that shows that packets are being received on both
> machines:

you shouldn't need to tcpdump yet.

> I've verified that I can connect to the realserver's "x.2.119.9" httpd from
> my client, and there's no problem there, however, if I try to connect
> through the LVS, nothing!

what is nothing? these are something

o the telnet client hangs

o the telnet client gives error messages.

Have you gone through the checklist in

http://www.austintek.com/LVS/LVS-HOWTO/mini-HOWTO/LVS-mini-HOWTO.html#problems

Joe

-- 
Joseph Mack NA3T EME(B,D), FM05lw North Carolina
jmack (at) wm7d (dot) net - azimuthal equidistant map
generator at http://www.wm7d.net/azproj.shtml
Homepage http://www.austintek.com/ It's GNU/Linux!