From owner-freebsd-net@FreeBSD.ORG Wed Sep 16 01:23:34 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 032B6106568D for ; Wed, 16 Sep 2009 01:23:34 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from server505.appriver.com (server505c.appriver.com [98.129.35.7]) by mx1.freebsd.org (Postfix) with ESMTP id C02F48FC08 for ; Wed, 16 Sep 2009 01:23:33 +0000 (UTC) X-Policy: GLOBAL - maxiscale.com X-Primary: psteele@maxiscale.com X-Note: This Email was scanned by AppRiver SecureTide X-ALLOW: psteele@maxiscale.com ALLOWED X-Virus-Scan: V- X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES->UNITED STATES X-Note-Sending-IP: 98.129.23.15 X-Note-Reverse-DNS: ht02.exg5.exghost.com X-Note-WHTLIST: psteele@maxiscale.com X-Note: User Rule Hits: X-Note: Global Rule Hits: 111 112 113 114 118 119 130 215 X-Note: Mail Class: ALLOWEDSENDER X-Note: Headers Injected Received: from [98.129.23.15] (HELO ht02.exg5.exghost.com) by server505.appriver.com (CommuniGate Pro SMTP 5.2.14) with ESMTPS id 11569536 for freebsd-net@freebsd.org; Tue, 15 Sep 2009 19:23:32 -0500 Received: from mbx03.exg5.exghost.com ([169.254.1.239]) by ht02.exg5.exghost.com ([98.129.23.15]) with mapi; Tue, 15 Sep 2009 19:23:31 -0500 From: Peter Steele To: "freebsd-net@freebsd.org" Date: Tue, 15 Sep 2009 19:23:29 -0500 Thread-Topic: Can lagg0 failback be prevented? Thread-Index: Aco2Y+qOd10xyJqxQqOt/5Uy+CM2MQ== Message-ID: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3042DBE7@MBX03.exg5.exghost.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 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: Wed, 16 Sep 2009 01:23:34 -0000 We're using the lag driver to provide automatic failover in case of a netwo= rk outage. The default configuration looks like this: lagg0: flags=3D8843 metric 0 mtu 15= 00 options=3D19b 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=3D0<> laggport: nfe0 flags=3D5 If nfe0 was to fail, we get an (almost) automatic failover to nfe1: lagg0: flags=3D8843 metric 0 mtu 15= 00 options=3D19b 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=3D4 laggport: nfe0 flags=3D1 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 w= ant to prevent. Is there a way to configure the lagg device to stay with th= e currently active interface, even if the MASTER interface comes back onlin= e?