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>
next in thread | previous in thread | raw e-mail | index | archive | help
=0A=0A--- On Tue, 9/15/09, Peter Steele <psteele@maxiscale.com> wrote:=0A= =0A> From: Peter Steele <psteele@maxiscale.com>=0A> Subject: Can lagg0 fail= back be prevented?=0A> To: "freebsd-net@freebsd.org" <freebsd-net@freebsd.o= rg>=0A> Date: Tuesday, September 15, 2009, 8:23 PM=0A> We're using the lag = driver to provide=0A> automatic failover in case of a network outage. The d= efault=0A> configuration looks like this:=0A> =0A> lagg0:=0A> flags=3D8843<= UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>=0A> metric 0 mtu 1500=0A> =A0 =A0 = =A0 =A0=0A> options=3D19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM= ,TSO4>=0A> =A0 =A0 =A0 =A0 ether 00:a0:d1:e3:58:26=0A> =A0 =A0 =A0 =A0 inet= 192.168.17.40 netmask=0A> 0xfffff000 broadcast 192.168.31.255=0A> =A0 =A0 = =A0 =A0 inet 192.168.22.11 netmask=0A> 0xffffff00 broadcast 192.168.22.255= =0A> =A0 =A0 =A0 =A0 media: Ethernet autoselect=0A> =A0 =A0 =A0 =A0 status:= active=0A> =A0 =A0 =A0 =A0 laggproto failover=0A> =A0 =A0 =A0 =A0 laggport= : nfe1 flags=3D0<>=0A> =A0 =A0 =A0 =A0 laggport: nfe0=0A> flags=3D5<MASTER,= ACTIVE>=0A> =0A> If nfe0 was to fail, we get an (almost) automatic failover= =0A> to nfe1:=0A> =0A> lagg0:=0A> flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX= ,MULTICAST>=0A> metric 0 mtu 1500=0A> =A0 =A0 =A0 =A0=0A> options=3D19b<RXC= SUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>=0A> =A0 =A0 =A0 =A0 et= her 00:a0:d1:e3:58:26=0A> =A0 =A0 =A0 =A0 inet 192.168.17.40 netmask=0A> 0x= fffff000 broadcast 192.168.31.255=0A> =A0 =A0 =A0 =A0 inet 192.168.22.11 ne= tmask=0A> 0xffffff00 broadcast 192.168.22.255=0A> =A0 =A0 =A0 =A0 media: Et= hernet autoselect=0A> =A0 =A0 =A0 =A0 status: active=0A> =A0 =A0 =A0 =A0 la= ggproto failover=0A> =A0 =A0 =A0 =A0 laggport: nfe1=0A> flags=3D4<ACTIVE>= =0A> =A0 =A0 =A0 =A0 laggport: nfe0=0A> flags=3D1<MASTER>=0A> =0A> The prob= lem we're having is when nfe0 comes online again, a=0A> failback occurs mak= ing nfe0 active again. This causes a=0A> momentary network outage that we w= ant to prevent. Is there a=0A> way to configure the lagg device to stay wit= h the currently=0A> active interface, even if the MASTER interface comes ba= ck=0A> online?=0A=0AWhy don't you just load balance? Usually fallback impli= es that =0Aone link is preferred (such as a more favorable path, or higher = =0Aspeed). =0A=0ABarney=0A=0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?491701.32471.qm>