Inter-As Multicast Configuration By Leveraging Static Rpf Peers - HP MSR2003 Configuration Manual

# Display detailed MSDP peer information on Router B.
[RouterB] display msdp peer-status
MSDP Peer 192.168.1.2; AS 200
Description:
Information about connection status:
State: Established
Up/down time: 00:15:47
Resets: 0
Connection interface: GigabitEthernet2/1/2 (192.168.1.1)
Received/sent messages: 16/16
Discarded input messages: 0
Discarded output messages: 0
Elapsed time since last connection or counters clear: 00:17:40
Mesh group peer joined: momo
Last disconnect reason: Hold timer expired with truncated message
Truncated packet: 5 bytes in buffer, type: 1, length: 20, without packet time: 75s
Information about (Source, Group)-based SA filtering policy:
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 in
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 at least one multicast source or receiver.
To meet the network requirements, perform the following tasks:
Figure 53:
156