H3C Technologies H3C SecPath F1000-E - Manual (Page 32)

18
# On Device C, configure a static multicast route and specify its RPF neighbor leading toward Source is
Tunnel 0 on Device A.
[DeviceC] ip rpf-route-static 10.1.1.0 24 50.1.1.1
Step6 Verify the configuration
Source sends multicast data to the multicast group 225.1.1.1 and Receiver can receive the multicast data
after joining the multicast group. You can view the PIM routing table information on the devices using the
display pim routing-table command. For example:
# View the PIM routing table information on Device C.
[DeviceC] display pim routing-table
VPN-Instance: public net
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: GigabitEthernet0/1
Protocol: igmp, UpTime: 00:04:25, Expires: never
(10.1.1.100, 225.1.1.1)
Protocol: pim-dm, Flag: ACT
UpTime: 00:06:14
Upstream interface: Tunnel0
Upstream neighbor: 50.1.1.1
RPF prime neighbor: 50.1.1.1
Downstream interface(s) information:
Total number of downstreams: 1
1: GigabitEthernet0/1
Protocol: pim-dm, UpTime: 00:04:25, Expires: never
As shown above, Device A is the RPF neighbor of Device C and the multicast data from Device A is
delivered over a GRE tunnel to Device C.
Troubleshooting Multicast Routing and Forwarding
Multicast Static 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 multicast static route fails.