Re: vmac support

On Wed, Feb 26, 2014 at 08:39:29AM +0100, Sander Klein wrote:
> On 25.02.2014 22:43, Lennart Sorensen wrote:
> >On Tue, Feb 25, 2014 at 09:15:37PM +0100, Sander Klein wrote:
> >>Is there or can anyone provide me with a manual how to use the vmac
> >>feature?
> >>
> >>I've been trying to get it working and I somehow can't get it working.
> >>It looks like the mac address of the vrrp interface gets spilled
> >>on the
> >>network from both vrrp hosts at the same time.
> >>
> >>I've used NOTE_vrrp_vmax.txt to create my setup but I've got a feeling
> >>it's missing something.
> >
> >Which version are you using?
> 
> I'm using keepalived 1.2.12 on kernel 3.2.54 with Debian Wheezy.
> 
> The sysctl settings are:
> 
> net.ipv4.conf.all.arp_filter = 0
> net.ipv4.conf.default.arp_filter = 0
> net.ipv4.conf.all.arp_ignore = 1
> net.ipv4.conf.default.arp_ignore = 1
> net.ipv4.conf.all.arp_announce = 2
> net.ipv4.conf.default.arp_announce = 2
> 
> And I've got a script which sets some settting on the vrrp interface
> when going to master like:
> 
> sysctl -w net.ipv4.conf.vrrp/18.arp_filter=0
> sysctl -w net.ipv4.conf.vrrp/18.accept_local=1
> 
> The keepalived config I use is quite simple:
> 
> vrrp_instance VI_1 {
> 	state MASTER
> 	interface eth0
> 	virtual_router_id 18
> 	priority 100
> 	advert_int 1
> 	use_vmac
> 	vmac_xmit_base
> 	authentication {
> 		auth_type PASS
> 		auth_pass somepass
> 	}
> 	virtual_ipaddress {
> 		x.x.x.x
> 	}
> 	track_interface {
> 		eth0
> 	}

Why are you tracking the interface you are running on?  Tracking is for
monitoring other interfaces in addition to the one you are running on
as far as I remember.  Shouldn't cause any problem as far as I can
tell though.

> 	track_script {
> 		chk_somecheck
> 	}
> 	notify_master "/etc/keepalived/vmac.sh"
> }
> 
> Everything starts up fine. I see the vrrp interface created on both
> the loadbalancers. But it seems like connections go to both
> loadbalancers sometimes.
> 
> If I ping the VIP and the second loadbalancer comes online then I
> receive a couple of (DUP!)'s from the ping utility.

Hmm, the second one should come up and check if there is already a master
running as far as I am aware.  It should not start out listening on the
VIP unless you someone have the configuration out of sync between the
two systems.

-- 
Len Sorensen



------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk