Date: Thu, 5 Oct 2017 19:34:51 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: rainer@ultra-secure.de Cc: freebsd-net@freebsd.org Subject: Re: lagg interface doesn't work Message-ID: <59D626EB.50006@grosbein.net> In-Reply-To: <9cc65618239aeb15abe707e9734b493a@ultra-secure.de> References: <F95A6802-8EC3-4027-8AA0-B38118F9A8D9@ultra-secure.de> <59D5E81A.5080700@grosbein.net> <90efe3d3524854f2a28e14f6496b8d88@ultra-secure.de> <59D5F317.8030104@grosbein.net> <436c7745802ce7ca9d196cccf600828a@ultra-secure.de> <59D621C9.1070704@grosbein.net> <9cc65618239aeb15abe707e9734b493a@ultra-secure.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05.10.2017 19:25, rainer@ultra-secure.de wrote: > Am 2017-10-05 14:12, schrieb Eugene Grosbein: >> On 05.10.2017 18:20, rainer@ultra-secure.de wrote: >> >>> 11.1-AMD64. >> >> Please run "tcpdump -enp -i bxe0" to see, if it shows incoming and/or >> outgoing >> LACP ethernet frames while lagg tries to negotiate its state with >> partner switch, >> and show output. > > > (server-prod </root>) 0 # tcpdump -r out1.dmp > reading from file out1.dmp, link-type EN10MB (Ethernet) > 12:20:15.163568 LACPv1, length 110 > 12:20:16.212569 LACPv1, length 110 > 12:20:19.389730 MARKERv1, length 110 > 12:20:19.389733 LACPv1, length 110 > 12:20:20.449569 MARKERv1, length 110 > 12:20:47.372875 LACPv1, length 110 > 12:21:18.527876 LACPv1, length 110 > 12:21:49.891923 LACPv1, length 110 I asked for -enp flags for a reason, please use them. And even better -enpv.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?59D626EB.50006>