5-17MSDP Peer Brief InformationPeer's Address State Up/Down time AS SA Count Reset Count1.1.1.1 Up 00:50:22 ? 2 0When Source 1 (10.110.5.100/24) sends multicast data to multicast group G (225.1.1.1), Receiver 1joins multicast group G. By comparing the PIM routing information displayed on Switch B with thatdisplayed on Switch D, you can see that Switch B now acts as the RP for Source 1 and Receiver 1.Source 1 registers with Switch B and Receiver 1 sends a join message to Switch B.# View the PIM routing information on Switch B.[Switch B] display pim routing-tablePIM-SM Routing TableTotal 1 (S,G) entry, 1 (*,G) entry, 0 (*,*,RP) entry(*, 225.1.1.1), RP 10.1.1.1Protocol 0x20: PIMSM, Flag 0x2003: RPT WC NULL_IIFUptime: 00:00:13, never timeoutUpstream interface: Null, RPF neighbor: 0.0.0.0Downstream interface list:Vlan-interface100, Protocol 0x1: IGMP, never timeout(10.110.5.100, 225.1.1.1)Protocol 0x20: PIMSM, Flag 0x4: SPTUptime: 00:03:08, Timeout in 206 secUpstream interface: Vlan-interface103, RPF neighbor: NULLDownstream interface list:Vlan-interface100, Protocol 0x1: IGMP, never timeoutMatched 1 (S,G) entry, 1 (*,G) entry, 0 (*,*,RP) entry# View the PIM routing information on Switch D.[SwitchD] display pim routing-tablePIM-SM Routing TableTotal 0 (S,G) entry, 0 (*,G) entry, 0 (*,*,RP) entryMatched 0 (S,G) entry, 0 (*,G) entry, 0 (*,*,RP) entryTroubleshooting MSDP ConfigurationMSDP Peer Always in the Down StateSymptomAn MSDP peer is configured, but it is always in the down state.AnalysisAn MSDP peer relationship between the locally configured connect-interface interface address andthe configured peer address is based on a TCP connection. If the address of local connect-interfaceinterface is inconsistent with the peer address configured on the peer router, no TCP connection can beestablished. If there is no route between the two peers, no TCP connection can be established.
