3Com Switch 4800G 24-Port Configuration Manual page 690

690 C 48: MSDP C
HAPTER
Inter-AS Multicast
Configuration
Leveraging Static RPF
Peers
ONFIGURATION
Description:
Information about connection status:
State: Up
Up/down time: 00:15:47
Resets: 0
Connection interface: Vlan-interface101 (192.168.1.1)
Number of sent/received messages: 16/16
Number of discarded output messages: 0
Elapsed time since last connection or counters clear: 00:17:51
Information about (Source, Group)-based SA filtering policy:
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
Network requirements
There are two ASs in the network, AS 100 and AS 200 respectively. OSPF is
■
running within each AS, and BGP is running between the two ASs.
PIM-SM 1 belongs to AS 100, while PIM-SM 2 and PIM-SM 3 belong to AS
■
200.
Each PIM-SM domain has zero or one multicast source and receiver. OSPF runs
■
within each domain to provide unicast routes.
PIM-SM 2 and PIM-SM 3 are both stub domains, and BGP or MBGP is not
■
required between these two domains and PIM-SM 1. Instead, static RPF peers
are configured to avoid RPF check on SA messages.
It is required that the respective loopback 0 of Switch B, Switch C and Switch E
■
be configured as the C-BSR and C-RP of the respective PIM-SM domains.
It is required that Switch C and Switch E be configured as static RPF peers of
■
Switch B, and Switch B be configured as the only static RPF peer of Switch C
and Switch E, so that any switch can receive SA messages only from its static
RPF peer(s) and permitted by the corresponding filtering policy.