Date: Wed, 22 Feb 2017 11:01:58 +0100 From: Harry Schmalzbauer <freebsd@omnilan.de> To: Ingeborg Hellemo <ingeborg.hellemo@uit.no> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 11.0, bxe and lagg Message-ID: <58AD6196.8030908@omnilan.de> In-Reply-To: <201702211023.v1LANQSL003773@halvsju.cc.uit.no> References: <201702211023.v1LANQSL003773@halvsju.cc.uit.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Bezüglich Ingeborg Hellemo's Nachricht vom 21.02.2017 11:23 (localtime): > Trond.Endrestol@fagskolen.gjovik.no said: >> Why does lagg0 refer to bge2 and bge3 in the ifconfig output, and not to >> bxe2 and bxe3? > My bad! No cut and paste from the console of the host without net. Wrote most > of it by hand but ended up using cut and paste from another host and forgot to > edit. > > Correct lines: > laggproto lacp lagghash l2,l3,l4 > laggport: bxe2 flags=0<> > laggport: bxe3 flags=0<> > There are known problems with laggproto lacp and if_bxe(4) due to full-duplex detection I guess. Workarround seems to be putting if_bxe(4) into promisc mode. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606 Especially comment #8 and #13! Mabye you can add your report to that bug, to raise it's priority. Using if_lagg(4) with laggproto lacp and if_igb(4) doesn't show any problems here on 11(-stable). I also think there were LACPDU changes forcing the switch to be set to active mode, but a very quick look didn't reveal a matching commit, so maybe I'm wrong. Anyway, in your case it seems if_bxe(4) is the root cause, not a configuration mismatch. -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58AD6196.8030908>