Configuring Mvpn Extranet Routing; Prerequisites For Mvpn Extranet Routing; Restrictions For Mvpn Extranet Routing - Cisco ASR 9000 Series Configuration Manual

Configuring MVPN Extranet Routing

Configuring MVPN Extranet Routing
To be able to import unicast routes from source VRFs to receiver VRFs, the import route targets of receiver
VRFs must match the export route targets of a source VRF. Also, all VRFs on the PEs where the extranet
source-receiver switchover takes place should be added to the BGP router configuration on those PEs.
Configuring MVPN extranet routing consists of these mandatory and optional tasks, which should be performed
in the sequence shown:
• "Configuring a Routing Policy" (required only if performing the following task)
For examples of an end-to-end configuration of each of the two available MVPN extranet topology solutions,
see Configuring MVPN Extranet Routing: Example, on page

Prerequisites for MVPN Extranet Routing

• PIM-SM and PIM-SSM are supported. You must configure the multicast group range in the source and
• Because only static RP configuration is currently supported for a given multicast group range, both
• In the IPv6 Connectivity over MVPN topology model, the data MDT encapsulation range should be
• Data MDT configuration is required on only the Source VRF and Source PE Router.

Restrictions for MVPN Extranet Routing

• PIM-DM and PIM-BIDIR are not supported.
• Cisco IOS XR Software software supports only IPv4 extranet multicast routing over IPv4 core multicast
• Any PE can be configured as an RP except a PE in the "Receiver VRF on the Source PE Router" model
• Cisco IOS XR Software currently supports only one encapsulation of VRF traffic on an extranet. This
Cisco ASR 9000 Series Aggregation Services Router Multicast Configuration Guide, Release 6.0.x
224
For information, see Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide.
receiver VRFs with a matching PIM mode.
source and receiver MVRFs must be configured with the same RP.
large enough to accommodate extranet streams without any aggregation. This prevents extranet traffic,
flowing to multiple VRFs, from being carried into only one data MDT.
routing.
where the extranet switchover occurs, and where the source VRF has no interfaces. This is because the
source VRF must have some physical interface to signal the data packets being received from the first
hop.
means that only one encapsulation interface (or MDT) is allowed in the outgoing forwarding interface
list of the multicast route. If, for a given stream, there are multiple receiver VRFs joining the same source
VRF, only the first receiver VRF receives traffic; other receiver VRF joins are discarded.
This limitation applies only to IPv6 Connectivity over MVPN topology model.
Note
Implementing Layer-3 Multicast Routing on Cisco IOS XR Software
276.