On Switch C, configure a static multicast route to the source and specify Switch A as the RPF
5.
neighbor.
[SwitchC] ip rpf-route-static 50.1.1.0 24 50.1.1.1
Verifying the configuration
# Send an IGMP report from Receiver to join multicast group 225.1.1.1. (Details not shown.)
# Send multicast data from Source to multicast group 225.1.1.1. (Details not shown.)
# Display PIM routing entries on Switch C.
[SwitchC] display pim routing-table
Total 1 (*, G) entry; 1 (S, G) entry
(*, 225.1.1.1)
Protocol: pim-dm, Flag: WC
UpTime: 00:04:25
Upstream interface: NULL
Upstream neighbor: NULL
RPF prime neighbor: NULL
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface200
(10.1.1.100, 225.1.1.1)
Protocol: pim-dm, Flag: ACT
UpTime: 00:06:14
Upstream interface: Tunnel1
Upstream neighbor: 50.1.1.1
RPF prime neighbor: 50.1.1.1
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface200
The output shows that Switch A is the RPF neighbor of Switch C and the multicast data from Switch
A is delivered over the GRE tunnel to Switch C.
Troubleshooting multicast routing and forwarding
Static multicast route failure
Symptom
No dynamic routing protocol is enabled on the routers, and the physical status and link layer status of
interfaces are both up, but the static multicast route fails.
Solution
To resolve the problem:
Use the display multicast routing-table static command to display information about static
1.
multicast routes. Verify that the static multicast route has been correctly configured and that the
route entry exists in the static multicast routing table.
Protocol: igmp, UpTime: 00:04:25, Expires: -
Protocol: pim-dm, UpTime: 00:04:25, Expires: -
73