Operation Manual – Multicast ProtocolH3C S3610&S5510 Series Ethernet Switches Chapter 6 PIM Configuration6-49(10.110.5.100, 232.1.1.1)Protocol: pim-ssm, Flag:UpTime: 00:13:25Upstream interface: Vlan-interface101Upstream neighbor: 192.168.1.2RPF prime neighbor: 192.168.1.2Downstream interface(s) information:Total number of downstreams: 11: Vlan-interface100Protocol: pim-ssm, UpTime: 00:13:25, Expires: -The information on Switch B and Switch C is similar to that on Switch A.# View the PIM multicast routing table information on Switch D.[SwitchD] display pim routing-tableVpn-instance: public netTotal 0 (*, G) entry; 1 (S, G) entry(10.110.5.100, 232.1.1.1)Protocol: pim-ssm, Flag:UpTime: 00:12:05Upstream interface: Vlan-interface300Upstream neighbor: 10.110.5.100RPF prime neighbor: 10.110.5.100Downstream interface(s) information:Total number of downstreams: 11: Vlan-interface105Protocol: pim, UpTime: 00:12:05, Expires: 00:03:256.8 Troubleshooting PIM Configuration6.8.1 Failure of Building a Multicast Distribution Tree CorrectlyI. SymptomNone of the routers in the network (including routers directly connected with multicastsources and receivers) has multicast forwarding entries. That is, a multicast distributiontree cannot be built correctly and clients cannot receive multicast data.II. Analysisz When PIM-DM runs on the entire network, multicast data is flooded from the firsthop router connected with the multicast source to the last hop router connectedwith the clients along the SPT. When the multicast data is flooded to a router, nomatter which router is, it creates (S, G) entries only if it has a route to the multicastsource. If the router does not have a route to the multicast source, or if PIM-DM is