LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: routing problem on RS in lvs_nat

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx, malalon@xxxxxxxxxxxxxx
Subject: Re: routing problem on RS in lvs_nat
From: Joseph Mack <mack.joseph@xxxxxxx>
Date: Thu, 30 Aug 2001 07:50:48 -0400
malalon@xxxxxxxxxxxxxx wrote:


> When I run rc.lvs_nat on RS it says: "the path to the director's default gw 
> does not go through the director", but when I run traceroute everything looks 
> ok (see below).
> 

please adjust your mailer. 
You don't have carriage returns in your paragraphs and each paragraph is one 
line and goes off the right side of my screen.

> What is the problem, can anyone help me?

sometime, please upgrade to configure-v0.9. 
It won't change your problem here, but it will make 
it easier for me to diagnose problems.


> 3. a route to the director is not good enough, it won't work, the director 
> must be the default gw.
> 4. the realservers must not have any other routes to the client.
> (Some routing problems are fixed by rerunning the script.)
> 
> To help debug the problem, here's the output of netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
> 192.168.1.2     0.0.0.0         255.255.255.255 UH        0 0          0 eth0
> 192.168.1.0     0.0.0.0         255.255.255.128 U         0 0          0 eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U         0 0          0 lo
> 0.0.0.0         192.168.1.1     0.0.0.0         UG        0 0          0 eth0
> 
> *****************************************************
> 
> Traceroute -n -s 192.168.1.2 194.29.167.126
> 
>  1  192.168.1.1  0.646 ms  0.475 ms  0.465 ms
>  2  194.29.167.126  2.511 ms  1.690 ms  1.670 ms

the configure script tests if packets to the director_gw from 
the realserver go through the director. It does this using
traceroute and grep to look for 2 hops. If there are other routes
to the director_gw then the script will see 1 hop. The output
of traceroute here shows 2 hops, so I expect that the script has
failed in parsing your traceroute output. It is likely that your
LVS is setup correctly. I would run the rc.lvs_nat file
on the director and then the realservers and just try your LVS to
see if it works.

I would suspect my script at this stage.

Can you let me know what happens? And on the machine that 
produces this failure message, can you send me 
(off-line to jmack@xxxxxxxx) the output from

$sh -x rc.lvs_nat > rc.lvs_nat.out 2>&1

Thanks
Joe



-- 
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center, 
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA


<Prev in Thread] Current Thread [Next in Thread>