From: Josh Coombs <jcoombs@staff.gwi.net>
To: illumos-discuss <discuss@lists.illumos.org>
Subject: [discuss] Mellanox LACP aggr fails without snoop if using vlan tags
Date: Thu, 31 Oct 2024 16:47:21 -0400 [thread overview]
Message-ID: <CACcUnf9JFSP6mRvYHgvNKJcpdXmpzsCqNA5gdBdgrxVBmtWSsA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]
I've got a brand new r151050e install using a Mellanox CNX5 card, dual 25Gb
ports paired up in an aggr to a Juniper EX4650 cluster. It will only work
if I start snoop on the aggr. Without doing so, it won't pass traffic. I
ran into this back in 2019 with bnx devices after upgrading to r151030 and
was never able to find a fix, that box I ended up changing NICs to intel to
get around the problem.
It also works if I do a snoop -P -d aggr0 so it may not be promiscuous mode
directly that's 'fixing' things?
If I rebuild the setup and don't use VLAN tagging, that appears to work as
anticipated which is different from my prior bnx troubles. Those I never
got around to testing with vlans on OmniOS.
When not working, I can see my aggr's mac address upstream on the switches.
I haven't tried manually firing packets out an interface but based on last
time I expect that will work. The issue seems to be on the receive side in
OmniOS, something about starting a snoop suddenly allows OmniOS to accept
the packets fully for some reason.
I don't have a production and lab setup, sadly my test box is in a
datacenter that is an hour away, unmanned so I'm limited in what I can do
at the moment. I've got a little bit of time before I need to lock the conf
for production use, but can only be onsite once or twice a week at best. I
can live without vlan tagging, but if this is an unexpected fail I'd like
to gather what data I can to help before shutting the door to testing?
Joshua Coombs
------------------------------------------
illumos: illumos-discuss
Permalink: https://illumos.topicbox.com/groups/discuss/T608dab80e5db30f6-Mf17e7261eeb23be4da6bab83
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription
[-- Attachment #2: Type: text/html, Size: 2705 bytes --]
next reply other threads:[~2024-10-31 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 20:47 Josh Coombs [this message]
2024-10-31 21:23 ` Alex Wilson via illumos-discuss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACcUnf9JFSP6mRvYHgvNKJcpdXmpzsCqNA5gdBdgrxVBmtWSsA@mail.gmail.com \
--to=jcoombs@staff.gwi.net \
--cc=discuss@lists.illumos.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).