cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
328
Views
0
Helpful
0
Replies

CBS350 IGMP and filtering unregistered multicast

Hi.
We have issues with CBS350 and SG350 switches when it comes to deal with multicast in the following ranges:

Local Network Control Block (224.0.0.0 - 224.0.0.255 (224.0.0/24))
Internetwork Control Block (224.0.1.0 - 224.0.1.255 (224.0.1/24))

 

We use those switches for AV application (Audio, video, lighting). A lot of the traffic that travels on our networks is multicast traffic. To make sure that the switches don't get flooded with that multicast traffic, we enable IGMP  snooping on all switches and we elect an IGMP querrier on one of the switches. We also enable "filter unregistered multicast" on all ports so the network don't get flooded by unregistered multicast (multicast traffic that does not have a listener).
The problem that we have when we activate "filter unregistered multicast", is that it also filters some of the  224.0.0.x and the 224.0.1.x traffic that is used for discovery, clocking and other protocoles that should be treated as broadcast due to purpose of that traffic. In my understanding, no device sends IGMP join or IGMP leave messages for those specific multicast groups.
Also, I sometimes have to disable "filter unregistered multicast" on my ISL ports (uplinks) to make sure that the discovery/clocking/other traffic can get to other switches. By doing this, I generate more traffic on my ISL while reducing my bandwith overhead.

 

Does anybody have any experience with that kind of issue?

 

0 REPLIES 0