Operation Manual – Multicast ProtocolH3C S3610&S5510 Series Ethernet Switches Chapter 7 MSDP Configuration7-24[SwitchD-msdp] peer 1.1.1.1 connect-interface loopback 0[SwitchD-msdp] quitYou can use the display msdp brief command to view the brief information of MSDPpeering relationships between the switches.# View the brief MSDP peer information on Switch C.[SwitchC] display msdp briefMSDP Peer Brief InformationConfigured Up Listen Connect Shutdown Down1 1 0 0 0 0Peer's Address State Up/Down time AS SA Count Reset Count2.2.2.2 Up 00:10:17 ? 0 0# View the brief MSDP peer information on Router D.[SwitchD] display msdp briefMSDP Peer Brief InformationConfigured Up Listen Connect Shutdown Down1 1 0 0 0 0Peer's Address State Up/Down time AS SA Count Reset Count1.1.1.1 Up 00:10:18 ? 0 07.7.3 Static RPF Peer Configuration ExampleI. Network requirementsz Two ISPs maintains their ASs, AS 100 and AS 200 respectively. OSPF is runningwithin each AS, and BGP is running between the two ASs.z PIM-SM1 belongs to AS 100, while PIM-SM2 and PIM-SM3 belong to AS 200.z Both PIM-SM domains are single-BSR-managed domains, each having 0 or 1multicast source and multiple receivers. OSPF runs within each domain to provideunicast routes.z PIM-SM2 and PIM-SM3 are both PIM stub domains, and BGP or MBGP is notrequired between these two domains and PIM-SM1. Instead, static RPF peers areconfigured to avoid RPF check on SA messages.z The respective loopback interfaces of Switch C, Switch D and Switch F areconfigured as the C-BSR and C-RP of the respective PIM-SM domains.z The static RPF peers of Switch C are Switch D and Switch F, while Switch C is theonly RPF peer of Switch D and Switch F. Any switch can receive the SA messagessent by its static RPF peer(s) and permitted by the corresponding filtering policy.
