Re: LVS-DR, Cisco switch, and ARPtables

[Graham Purcocks <grahamp@xxxxxxxxxxxxx>]

Hmmm. I don't think this is a noarp problem.

Basically, there is a howto on checking the hidden arp problem.

You clear your arp table of the VIP address.

arp -d 172.27.21.210

Then ping 172.27.21.210

then check your arp table again to see which MAC address you have. If 
the MAC address is of the director then I don't think this is your problem.
noarpctl list on the RIP

should go up by 1 if it blocked the arp request.

Thats getting near the end of my knowledge.

Graham


Brett Simpson wrote:
> On Friday 03 December 2004 11:15, Graham Purcocks wrote:
>
> > So why do you think its not working. 
>
> I'm not sure what's wrong. I'm going to setup a Laptop with Linux on the same 
> network and have it act as the director to 172.27.21.212 only (no bonding on 
> the realserver or director) and see what happens.
>
> > Are you getting this arp as 
> > 172.27.21.210?  
>
> How can I tell? Packet trace?
>
>
> > If you clear the arp table on the test machine and ping 
> > the VIP does the count go up on the noarpctl list output. i.e. noarp has
> > acknowledged it has blocked the arp request.
>
> My client only has one arp entry, the default gateway, and it's 172.27.121.1. 
> It's on another subnet with an IP of 172.27.21.53.  When I try to connect to 
> port 80 it just times out. The count doesn't change.
> Thanks,
> Brett
> _______________________________________________
> 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