|
> -----Original Message-----
> From: Sam Mayes [mailto:sam.mayes@xxxxxxxxx]
> Sent: Friday, September 07, 2001 5:19 AM
> To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE: 2.4.5 dr problems
>
>
> That's what is so strange, it has been running fine for a
> month. Nothing
> changed I rebooted is all. This teach me..
>
> Sam
>
>
>
> Hello,
>
> On Thu, 6 Sep 2001, Sam Mayes wrote:
>
> > Ok, this is strange
> >
> > Ive had dr running for a month. No problems at all.
>
> What was the running LVS version and on what was kernel before
> switching to this:
>
> > I rebooted my 3 machines today rh 7.1 kernel 2.4.5
> ...
> > My director has 2 nics, a public nic, and a second private net nic
> >
> > My two realserver have private nics, and public nics with
> the VIP set
> to
> > lo:10, After rebooting (mind you nothing changed AT ALL) software
> wise.
> > Some tripped over our power cables :), when I do a ipvsadm -l -c
> nothing
> > shows up
> > And all traffic is going to just one of the real server
> (web). Nothing
> > is getting to the second realserver. Is this the arp problem?
This definately sounds like the arp problem to me. I had something
similar happen when I replaced my regular server with a cluster. Even
after I hid the interface on my old server, the router continued to send
requests to that server, I think because of its cache.
It sounds to me like one of your real servers (the one getting the
traffic) managed to broadcast an ARP packet before the hidden stuff came
into effect.
Remember that you need to bring the interface up on some IP (NOT the
VIP), then hide it, then add the alias for the VIP.
Something else that helped me is the fake command. Even after I fixed
my real servers to hide the VIP properly, the router kept sending
packets to them because of its ARP cache. I used fake to send
gratuitous ARP packets to inform the router of the new location of the
VIP, and then everything started working again.
I think that the best strategy for making sure you don't get bit by this
again is to always boot the director first, and only bring the real
servers up once you are sure that the router is sending VIP packets to
the director. That way, even if something is wrong with your hidden
configuration, the router will get the right MAC address.
> Shouldn't
> > be, /proc settings are there.. this is drivinf me nuts.... help
> please
> > :)
>
> I'm not sure whether these settings are there by default.
> Better you to check /proc/sys/net/ipv4/conf/all/hidden. 2.4 does not
> come with them. You have to read /docs/arp.html from the web site
> and to apply patch to the 2.4 real servers (if they are running 2.4).
>
> > Sam
>
>
> Regards
>
> --
> Julian Anastasov <ja@xxxxxx>
>
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
>
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
>
|
