Interaction of EVPN-VXLAN and EVPN-MPLS with existing VPLS features

When enabling existing VPLS features in an EVPN-VXLAN or an EVPN-MPLS enabled service, the following must be considered:

• EVPN-VXLAN services are not supported on I-VPLS/B-VPLS. VXLAN cannot be enabled on those services. EVPN-MPLS is only supported in regular VPLS and B-VPLS. Other VPLS types, such as m-vpls, are not supported with either EVPN-VXLAN or EVPN-MPLS VPLS etree services are supported with EVPN-MPLS.

• In general, no router-generated control packets are sent to the EVPN destination bindings, except for ARP, VRRP, ping, BFD and Eth-CFM for EVPN-VXLAN, and proxy-ARP/proxy-ND confirm messages and Eth-CFM for EVPN-MPLS.

• The following rules apply to xSTP and M-VPLS services:

  • xSTP can be configured in BGP-EVPN services. BPDUs are not sent over the EVPN bindings.

  • bgp-evpn is blocked in m-vpls services; however, a different m-vpls service can manage a SAP or spoke SDP in a bgp-evpn-enabled service.

• In bgp-evpn enabled VPLS services, mac-move can be used in SAPs/SDP bindings; however, the MACs being learned through BGP-EVPN are considered.

  Note: The MAC duplication already provides a protection against mac-moves between EVPN and SAPs/SDP bindings.

• disable-learning and other fdb-related tools only work for data plane learned MAC addresses.

• mac-protect cannot be used in conjunction with EVPN.

  Note: EVPN provides its own protection mechanism for static MAC addresses.

• MAC OAM tools are not supported for bgp-evpn services, that is: mac-ping, mac-trace, mac-populate, mac-purge, and cpe-ping.

• EVPN multihoming and BGP-MH can be enabled in the same VPLS service, as long as they are not enabled in the same SAP-SDP or spoke SDP. There is no limitation on the number of BGP-MH sites supported per EVPN-MPLS service.

  Note: The number of BGP-MH sites per EVPN-VXLAN service is limited to 1.

• SAPs/SDP bindings that belong to a specified ES but are configured on non-BGP-EVPN-MPLS-enabled VPLS or Epipe services are kept down with the StandByForMHProtocol flag.

• CPE-ping is not supported on EVPN services but it is in PBB-EVPN services (including I-VPLS and PBB-Epipe). CPE-ping packets are not sent over EVPN destinations. CPE-ping only works on local active SAP or SDP bindings in I-VPLS and PBB-Epipe services.

• Other commands not supported in conjunction with bgp-evpn are:

  • Subscriber management commands under service, SAP, and SDP binding interfaces

  • BPDU translation

  • L2PT termination

  • MAC-pinning

• Other commands not supported in conjunction with bgp-evpn mpls are:

  • VSD-domains

  • SPB configuration and attributes