Configuring Mvpn; Forcing Ingress Multicast Replication Mode (Optional) - Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual

Configuring MVPN

•
•
•
•
•
•
•
Configuring MVPN
These sections describe how to configure MVPN:
•
•
•
•
These configuration tasks assume that BGP is already configured and operational on all routers that are
Note
sending or receiving the multicast traffic. In addition, BGP extended communities must be enabled
(using the neighbor send-community both or neighbor send-community extended command) to
support the use of MDTs in the network.

Forcing Ingress Multicast Replication Mode (Optional)

The MVPN feature supports only ingress multicast replication mode. If the switch is currently
configured for egress replication, it is forced into ingress replication when the first MVRF is configured.
This change in replication mode automatically purges all forwarding entries in the hardware, temporarily
forcing the switch into software switching until the table entries can be rebuilt.
To avoid disrupting customer traffic, we recommend verifying that the switch is already in ingress
multicast replication mode before configuring any MVRFs.
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
22-8
Each MVRF that is configured with a default MDT uses three hidden VLANs (one each for
encapsulation, decapsulation, and interface), in addition to external, user-visible VLANs. This
means that an absolute maximum of 1,000 MVRFs are supported on each router. (MVRFs without
a configured MDT still use one internal VLAN, so unused MVRFs should be deleted to conserve
VLAN allocation.)
Because MVPN uses MPLS, MVPN supports only the RPR redundancy mode.
If your MPLS VPN network already contains a network of VRFs, you do not need to delete them or
recreate them to be able to support MVRF traffic. Instead, configure the mdt default and mdt data
commands, as listed in the following procedure, to enable multicast traffic over the VRF.
BGP should be already configured and operational on all routers that are sending or receiving
multicast traffic. In addition, BGP extended communities must be enabled (using the neighbor
send-community both or neighbor send-community extended command) to support the use of
MDTs in the network.
The same MVRF must be configured on each PE router that is to support a particular VPN
connection.
Each PE router that supports a particular MVRF must be configured with the same mdt default
command.
The switch supports only ingress replication when MVPN is configured. If a switch is currently
configured for egress replication, it is forced into ingress replication when the first MVRF is
configured. If a switch is currently configured for egress replication, we recommend performing this
task only during scheduled maintenance periods, so that traffic disruption can be kept to a minimum.
Forcing Ingress Multicast Replication Mode (Optional), page 22-8
Configuring a Multicast VPN Routing and Forwarding Instance, page 22-9
Configuring Multicast VRF Routing, page 22-15
Configuring Interfaces for Multicast Routing to Support MVPN, page 22-20
Chapter 22 Configuring IPv4 Multicast VPN Support
OL-11439-03