02-07-2022 07:31 AM
Hello All,
We have inherited a network with a ton of video traffic and multicast. I am researching what "no ip igmp snooping tcn flood" command is needed for here. It is on some ports but some it is not. Not sure if we should just allow it on all ports? Some vlans also have pim sparse mode set. From what I gather, there really is no reason to disable it since it can cause congestion and possible DOS. We also don't want to break the network by removing it but want to keep network consistent! Thanks for any help on this one!
02-07-2022 12:38 PM
Hi ,
The command " no ip igmp snooping tcn flood" command is used to disable multicast flooding when there is a spanning tree topology change notification from the root switch. When topology changes happen, multicast traffic will be flooded to all ports for a period of time before it stabilizes. As stated in the document attached below: "Only the multicast groups that have been joined by a port are sent to that port, even during a topology change."
There is a possibility it's currently set on ports that receive and send multicast traffic. I would suggest validating the traffic path for multicast in your network to better understand which ports need the command.
Refer to this documentation below which expands more on this behavior :
"Some vlans also have pim sparse mode set."
- Vlans with this command set indicates that there are clients in those vlans that utilize multicast traffic. This is a PIM mode that is typically used when we have clients spread throughout the network and it uses a rendezvous point AKA "RP" which serves as the "middle-man" between the multicast source and the clients that need multicast traffic. This helps with limiting the amount of multicast streams sent through the network so yes, it's useful in limiting congestion on the network.
Please refer to this document below which expands more on this:
02-09-2022 05:31 AM
Prince,
Thank you for the links. I have taken a look at them. I suppose we will have to find out why some switches have it set and some don't. It is still unclear as to why it is on some ports and some not. This is the answer we can't find in the Cisco links. Some more research is needed on our part. Appreciate the response.
02-09-2022 11:44 AM
Jay,
Generally, we set the multicast commands on switches performing layer 3 functionality as switches just performing layer 2 functions just forward the traffic upstream to the layer 3 device for routing so that could be a potential reason why you may see the commands on some switches and not on others.
However, every network is different so deeper investigating is needed to better understand
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide