H3C Technologies H3C SecPath F1000-E - Manual (Page 688)

663
Import policy: none
Export policy: none
Information about SA-Requests:
Policy to accept SA-Request messages: none
Sending SA-Requests status: disable
Minimum TTL to forward SA with encapsulated data: 0
SAs learned from this peer: 0, SA-cache maximum for the peer: none
Input queue size: 0, Output queue size: 0
Counters for MSDP message:
Count of RPF check failure: 0
Incoming/outgoing SA messages: 0/0
Incoming/outgoing SA requests: 0/0
Incoming/outgoing SA responses: 0/0
Incoming/outgoing data packets: 0/0
Inter-AS multicast configuration by leveraging static RPF peers
Network requirements
As shown in Figure 350 , the network has two OSPF ASs: AS 100 and AS 200. BGP runs between the
two ASs.
PIM-SM 1 belongs to AS 100, and PIM-SM 2 and PIM-SM 3 belong to AS 200. Each PIM-SM domain
has at least one multicast source or receiver.
Configure Loopback 0 as the C-BSR and C-RP of the related PIM-SM domain on SecPath A, SecPath B
and SecPath C.
According to the RPF principle, the routers can receive SA messages that pass the filtering policy from its
static RPF peers. To share multicast source information among PIM-SM domains without changing the
unicast topology structure, configure MSDP peering relationships for the RPs of the PIM-SM domains and
configure static RPF peering relationships for the MSDP peers to share multicast source information
among the PIM-SM domains.