atom feed20 messages in org.freebsd.freebsd-stablelagg(4) and failover
FromSent OnAttachments
Marian HettwerAug 12, 2008 3:36 am 
Eugene GrosbeinAug 12, 2008 3:55 am 
Marian HettwerAug 12, 2008 4:02 am 
Peter JeremyAug 12, 2008 4:24 am 
Pete FrenchAug 12, 2008 4:29 am 
Pete FrenchAug 12, 2008 4:39 am 
Marian HettwerAug 12, 2008 4:43 am 
Max LaierAug 12, 2008 4:59 am 
Peter JeremyAug 12, 2008 5:02 am 
Marian HettwerAug 12, 2008 5:13 am 
Marian HettwerAug 12, 2008 5:14 am 
Andrew ThompsonAug 12, 2008 8:46 am 
Andrew ThompsonAug 12, 2008 8:49 am 
Brian A. SekleckiDec 5, 2008 4:33 am 
Peter JeremyDec 6, 2008 1:02 pm 
Brian A. SekleckiDec 8, 2008 6:36 am 
Tom SamploniusDec 8, 2008 11:57 pm 
Peter JeremyDec 9, 2008 1:01 am 
Andrew SnowDec 9, 2008 1:21 am 
Brian A. SekleckiDec 9, 2008 7:34 am 
Subject:lagg(4) and failover
From:Marian Hettwer (mh@kernel32.de)
Date:Aug 12, 2008 3:36:52 am
List:org.freebsd.freebsd-stable

Hi Folks,

I'm using lagg(4) on some of our servers and I'm just wondering how the failover is implemented. The manpage isn't quite clear:

failover Sends and receives traffic only through the master port. If the master port becomes unavailable, the next active port is used. The first interface added is the master port; any interfaces added after that are used as failover devices.

What is meant by "becomes unavailable"? Is it just the physical link which needs to become unavailable to trigger a failover?

I do wonder, because there might be other faults where the link is still active, but the port is unusable. Think of a wrong vlan on the switch itself.

When using bonding under Linux (yeah, I know, the configuration sucks ;) ), I can configure the device to check for arp respones of it's default gateway. If arp to the default gw becomes unavailable, bonding fails over to the next interface and tries it luck over there. With that kind of configuration, I could cover a misconfigured switch port and still have failover.

Long Story short: How is failover in lagg(4) implemented?

Thanks for any hints :)

Or should I ask the OpenBSD boys, since lagg(4) seems to be a port of trunk(4)?? :)

best regards, Marian