Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Sep 2009 13:23:51 -0700 (PDT)
From:      Barney Cordoba <barney_cordoba@yahoo.com>
To:        Peter Steele <psteele@maxiscale.com>
Cc:        net@freebsd.org
Subject:   Re: Can lagg0 failback be prevented?
Message-ID:  <491701.32471.qm@web63901.mail.re1.yahoo.com>
In-Reply-To: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3042DBE7@MBX03.exg5.exghost.com>

index | next in thread | previous in thread | raw e-mail



--- On Tue, 9/15/09, Peter Steele <psteele@maxiscale.com> wrote:

> From: Peter Steele <psteele@maxiscale.com>
> Subject: Can lagg0 failback be prevented?
> To: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
> Date: Tuesday, September 15, 2009, 8:23 PM
> We're using the lag driver to provide
> automatic failover in case of a network outage. The default
> configuration looks like this:
> 
> lagg0:
> flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> metric 0 mtu 1500
>        
> options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
>         ether 00:a0:d1:e3:58:26
>         inet 192.168.17.40 netmask
> 0xfffff000 broadcast 192.168.31.255
>         inet 192.168.22.11 netmask
> 0xffffff00 broadcast 192.168.22.255
>         media: Ethernet autoselect
>         status: active
>         laggproto failover
>         laggport: nfe1 flags=0<>
>         laggport: nfe0
> flags=5<MASTER,ACTIVE>
> 
> If nfe0 was to fail, we get an (almost) automatic failover
> to nfe1:
> 
> lagg0:
> flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>
> metric 0 mtu 1500
>        
> options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
>         ether 00:a0:d1:e3:58:26
>         inet 192.168.17.40 netmask
> 0xfffff000 broadcast 192.168.31.255
>         inet 192.168.22.11 netmask
> 0xffffff00 broadcast 192.168.22.255
>         media: Ethernet autoselect
>         status: active
>         laggproto failover
>         laggport: nfe1
> flags=4<ACTIVE>
>         laggport: nfe0
> flags=1<MASTER>
> 
> The problem we're having is when nfe0 comes online again, a
> failback occurs making nfe0 active again. This causes a
> momentary network outage that we want to prevent. Is there a
> way to configure the lagg device to stay with the currently
> active interface, even if the MASTER interface comes back
> online?

Why don't you just load balance? Usually fallback implies that 
one link is preferred (such as a more favorable path, or higher 
speed). 

Barney







help

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?491701.32471.qm>