Operation Manual – MulticastH3C S7500E Series Ethernet Switches Chapter 6 MSDP Configuration6-23State: UpUp/down time: 00:15:47Resets: 0Connection interface: Vlan-interface101 (192.168.1.1)Number of sent/received messages: 16/16Number of discarded output messages: 0Elapsed time since last connection or counters clear: 00:17:51Information about (Source, Group)-based SA filtering policy:Import policy: noneExport policy: noneInformation about SA-Requests:Policy to accept SA-Request messages: noneSending SA-Requests status: disableMinimum TTL to forward SA with encapsulated data: 0SAs learned from this peer: 0, SA-cache maximum for the peer: noneInput queue size: 0, Output queue size: 0Counters for MSDP message:Count of RPF check failure: 0Incoming/outgoing SA messages: 0/0Incoming/outgoing SA requests: 0/0Incoming/outgoing SA responses: 0/0Incoming/outgoing data packets: 0/06.7.2 Inter-AS Multicast Configuration Leveraging Static RPF PeersI. Network requirementsz There are two ASs in the network, AS 100 and AS 200 respectively. OSPF isrunning within each AS, and BGP is running between the two ASs.z PIM-SM 1 belongs to AS 100, while PIM-SM 2 and PIM-SM 3 belong to AS 200.z Each PIM-SM domain has zero or one multicast source and receiver. OSPF runswithin each domain to provide unicast routes.z PIM-SM 2 and PIM-SM 3 are both stub domains, and BGP or MBGP is notrequired between these two domains and PIM-SM 1. Instead, static RPF peers areconfigured to avoid RPF check on SA messages.z It is required that the respective loopback 0 of Switch B, Switch C and Switch E beconfigured as the C-BSR and C-RP of the respective PIM-SM domains.z It is required that Switch C and Switch E be configured as static RPF peers ofSwitch B, and Switch B be configured as the only static RPF peer of Switch C andSwitch E, so that any switch can receive SA messages only from its static RPFpeer(s) and permitted by the corresponding filtering policy.
