VPLS and EVPN SRv6 seamless integration

EVPN and VPLS seamless integration (RFC 8560) is supported for SRv6 VPLS services, as in the case of VPLS services with EVPN-MPLS.

This seamless integration comprises the following aspects:

• SDP binds signaled by TLDP (manual, BGP-AD) or BGP can coexist in VPLS services where EVPN SRv6 is enabled.

  If an EVPN destination and an SDP binding to the same far end exist, the router brings down the SDP binding. The EVPN SRv6 destination far end is specified by the route’s next hop (shown as TEP Address in the show service id id segment-routing-v6 destinations command), and not the locator. The router allows the creation of the EVPN destination and the SDP binding to the same far end but the SDP binding is kept operationally down (with a flag indicating there is an EVPN route conflict):

  show service id 10 sdp 32765:4294967291 detail | match Flag 
  Flags              : EvpnRouteConflict
  

  In case of an SDP binding and EVPN endpoint to different far-end IPs on the same remote PE, both links are operationally up. This can happen if the SDP binding is terminated in an IPv6 address or IPv4 address different from the system address where the EVPN endpoint is terminated.

• The user can configure spoke SDPs and all the EVPN endpoints in the same split horizon group (SHG).

  The split-horizon-group command is added under the bgp-evpn>segment-routing-v6 context so that the EVPN SRv6 endpoints are added to a split-horizon-group.

  Note: the BGP EVPN SRv6 split horizon group must reference user-configured SHGs and not auto-created SHGs.

  If the split-horizon-group command for bgp-evpn>segment-routing-v6> context is not used, the default split horizon group (in which all the EVPN endpoints are) is still used, but it is not possible to reference it on SAP or spoke SDPs. User-configured split horizon groups can be configured within the service context. The same group-name can be associated to SAPs, spoke SDPs, pw-templates, pw-template-bindings and EVPN-SRv6 destinations. The bgp-evpn segment-routing-v6 split-horizon-group configuration is only allowed if the bgp-evpn> segment-routing-v6 is disabled. No changes are allowed when bgp-evpn> segment-routing-v6 is enabled.

• The advertisement of MACs learned on spoke SDPs or SAPs that are part of an EVPN split horizon group are disabled.

  When the SAPs, spoke SDPs, or both (manual or BGP-AD/VPLS discovered) are configured within the same split-horizon-group as the EVPN destinations, MAC addresses are still learned on them, but they are not advertised in EVPN.

  The previously mentioned is also true if proxy-ARP or ND is enabled and an IP-MAC pair is learned on a SAP or SDP binding that belongs to the EVPN split-horizon-group.