Please see the below diagram. I have a scenario where we currently receive three multicast sources on dedicated VLANs. As of today we do not do any pruning or snooping on this VLAN it is broadcast based and we would like to keep it that way as some receivers are mandated to not be IGMP-dependent.
HOWEVER, there is an exception. We have a network of receivers that need to have the granularity to request multicast group membership from multiple source VLANs and have non-interested traffic pruned from the receivers. This is a simple setup in a scenario where you have a single VLAN for the senders as I would just turn up a snooper/querier setup and let the local L3 switch handle the joins/leaves. Unfortunately though we have this need to allow multiple source VLANs to be candidates for sending to any downstream receiver. What I don't want to do is change the nature of the upstream multicast streams coming in to the switch. If that were the case then we could go to a routed multicast environment and not have to worry about VLAN segmentation issues.
What is the best practice/recommended config to allow a setup like this to work? I'm also concerned with the possibility of flooding multicast between VLAN A,B and C accidentally by combining the VLANs.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...