Re: Can lagg0 failback be prevented?
On Wednesday 16 September 2009 20:58:45 Peter Steele wrote: Not really, unless you manually change master. However I believe this also causes a slight or even bigger network outage. Any reason you're not using loadbalance algorithm, since it seems to suit you better? Our resident network guru is quite opposed to using the loadbalancing option since it comes with a lot of potentially undesirable baggage of its own... Then your best option is to patch lagg(4) with an avail algorithm, that prefers $master and sticks with an interface till it's detected down. When done properly the chances are good to get this into base. Another approach would be to change the failover with a 'fader' algorithm, that gradually fades from one nic to the other, kind of like an audio mixer, though I'm not sure if that's possible and would work satisfactory. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Can lagg0 failback be prevented?
I posted this on the -net list but didn't get any responses. I'm hoping a wider audience might help. We're using the lag driver to provide automatic failover in case of a network outage. The default configuration looks like this: lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:a0:d1:e3:58:26 inet 192.168.17.40 netmask 0xf000 broadcast 192.168.31.255 inet 192.168.22.11 netmask 0xff00 broadcast 192.168.22.255 media: Ethernet autoselect status: active laggproto failover laggport: nfe1 flags=0 laggport: nfe0 flags=5MASTER,ACTIVE If nfe0 was to fail, we get an (almost) automatic failover to nfe1: lagg0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=19bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4 ether 00:a0:d1:e3:58:26 inet 192.168.17.40 netmask 0xf000 broadcast 192.168.31.255 inet 192.168.22.11 netmask 0xff00 broadcast 192.168.22.255 media: Ethernet autoselect status: active laggproto failover laggport: nfe1 flags=4ACTIVE laggport: nfe0 flags=1MASTER 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-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Can lagg0 failback be prevented?
On Wednesday 16 September 2009 16:12:25 Peter Steele wrote: 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? Not really, unless you manually change master. However I believe this also causes a slight or even bigger network outage. Any reason you're not using loadbalance algorithm, since it seems to suit you better? -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Can lagg0 failback be prevented?
Not really, unless you manually change master. However I believe this also causes a slight or even bigger network outage. Any reason you're not using loadbalance algorithm, since it seems to suit you better? Our resident network guru is quite opposed to using the loadbalancing option since it comes with a lot of potentially undesirable baggage of its own... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
