From owner-freebsd-net@FreeBSD.ORG Fri Sep 25 14:14:22 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C45C11065670 for ; Fri, 25 Sep 2009 14:14:22 +0000 (UTC) (envelope-from barney_cordoba@yahoo.com) Received: from n4a.bullet.mail.ac4.yahoo.com (n4a.bullet.mail.ac4.yahoo.com [76.13.13.67]) by mx1.freebsd.org (Postfix) with SMTP id 764868FC0C for ; Fri, 25 Sep 2009 14:14:22 +0000 (UTC) Received: from [76.13.13.25] by n4.bullet.mail.ac4.yahoo.com with NNFMP; 25 Sep 2009 14:14:21 -0000 Received: from [76.13.10.171] by t4.bullet.mail.ac4.yahoo.com with NNFMP; 25 Sep 2009 14:14:21 -0000 Received: from [127.0.0.1] by omp112.mail.ac4.yahoo.com with NNFMP; 25 Sep 2009 14:14:21 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 562061.69649.bm@omp112.mail.ac4.yahoo.com Received: (qmail 87317 invoked by uid 60001); 25 Sep 2009 14:14:21 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1253888061; bh=2+WZgkgRWps4PTBRhk9sz22l7Jnx9xQ2+QsCl5DA7s8=; 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=0UVnaC3OvPjdB41NfRMzYjz1oyp0hR2ANxB6tmlGHvJ/3RizPHTtvxq0UXN2+rFYIhDwCdHg46yTUJtpoaxGt/srFJIlJzWZRya/v8UvSQ4Vd6IijOh+qyMHm5yUCsK0kQDFPtLLNqz24gnSM68ILZIwoW3P3Kl5NYP5n69VmNs= 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=PF4GY1bjzHtzSvHMMZhvMN+OAqCBMBHRmOEO1nMx8fyHjQklpCYi7tevvIdiCQoyvezgjbFYdqllT8C8BlpecUUIhXDl4+KaP0ldslEcwDzeRBeuk8s09fMrKzAepMfQxiZVYwenHg2cD3eXAb/B5KVddheYsBPTcOyORt/1PqM=; Message-ID: <461385.86611.qm@web63904.mail.re1.yahoo.com> X-YMail-OSG: TVOg4F0VM1l9YipZaSSz.ZIO8FofMCspErOk74eEZMx5Y5vYUYuMHhmp9WTws94YWVYsoNmaI3_Tf8kvZL6megU1LzKVJOZMfwMBDH5OxvHaUdKeOqjKJtz4KpXBSd7Te7BLE1s5aigz2g6X1MUrG8k1xj0fAnG5ECzxSxpDUltGq8KMwpK45EOuTJIwAdEepXAzJZ8TkR3UkJAQe3RFp9aPUjwQqortY7hvCLJlgOiAArvm13FELZjupUkAf2_7AUj8To9jjt_15wOmK_VqDRjATwl2 Received: from [98.203.21.152] by web63904.mail.re1.yahoo.com via HTTP; Fri, 25 Sep 2009 07:14:21 PDT X-Mailer: YahooMailClassic/7.0.14 YahooMailWebService/0.7.347.3 Date: Fri, 25 Sep 2009 07:14:21 -0700 (PDT) From: Barney Cordoba To: Peter Steele , Nikolay Denev In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-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: Fri, 25 Sep 2009 14:14:22 -0000 =0A=0A--- On Thu, 9/24/09, Nikolay Denev wrote:=0A=0A> F= rom: Nikolay Denev =0A> Subject: Re: Can lagg0 failback b= e prevented?=0A> To: "Peter Steele" =0A> Cc: freebsd= -net@freebsd.org=0A> Date: Thursday, September 24, 2009, 2:32 AM=0A> How lo= ng exactly is that "momentary=0A> network outage"?=0A> If it's longer than = a few (1-5) seconds it may be due to=0A> RSTP or STP enabled on the switch.= =0A> You could try disabling STP on these ports and see if it=0A> will=0A> = start forwarding traffic faster.=0A> =0A> --=0A> Regards,=0A> Nikolay Denev= =0A> =0A> =0A> =0A> =0A> On 16 Sep, 2009, at 03:23 , Peter Steele wrote:=0A= > =0A> > We're using the lag driver to provide automatic=0A> failover in ca= se of a network outage. The default=0A> configuration looks like this:=0A> = > =0A> > lagg0:=0A> flags=3D8843=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 br= oadcast 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 au= toselect=0A> >=A0 =A0 =A0 =A0 status: active=0A> >=A0 =A0 =A0 =A0 laggproto= failover=0A> >=A0 =A0 =A0 =A0 laggport: nfe1=0A> flags=3D0<>=0A> >=A0 =A0 = =A0 =A0 laggport: nfe0=0A> flags=3D5=0A> > =0A> > If nfe0 wa= s to fail, we get an (almost) automatic=0A> failover 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 ether 00:a0:d1:e3:58:26= =0A> >=A0 =A0 =A0 =A0 inet 192.168.17.40 netmask=0A> 0xfffff000 broadcast 1= 92.168.31.255=0A> >=A0 =A0 =A0 =A0 inet 192.168.22.11 netmask=0A> 0xffffff0= 0 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 failove= r=0A> >=A0 =A0 =A0 =A0 laggport: nfe1=0A> flags=3D4=0A> >=A0 =A0 = =A0 =A0 laggport: nfe0=0A> flags=3D1=0A> > =0A> > The problem we're= having is when nfe0 comes online=0A> again, a failback occurs making nfe0 = active again. This=0A> causes a momentary network outage that we want to pr= event.=0A> Is there a way to configure the lagg device to stay with the=0A>= currently active interface, even if the MASTER interface=0A> comes back on= line?=0A> > =0A=0AThe "outage" is because the failover isn't detected until= you get a =0Afailure. When a link down is detected, the backup port is ena= bled. =0ASo there is going to be some traffic loss. There may be packets in= =0Athe transmit queue as well.=0A=0AI asked earlier why you were using fail= over if you really don't care=0Awhich link it uses? If you load balance it = will use both links=0Aunless one of the links is down, in which case it wou= ld use one link.=0AYou'd avoid the problem that seems to concern you.=0A=0A= Barney=0A=0A=0A