Date: Wed, 16 Sep 2009 09:12:25 -0500 From: Peter Steele <psteele@maxiscale.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Can lagg0 failback be prevented? Message-ID: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3042DC5F@MBX03.exg5.exghost.com>
next in thread | raw e-mail | index | archive | help
I posted this on the -net list but didn't get any responses. I'm hoping a w= ider audience might help. 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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 15= 00 options=3D19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO= 4> 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<MASTER,ACTIVE> If nfe0 was to fail, we get an (almost) automatic failover to nfe1: lagg0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 15= 00 options=3D19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO= 4> 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<ACTIVE> laggport: nfe0 flags=3D1<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 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7B9397B189EB6E46A5EE7B4C8A4BB7CB3042DC5F>