VPN-A and VPN-B and forwards the packets. After receiving the packets from this source, PE2 and PE3
decapsulate and forward the packets to the respective MVRFs.
Figure 8: Receiver MVRF at the Source PE Router Receiver
For more information, see also Configuring MVPN Extranet Routing, on page 83 and Configuring MVPN
Extranet Routing: Example, on page 134.
RPF Policies in an Extranet
RPF policies can be configured in receiver VRFs to bypass RPF lookup in receiver VRFs and statically
propagate join states to specified source VRF. Such policies can be configured to pick a source VRF based
on either multicast group range, multicast source range, or RP address.
For more information about configuration of RFP policies in extranets, see Configuring RPL Policies in
Receiver VRFs to Propagate Joins to a Source VRF: Example, on page 136 and Configuring RPL Policies in
Receiver VRFs on Source PE Routers to Propagate Joins to a Source VRF: Example, on page 139.
Multicast VPN Hub and Spoke Topology
Hub and spoke topology is an interconnection of two categories of sites — Hub sites and Spoke sites. The
routes advertised across sites are such that they achieve connectivity in a restricted hub and spoke fashion. A
spoke can interact only with its hub because the rest of the network (that is, other hubs and spokes) appears
hidden behind the hub.
The hub and spoke topology can be adopted for these reasons:
•
Spoke sites of a VPN customer receives all their traffic from a central (or Hub) site hosting services
such as server farms.
•
Spoke sites of a VPN customer requires all the connectivity between its spoke sites through a central
site. This means that the hub site becomes a transit point for interspoke connectivity.
Cisco ASR 9000 Series Aggregation Services Router Multicast Configuration Guide, Release 5.1.x
24
Implementing Layer-3 Multicast Routing on Cisco IOS XR Software
Multicast VPN Hub and Spoke Topology
To Next Page
Loading...
