Inter-As Multicast Configuration By Leveraging Static Rpf Peers - HP FlexFabric 5950 series Configuration Manual

Import policy: None
Export policy: None
Information about SA-Requests:
Policy to accept SA-Requests: 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: 4294967295
Input queue size: 0, Output queue size: 0
Counters for MSDP messages:
RPF check failure: 0
Incoming/outgoing SA: 0/0
Incoming/outgoing SA-Request: 0/0
Incoming/outgoing SA-Response: 0/0
Incoming/outgoing Keepalive: 867/867
Incoming/outgoing Notification: 0/0
Incoming/outgoing Traceroutes in progress: 0/0
Incoming/outgoing Traceroute reply: 0/0
Incoming/outgoing Unknown: 0/0
Incoming/outgoing data packet: 0/0
Inter-AS multicast configuration by leveraging static RPF
peers
Network requirements
As shown inFigure
•
The network has two ASs: AS 100 and AS 200. OSPF runs within each AS. 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 a minimum of one multicast source or receiver.
Configure the switches to meet the network requirements:
•
Configure Loopback 0 as the C-BSR and C-RP of the related PIM-SM domain on Switch A,
Switch D and Switch G.
•
According to the peer-RPF forwarding rule, the switches accept 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 the static RPF peering
relationships.
65:
189