|
Joseph Mack wrote:
On Fri, 20 Apr 2001, Paul Baker wrote:
This error is usually a routing error on the real-server.
Make sure the route to the client from the real-server
doesn't go through the director.
Here is the output of ifconfig and route from one of the real-servers
when it was not work with VS-Tun
eth0 Link encap:Ethernet HWaddr 00:02:B3:3D:1F:FA
inet addr:63.216.62.179 Bcast:63.216.62.191
Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5709 errors:0 dropped:0 overruns:0 frame:0
TX packets:4566 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:24 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
tunl0 Link encap:IPIP Tunnel HWaddr
inet addr:63.216.62.170 Mask:255.255.255.255
UP RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
63.216.62.170 * 255.255.255.255 UH 0 0 0
tunl0
63.216.62.160 * 255.255.255.224 U 0 0 0 eth0
default 63.216.62.161 0.0.0.0 UG 0 0 0 eth0
Here is the output from ifconfig and route on one of the real-servers
with VS-DR working:
eth0 Link encap:Ethernet HWaddr 00:02:B3:3D:1F:FA
inet addr:63.216.62.179 Bcast:63.216.62.191
Mask:255.255.255.224
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2217 errors:0 dropped:0 overruns:0 frame:0
TX packets:1295 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:24 Base address:0x4000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
lo:0 Link encap:Local Loopback
inet addr:63.216.62.170 Mask:255.255.255.255
UP LOOPBACK RUNNING MTU:3924 Metric:1
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
63.216.62.170 * 255.255.255.255 UH 0 0 0 lo
63.216.62.160 * 255.255.255.224 U 0 0 0 eth0
default 63.216.62.161 0.0.0.0 UG 0 0 0 eth0
Doesn't seem to be that much different between the VS-Tun and VS-DR
output to me.
Is there any other device with the VIP on the real-server?
Nope.
You can try the configure script if you want an alternative
view on the matter. You'll at least see how a working
setup is set up.
When I was trying to tackle all this 2 weeks ago, I was using the
configure script, and with that method it never even made it to get the
real-servers listed with ipvsadm. unfortuneately the configure script
seems to be very redhat-oriented.
if you haven't changed the routing then the routing in the VS-Tun
case isn't the problem.
Not that I am at all aware of. The commands I pasted in my last email
are exactly the ones I executed and only those.
--
=======================================================================
Paul J. Baker Internet Systems Technician
pbaker@xxxxxxxxxxxxxxx Where2GetIt.com
phone 847-498-0111x234
fax 847-480-7422
=======================================================================
| 