Information Technology Reference
In-Depth Information
There is no need for (m)BGP, because there is a single MSDP peer, and no RPF checking
is performed on the MSDP SA messages. The provider must inject the customer's networks
into mBGP to ensure that RPF checking will work. The provider does not need to perform
peer-RPF on the SA messages received from the customer, because the customer is the
originating RP.
Multiple Links, Same Upstream Provider
As shown in Figure 11-29, this scenario illustrates a customer who has his own RP and
multiple links to the same upstream ISP. The customer wants to use only one of the links
for multicast.
Figure 11-29
Multiple Links, Same Upstream Customer Connection
ISP Network
Customer
Network
RP
MSDP Peer
The customer configuration is shown in Example 11-21.
Example 11-21
Customer Router Configuration
hostname Customer
!
ip multicast-routing
!
interface Loopback0
ip address 10.1.0.1 255.255.255.255
!
interface Serial2/0
ip address 10.1.1.1 255.255.255.252
!
interface Serial3/0
ip address 10.1.2.1 255.255.255.252
ip pim sparse-mode
!
router bgp 65000
no synchronization
bgp log-neighbor-changes
continues
