LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: [lvs-users] Redhat init script problem with realservers

To: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [lvs-users] Redhat init script problem with realservers
From: "David Dyer-Bennet" <dd-b@xxxxxxxx>
Date: Fri, 5 Sep 2008 09:26:38 -0500 (CDT)
On Fri, September 5, 2008 03:29, Graeme Fowler wrote:
> On Thu, 2008-09-04 at 17:43 -0500, David Dyer-Bennet wrote:
>> After taking Xen out of the picture on the LVS node, and a failing
>> attempt
>> to use the "configure" script, setting up via piranha following the
>> Redhat
>> instructions sort of worked.  I get connections to one realserver or the
>> other, and other connections hang.
>
> Aha, you may be better off asking the Piranha-related questions on the
> relevant Redhat mailing list(s):

I don't think I do have Piranha-related questions; at least, the ipvsadm
output looks perfectly reasonable to me.  I think I've got a correct
configuration on the LVS node.  I only resorted to Piranha because nothing
suggested here was getting me any configuration at all.

>> None of the realservers can ping out.  Is this normal?  I'm using the
>> NAT
>> setup, partly because I thought it would allow the realservers to
>> connect
>> out (normal NAT setups that I'm familiar with support outward
>> connections!).  Once I get past basic testing, the applications on the
>> realservers will have to connect to databases and things which aren't of
>> course on the private network.  Also the realservers currently have an
>> interface directly connected to the outside network; shouldn't *that*
>> provide outside connectivity?  Or is it the source of my problems?  Do
>> the
>> realservers *have to* be totally isolated behind the LVS nodes?
>
> On the realservers, the default route *must* be via the notional
> "inside" interface of the director for LVS-NAT to work. If the default
> route goes a different way, then the traffic returning to the client is
> not un-NATted correctly and may result in a hung connection.

And I have the default route set that way.

But I had another route back into the main corporate LAN due to a
secondary interface being turned on, and that turns out to have been
causing the trouble.  Once I got that turned off, I get traffic
distributed across both realservers.  I examined this more carefully when
you pointed that out as a key requirement, so thank you!

-- 
David Dyer-Bennet, dd-b@xxxxxxxx; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info



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