H3C Technologies H3C S7500E Series Switches - Manual (Page 106)

4-22
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 routers using the display pim routing-table command. For example:
# View the PIM routing table information on Switch C.
[SwitchC] 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: Vlan-interface200
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: Vlan-interface200
Protocol: pim-dm, UpTime: 00:04:25, Expires: never
As shown above, Switch A is the RPF neighbor of Switch C and the multicast data from Switch
A is delivered over a GRE tunnel to Switch C.
Troubleshooting Multicast Routing and Forwarding
Multicast Static Route Failure
Symptom
No dynamic routing protocol is enabled on the routers, and the physic status and link layer
status of interfaces are both up, but the multicast static route fails.
Analysis
z If the multicast static route is not configured or updated correctly to match the current
network conditions, the route entry and the configuration information of multicast static
routes do not exist in the multicast routing table.
z If a better route is found, the multicast static route may also fail.
Solution
1) In the configuration, you can use the display multicast routing-table static config
command to view the detailed configuration information of multicast static routes to verify
that the multicast static route has been correctly configured and the route entry exists.