Date: Thu, 24 Sep 2009 09:32:40 +0300 From: Nikolay Denev <ndenev@gmail.com> To: Peter Steele <psteele@maxiscale.com> Cc: freebsd-net@freebsd.org Subject: Re: Can lagg0 failback be prevented? Message-ID: <C0778F03-C450-4C69-8AF0-4A6A8F9E690F@gmail.com> In-Reply-To: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3042DBE7@MBX03.exg5.exghost.com> References: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3042DBE7@MBX03.exg5.exghost.com>
next in thread | previous in thread | raw e-mail | index | archive | help
How long exactly is that "momentary network outage"? If it's longer than a few (1-5) seconds it may be due to RSTP or STP enabled on the switch. You could try disabling STP on these ports and see if it will start forwarding traffic faster. -- Regards, Nikolay Denev On 16 Sep, 2009, at 03:23 , Peter Steele wrote: > 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? > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C0778F03-C450-4C69-8AF0-4A6A8F9E690F>