IGMP Snooping with SJA1110

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

IGMP Snooping with SJA1110

185 Views
sg_cnh
Contributor I

Hello,

I have an S32G with SJA1110 running bsp43 and am trying to enable IGMP snooping to dynamically route multicast streams.  I have identified a few unique issues related to IGMP which I am not sure how to resolve.  I have confirmed that disabling IGMP snooping causes multicast packets to flood the switch, so the IGMP snooping option is doing something...  Just not the expected behavior.

  1. Multicast traffic is always forwarded to the lowest enumerated active port
    1. A stream egressing on port 4 with a node on port 3 requesting that traffic through IGMP will cause traffic to egress through port 1 (if that link is active) as if port 1 had requested the traffic.  If the port 1 link is not active, traffic will be forwarded to port 2 if that link is active.
    2. I am able to manually route the traffic with mdb, but my expectation is that IGMP snooping should be managing this automatically
  2. Enabling multicast-querier does not cause membership queries to egress the switch ports
    1. There are  IGMP queries on the DSA bridge interface, but no IGMP queries are visible on other links connected to the switch
    2. I suspect I may need to set up a tc rule to trap IGMP queries from the bridge port and redirect them to the switch ports?

I'm not clear if this is some issue with Linux configuration or a limitation from switch hardware.

Thanks for any suggestions.

0 Kudos
Reply
0 Replies
%3CLINGO-SUB%20id%3D%22lingo-sub-2199453%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EIGMP%20Snooping%20with%20SJA1110%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2199453%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CDIV%20class%3D%22%22%3E%3CDIV%20class%3D%22%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20have%20an%20S32G%20with%20SJA1110%20running%20bsp43%20and%20am%20trying%20to%20enable%20IGMP%20snooping%20to%20dynamically%20route%20multicast%20streams.%26nbsp%3B%20I%20have%20identified%20a%20few%20unique%20issues%20related%20to%20IGMP%20which%20I%20am%20not%20sure%20how%20to%20resolve.%26nbsp%3B%20I%20have%20confirmed%20that%20disabling%20IGMP%20snooping%20causes%20multicast%20packets%20to%20flood%20the%20switch%2C%20so%20the%20IGMP%20snooping%20option%20is%20doing%20something...%26nbsp%3B%20Just%20not%20the%20expected%20behavior.%3C%2FP%3E%3COL%3E%3CLI%3EMulticast%20traffic%20is%20always%20forwarded%20to%20the%20lowest%20enumerated%20active%20port%3COL%3E%3CLI%3EA%20stream%20egressing%20on%20port%204%20with%20a%20node%20on%20port%203%20requesting%20that%20traffic%20through%20IGMP%20will%20cause%20traffic%20to%20egress%20through%20port%201%20(if%20that%20link%20is%20active)%20as%20if%20port%201%20had%20requested%20the%20traffic.%26nbsp%3B%20If%20the%20port%201%20link%20is%20not%20active%2C%20traffic%20will%20be%20forwarded%20to%20port%202%20if%20that%20link%20is%20active.%3C%2FLI%3E%3CLI%3EI%20am%20able%20to%20manually%20route%20the%20traffic%20with%20mdb%2C%20but%20my%20expectation%20is%20that%20IGMP%20snooping%20should%20be%20managing%20this%20automatically%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3CLI%3EEnabling%20multicast-querier%20does%20not%20cause%20membership%20queries%20to%20egress%20the%20switch%20ports%3COL%3E%3CLI%3EThere%20are%26nbsp%3B%20IGMP%20queries%20on%20the%20DSA%20bridge%20interface%2C%20but%20no%20IGMP%20queries%20are%20visible%20on%20other%20links%20connected%20to%20the%20switch%3C%2FLI%3E%3CLI%3EI%20suspect%20I%20may%20need%20to%20set%20up%20a%20tc%20rule%20to%20trap%20IGMP%20queries%20from%20the%20bridge%20port%20and%20redirect%20them%20to%20the%20switch%20ports%3F%3C%2FLI%3E%3C%2FOL%3E%3C%2FLI%3E%3C%2FOL%3E%3CP%3EI'm%20not%20clear%20if%20this%20is%20some%20issue%20with%20Linux%20configuration%20or%20a%20limitation%20from%20switch%20hardware.%3C%2FP%3E%3CP%3EThanks%20for%20any%20suggestions.%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E