atom feed20 messages in org.freebsd.freebsd-stableRe: lagg(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:Re: lagg(4) and failover
From:Eugene Grosbein (eug@kuzbass.ru)
Date:Aug 12, 2008 3:55:29 am
List:org.freebsd.freebsd-stable

On Tue, Aug 12, 2008 at 12:37:15PM +0200, Marian Hettwer wrote:

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?

Yes. It seems you need lacp protocol described later in the manual.