Static Multicast Routes and Group Memberships
Problem
You want to override the dynamic multicast routing and group membership with static entries.
Solution
By default, PIM will use the same dynamic routing table learned by the unicast routing protocol. However, in some cases you don’t want to use these routes. For example, you might have to send multicast traffic through a tunnel to bypass a section of network that doesn’t support multicast routing. In this case, the unicast routing table is clearly the wrong path for multicast traffic. So you need to specify a different route for multicast traffic to use:
Router1#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router1(config)#ip multicast-routingRouter1(config)#ip mrouteRouter1(config)#192.168.15.0 255.255.255.0 192.168.98.6interface Tunnel0Router1(config-if)#ip addressRouter1(config-if)#192.168.98.5 255.255.255.252ip pim sparse-dense-modeRouter1(config-if)#tunnel mode gre ipRouter1(config-if)#endRouter1#
You can specify a static IGMP join to ensure that the router always thinks that there are group members on an interface:
Router1#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router1(config)#ip multicast-routingRouter1(config)#interface FastEthernet0/0Router1(config-if)#ip pim sparse-dense-modeRouter1(config-if)#ip igmp join-groupRouter1(config-if)#239.5.5.55endRouter1#
Discussion
The static mroute command is used only to describe the Reverse Path Forwarding ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access