LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: Problem with LVS DR - 10065 Host is unreachable

To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Re: Problem with LVS DR - 10065 Host is unreachable
From: Malcolm Turnbull <Malcolm.Turnbull@xxxxxxxxxxxx>
Date: Fri, 20 Dec 2002 09:08:30 +0000
Rogers, Paul wrote:
Sébastien

The set up of the ip addresses on the realservers seems very strange. Can you confirm what the submask should be, based on the following.

All servers/clients on the network use a mask of 255.255.248.0 ie RIP1 = 10.80.18.44 with 255.255.248.0

Therefore should the mask for 10.80.18.203 on the lo:203 interface be 255.255.248.0 or 255.255.255.0?

How about the mask for 10.80.18.203 on the eth0:203 interface?

On the basis that there is no DNS, only the host files, what entries should be in the hosts tables on the director - VIP, DIP or both? Both RIP's?

How about the real servers?  VIP, DIP or both?

I tried pinging the real servers from another linux box and no reply, so it appears that the Windows clients can see them but not the linux boxes. I suspect this is because the windows clients use WINS to resolve the names while the linux boxes can't.


Um.. dont ping the DNS name, LVS doesn't care if that works although always use ipvsadm -Ln to stop a long lookup...
Ping the IPAddress that is what you are interested in..

ALL IPAddresses that you want to work i.e. VIP, DIP, RIPs should all have the same subnet. And they should all be pingable...

The fake VIP on the lo: we don't want to work so give it 255.255.255.255 as well as hidding it.. And it should NOT be pingable...

255.255.248.0 is a weird subnet to have on a private network (OK not that weird.. :-) ) are you sure you've got the broadcast address correct ?

For 192.168.1.10/255.255.255.0 the broadcast is 192.168.1.255
I'm not sure what your sould be can't remember how to work it out.







--


Regards,

Malcolm Turnbull.

Crocus.co.uk Ltd
01344 629629
http://www.crocus.co.uk/







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