Date: Sat, 29 Oct 2016 00:17:47 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Mark Saad <nonesuch@longcount.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: lacp weirdness on 10.3-STABLE Message-ID: <20161028211747.GU57714@zxy.spb.ru> In-Reply-To: <CAMXt9NY46rd1v1XfVH2HFp2ay6cnayi-k6EVUy9cuoO3RE-rqQ@mail.gmail.com> References: <CAMXt9NY46rd1v1XfVH2HFp2ay6cnayi-k6EVUy9cuoO3RE-rqQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 28, 2016 at 05:14:37PM -0400, Mark Saad wrote: > Hi everyone > I wast sure where to start on this one. So let me jump in here. > I have a box with a dual port solarflare card. Both ports were running in > lacp > lagg for a while with out any issues. I took the box down free up some > space in the rack. I reciently > booted it back up; using the original network ports and cables from the > original seutp. However I can not bring up the lagg in lacp mode. Trussing > the process is showing this > > n01:~ # ifconfig lagg0 up lacp > ifconfig: lacp: bad value ifconfig lagg0 up laggproto lacp > n01:~ # truss ifconfig lagg0 up lacp > ..... > read(4,"# $FreeBSD: stable/10/etc/networ"...,4096) = 368 (0x170) > read(4,0x801c47000,4096) = 0 (0x0) > close(4) = 0 (0x0) > ifconfig: write(2,"ifconfig: ",10) = 10 (0xa) > lacp: bad valuewrite(2,"lacp: bad value",15) = 15 (0xf) > .... > > I am at a loss. The Switch ports are in the original configs as well. > Anyone have any ideas ? > Kernel and Userland are FreeBSD 10.3-STABLE #0: Tue Aug 23 14:48:27 EDT > 2016 > > > -- > mark saad | nonesuch@longcount.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161028211747.GU57714>