About Seamless Integration of EVPN (TRM) with MVPN (Draft Rosen)
Seamless integration of EVPN (TRM) with MVPN (draft rosen) enables packets to be handed off between a VXLAN network (TRM or TRM Multi-Site) and an MVPN network. To support this feature, VXLAN TRM and MVPN must be supported on a Cisco Nexus device node, the handoff node.
The handoff node is the PE for the MVPN network and the VTEP for the VXLAN network. It connects to the VXLAN, MVPN, and IP multicast networks, as shown in the following figure.
Sources and receivers can be in any of the three networks (VXLAN, MVPN, or IP multicast).
All multicast traffic (that is, the tenant traffic from the VXLAN, MVPN, or multicast network) is routed from one domain to another domain. The handoff node acts as the central node. It performs the necessary packet forwarding, encapsulation, and decapsulation to send the traffic to the respective receivers.
Supported RP Positions
The rendezvous point (RP) for the customer (overlay) network can be in any of the three networks (VXLAN, MVPN, or IP multicast).
RP Locations |
Description |
---|---|
RP in IP network |
|
RP internal to VXLAN fabric |
All VTEPs are RPs inside the VXLAN fabric. All MVPN PEs use the RP configured on the VXLAN fabric. |
RP on VXLAN MVPN handoff node |
The RP is the VXLAN MVPN handoff node. |
RP in MVPN network |
The RP is external to the VXLAN network. It's configured on one of the nodes in the MPLS cloud, other than the handoff node. |
RP Everywhere (PIM Anycast RP or MSDP-based Anycast RP) |
The Anycast RP can be configured on the VXLAN leaf. The RP set can be configured on the handoff node or any MVPN PE. |