EVPN-MPLS with existing VPLS features

When enabling existing VPLS features in an EVPN-MPLS-enabled service, the following considerations apply:

• EVPN-MPLS is only supported in regular VPLS. Other VPLS types, such as m-vpls, are not supported.

• In general, no router-generated control packets are sent to the EVPN destination bindings, except for proxy-ARP/proxy-ND confirm messages for EVPN-MPLS.

• For xSTP and M-VPLS services, the following applies:

  • 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.

• For BGP-EVPN-enabled VPLS services, mac-move can be used in SAPs/SDP-bindings; however, MACs learned through BGP-EVPN are not considered.

  Note:

  MAC duplication provides protection against MAC moves between EVPN and SAPs/SDP-bindings.

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

• MAC OAM tools (mac-ping, mac-trace, mac-populate, mac-purge, and cpe-ping) are not supported for BGP-EVPN services.

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

• CPE ping is not supported on EVPN services.

• Other features not supported in conjunction with BGP-EVPN are:

  • endpoints and attributes

  • BPDU translation

  • L2PT termination

  • MAC-pinning

  • IGMP snooping in VPLS services when BGP-EVPN MPLS is enabled (in the service)

  • DHCP snooping

  • ETH-CFM (MEPs, vMEPs, MIPs)

  • allow-ip-int-bind (R-VPLS)