Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Feb 2020 13:42:29 +0700
From:      Eugene Grosbein <eugen@grosbein.net>
To:        Mark Saad <nonesuch@longcount.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: LACP / Slow-protocol issue
Message-ID:  <bb566a20-7fbb-03f3-cb6a-83371e39486d@grosbein.net>
In-Reply-To: <CAMXt9NYVyk7xpevMJE65eG8D2JPg2aY3X2Sh4r2WusqcQMzkGA@mail.gmail.com>
References:  <CAMXt9NYVyk7xpevMJE65eG8D2JPg2aY3X2Sh4r2WusqcQMzkGA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
11.02.2020 2:30, Mark Saad wrote:

> Hello FreeBSD Hackers
>   I was wondering if there is anyone on-list who has hands on
> knowledge of the "slow-protocols" and in particular lacp .
> 
> I am running a fairly new 12.1-STABLE amd64 r354698 , for reasons I
> can't yet identify a two port lacp lagg has a short <1sec blip where
> switches and lagg members believe each side has stopped distributing
> lacp slow-protocol frames.  I am not super knowledgeable about how to
> diagnose the slow-protocol frames to see who is at fault . Any insight
> here would help.

Just use: tcpdump -s0 -np -i parent0 not ip
Replace "parent0" with name of your real (physical) interface name (one of), like igb0.

You may be facing one of iflib's problems, so try booting FreeBSD 11.3-RELEASE (pre-iflib)
to compare behaviour and see if it runs better or not.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb566a20-7fbb-03f3-cb6a-83371e39486d>