public inbox for discuss@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: "Alex Wilson via illumos-discuss" <discuss@lists.illumos.org>
To: discuss@lists.illumos.org
Cc: rm@fingolfin.org
Subject: Re: [discuss] Mellanox LACP aggr fails without snoop if using vlan tags
Date: Fri, 1 Nov 2024 07:23:16 +1000	[thread overview]
Message-ID: <9682f6e3-b34b-495e-bdea-53e98a4cf9d5@cooperi.net> (raw)
In-Reply-To: <CACcUnf9JFSP6mRvYHgvNKJcpdXmpzsCqNA5gdBdgrxVBmtWSsA@mail.gmail.com>

Hi Josh,

On 1/11/24 06:47, Josh Coombs wrote:
> 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?
> 

I've seen this bug as well. When I dtrace the calls into mlxcx what I 
see is that aggr never gives the driver any VLAN tag filters for the 
default group (but it does give MAC filters), so no traffic other than 
on the default tag ends up received.

If you perturb the MAC state of the aggr enough it will switch to 
explicit VLAN tag filters and work fine (e.g. if you add a VNIC as well 
as the VLAN interface, the existence of the VNIC will fix it since that 
causes MAC to add an explicit VLAN tag filter for the vlan DL)

I think this is a semantic bug here -- I suspect MAC is assuming that if 
it adds just MAC filters and no VLAN filters to a NIC, that means all 
tagged traffic for that MAC should be matched, not just un-tagged. 
Unfortunately the documentation (mac_capab_rings.9e and mac.9e) is not 
very clear on this point and some drivers (definitely mlxcx I can speak 
for, since I wrote most of it) have interpreted it differently.

For now I've just been always using VNICs, since those always generate 
explicit filters and work fine. But we should get this fixed up, and 
probably the documentation adjusted to spell it out more clearly so no 
other new drivers make the same mistake going forwards.

------------------------------------------
illumos: illumos-discuss
Permalink: https://illumos.topicbox.com/groups/discuss/T608dab80e5db30f6-M7a4bf3d343ab2df1faf1eed8
Delivery options: https://illumos.topicbox.com/groups/discuss/subscription

      reply	other threads:[~2024-10-31 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-31 20:47 Josh Coombs
2024-10-31 21:23 ` Alex Wilson via illumos-discuss [this message]

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=9682f6e3-b34b-495e-bdea-53e98a4cf9d5@cooperi.net \
    --to=discuss@lists.illumos.org \
    --cc=rm@fingolfin.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).