Link aggregation in FreeBSD 8 reddit / BSD ---------------------------------------------------------------------- [deleted] · 2011-08-29 08:27 I was in a situation recently where a switch lost its configuration, vlans and all, and all the machines behind hit were connected to a secondary switch. Most of them were Debian Linux, using a bond-interface to team eth0 and eth1. So each NIC was connected to one switch. None of the Linux machines felt any issues. The FreeBSD machines however that had chosen the NIC connected to the failed switch as master port all went down. Reason for this is that under failover mode the lagg driver will only switch over to a non master port if the link goes down. With configuration gone, vlans gone, the link was active but no traffic was going through. My emergency solution to this is to try and make a heartbeat script that can send ICMP through each of the interfaces but is there no better link aggregation in the BSD world? How would OpenBSD handle this issue for example? Also, I haven't had time to test the heartbeat idea yet, but it all falls on whether it can ping using the -I argument through one NIC without going over the lagg-interface. Is this possible using just the ping utility? ---------------------------------------------------------------------- sh_ · 2011-08-29 09:01 carp(4) originated on OpenBSD, which also provides ifstated(8) for monitoring the link in some user-defined way (e.g. pinging) and setting the interface up/down as necessary. ---------------------------------------------------------------------- [deleted] · 2011-08-29 09:04 Thank you, something told me that OpenBSD had better implementations for this but I hadn't used it in years so I wasn't sure. ---------------------------------------------------------------------- ciny · 2011-08-29 09:16 FreeBSD has [carp](http://www.freebsd.org/doc/handbook/carp.html) implemented as well. ---------------------------------------------------------------------- masta · 2011-08-29 14:35 I just run ipv6 on the interfaces for the test address. It's a nice way to know if two interfaces are on the same vlan, or whatever ethernet broadcast domain. Then just ping one interface from the other to test the switch, and/or ping the router to test the IP. ---------------------------------------------------------------------- thompsa · 2011-08-29 18:15 You should use LACP mode rather than failover. LACP has a heartbeat protocol while failover is intended just for the link status. ---------------------------------------------------------------------- [deleted] · 2011-08-29 18:20 I had to double check that it was actually in the manual on the machine where I printed it from. And it was, but I totally overlooked it. Thanks! I will test it first and if it goes well then ditching failover is quite likely. Edit: Thinking back I actually printed and showed this to a Cisco guy at work, asking if any of these options could be a good solution. I verified on google that the model of switch we use does support lacp in at least the advertised update I saw the release notes for. Thanks again!