I have multiple (like more than 100) IP igmp join-group statements for multiple multicast groups in a single interface. Is there any way to summarize all these multiple igmp join-group statements in one join-group satement. I was planning to use ip igmp access-group with an access-list. But igmp access-group is for filtering a multicast group and it's not a joining group. Any help is appreciated!
Not that I'm aware of. If you were to summarize, the router would think that you'd want to join the summarized group instead of the individual groups that you're needing. Do you have these joins on the router's interface?
Yes, I configured the joined statement on the CE router as it is connected to MPLS cloud,. My plan was to create like a standard access-list that permit all the multiple multicast groups and create a single igmp-join group on the router's interface and bind it with that standard access-list. but still no hope....I don't want to use summarization as you said the router might attempt to join that specific summarized group rather than those specific groups....weired!
Why do you configure join statements at all? Do you really need them? Why don't you just enable PIM (or IGMP if there are no other PIM Routers connected) on your interface and let the clients send the IGMP-Joins?
I agree with Marcel. You usually let the client send the igmp join, otherwise it ends up being an administrative nightmare. On top of that, your interface will always join a group that clients on that segment may not need.
The "ip igmp join-group" command is actually used to make the router itself to join the group as a group member. This command is totally used as a testing method if you don't have group members yet. If, for some reason, a host can't send IGMP Group Membership Report (could be a BUG!) in response to the router's General Query, this command makes the router to join the group and send (S,G) or (*,G) joins to its upstream neighbors to maintain the paths for the group until the host's BUG get fixed. Another case, this command is sometimes used as a debugging method, to make the router reply to the group Ping. For instance, when the router joins the group, you can ping the group and makes the router reply. (Since it is a member)
Therefore, you do not need this command to force the host to join the group. As mentioned by the above users, the host will join automatically (depending on the settings in the multicast application itself).
If the goal is to put traffic out of an interface without sending it to the cpu, then "ip igmp static-group" is a better choice than "join-group". And for static-group command, you can use a class-map to summarize groups. This example will join 51 groups.
Thank you Guys. The reason I put the join-group on the router interface was the reciever was not sending IGMP join-group properly. Now the reciever is sending joing-group properly and took out all IGMP join-group confs from the router interface and it works.......Once again thank you all for your comments!
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...