From owner-freebsd-net@FreeBSD.ORG Sat Sep 19 20:36:05 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7BE71065697 for ; Sat, 19 Sep 2009 20:36:04 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from n3a.bullet.mail.ac4.yahoo.com (n3a.bullet.mail.ac4.yahoo.com [76.13.13.66]) by mx1.freebsd.org (Postfix) with SMTP id 909588FC1D for ; Sat, 19 Sep 2009 20:36:04 +0000 (UTC) Received: from [76.13.13.25] by n3.bullet.mail.ac4.yahoo.com with NNFMP; 19 Sep 2009 20:23:51 -0000 Received: from [76.13.10.176] by t4.bullet.mail.ac4.yahoo.com with NNFMP; 19 Sep 2009 20:23:51 -0000 Received: from [127.0.0.1] by omp117.mail.ac4.yahoo.com with NNFMP; 19 Sep 2009 20:23:51 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 653746.51671.bm@omp117.mail.ac4.yahoo.com Received: (qmail 33423 invoked by uid 60001); 19 Sep 2009 20:23:51 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1253391831; bh=9GYPNMurGKjn50OanWvyEaBA5VWc8tntrc58l4srWNA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=JoCEJyn50+nPxJOI3W+WOaV3J2/K3HgEB4B303pGUuLHB+w62rMRH/R/i9ZS4HxBnKMj3yQOPJPhux3FRY0Obvnh5rTsCPz3wW/cDZTcRRMBSZS88U+PUqry7IWKKNsUCFraDA1gEKgwUptuSitvqfsCyS9Rw+2lw9OVF8CR3nU= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=VL9U5KppfVnutG1RAk2Mb7x3x/1o6sOPU00w1Y0osiogRRnqKWdDS1zCjhgK1t6Io8Tgz07zbq9Z0pwXV6Yq7sy/ttAkgDH02DDPXAGdUAsmC+/YiLmQtZEZ8699fL4co98M6YpKoC41BUOvbVVpw9PsFC/yLDpThCWmBHc41fY=; Message-ID: <491701.32471.qm@web63901.mail.re1.yahoo.com> X-YMail-OSG: Lo.KTw4VM1nItDLwjnIIyimxC2SJHeNDkjqy_5R7CcVRBwfWgDZBlPxiFkTk7LsjkxqHQbW0VWTCjfohG48PqKNW2lzlxMhC2hfuA0qH4KkXk0NDqMMvuwmOWXhwKSbg2Xl20Udyjpb2rti0dUBZyYJb0BPsqJPtqiGfOzyUoyh3esSvWfUEbKllK1HsHTy.CU35sOS..XCSzRopxocIyV208JMyrhdwMrI6JferuHbYm02zqGV_34XFmVKpPrHY_llD1mXVTsLcuAyjsJHRMxmHIclXbIsiXTuJA.qz5qpTHK3pgdvwS3aV Received: from [98.203.21.152] by web63901.mail.re1.yahoo.com via HTTP; Sat, 19 Sep 2009 13:23:51 PDT X-Mailer: YahooMailClassic/7.0.14 YahooMailWebService/0.7.347.2 Date: Sat, 19 Sep 2009 13:23:51 -0700 (PDT) From: Barney Cordoba To: Peter Steele In-Reply-To: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3042DBE7@MBX03.exg5.exghost.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: net@freebsd.org Subject: Re: Can lagg0 failback be prevented? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Sep 2009 20:36:05 -0000 =0A=0A--- On Tue, 9/15/09, Peter Steele wrote:=0A= =0A> From: Peter Steele =0A> Subject: Can lagg0 fail= back be prevented?=0A> To: "freebsd-net@freebsd.org" =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=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=0A> =0A> If nfe0 was to fail, we get an (almost) automatic failover= =0A> to nfe1:=0A> =0A> lagg0:=0A> flags=3D8843=0A> metric 0 mtu 1500=0A> =A0 =A0 =A0 =A0=0A> options=3D19b=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= =0A> =A0 =A0 =A0 =A0 laggport: nfe0=0A> flags=3D1=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