Configuring EVPN VPLS over SRv6 BE

Procedure

1. Establish a BGP EVPN peer relationship between PEs.
   1. Run system-view

      The system view is displayed.

   2. Run bgp { as-number-plain | as-number-dot }

      The BGP view is displayed.

   3. (Optional) Run router-id ipv4-address

      A BGP router ID is configured.

   4. Run peer ipv6-address as-number { as-number-plain | as-number-dot }

      The remote PE is configured as a peer.

   5. Run peer ipv6-address connect-interface loopback interface-number

      The interface on which a TCP connection to the specified BGP peer is established is specified.

   6. Run l2vpn-family evpn

      The BGP EVPN address family view is displayed.

   7. Run peer ipv6-address enable

      The device is enabled to exchange EVPN routes with the specified peer.

   8. Run peer { ipv6-address | group-name } advertise encap-type srv6 [ advertise-srv6-locator ]

      The device is enabled to send EVPN routes carrying SRv6-encapsulated attributes to the specified peer or peer group.

      In a scenario where BFD is used to check locator reachability, after locator routes are summarized by a P device between local and remote PEs, the remote PE can learn only the summary locator route, not the locator on the local PE. This leads to a BFD failure. To address this issue, configure the advertise-srv6-locator parameter in the command to allow the local PE to carry locator length information in the EVPN route advertised to the remote PE. In this way, after receiving the EVPN route, the remote PE can calculate the locator on the local PE, enabling BFD to take effect.

   9. Run quit

      Exit the BGP EVPN address family view.

   10. Run quit

       Exit the BGP view.

   11. Run commit

       The configuration is committed.

2. Configure basic SRv6 functions.
   1. (Optional) Run evpn srv6 next-header-field { 59 | 143 }

      A value is set for the Next Header field in an SRv6 extension header.

      If the value is 59 in earlier versions, you can perform this step to change the value to 59 to ensure compatibility with the earlier versions.

   2. Run segment-routing ipv6

      SRv6 is enabled, and the SRv6 view is displayed.

   3. Run encapsulation source-address ipv6-address [ ip-ttl ttl-value ]

      A source address is specified for SRv6 EVPN encapsulation.

   4. Run locator locator-name [ ipv6-prefix ipv6-address prefix-length [ static static-length | args args-length ] ^* ]

      An SRv6 locator is configured.

   5. (Optional) Run opcode func-opcode end-dt2m bridge-domain bd-id

      A static End.DT2M SID operation code (opcode) is configured.

      Perform this step if a static locator is configured using the static static-length parameter. End.DT2M SIDs are used for BUM traffic forwarding through VPLS.

   6. (Optional) Run opcode func-opcode { end-dt2u | end-dt2ul } bridge-domain bd-id

      Static End.DT2U and End.DT2UL SID opcodes are configured.

      Perform this step if a static locator is configured using the static static-length parameter. End.DT2U SIDs are used for the forwarding of known unicast traffic through VPLS. In dual-homing scenarios, an End.DT2UL SID opcode needs to be specified for the bypass path to prevent traffic loops between PEs.

   7. Run quit

      Exit the SRv6 locator view.

   8. Run quit

      Exit the SRv6 view.

3. Enable IS-IS SRv6.
   1. Run isis [ process-id ]

      The IS-IS view is displayed.

   2. Run ipv6 enable topology ipv6

      The IPv6 capability is enabled for the IS-IS process in the IPv6 topology.

   3. Run segment-routing ipv6 locator locator-name [ auto-sid-disable ]

      IS-IS SRv6 is enabled.

      In this command, the value of locator-name must be the same as that configured using locator locator-name [ ipv6-prefix ipv6-address prefix-length [ static static-length | args args-length ] ^* ]. If a separate locator is configured for each of BUM traffic and known unicast traffic of EVPN VPLS services, you need to run this command once for each locator for IS-IS to advertise them both.

   4. Run quit

      Exit the IS-IS view.

4. Configure EVPN routes to carry SIDs and recurse to SRv6 BE paths based on the SIDs.
   1. Run evpn vpn-instance vpn-instance-name bd-mode

      The view of the EVPN instance that works in BD mode is displayed.

   2. Run segment-routing ipv6 locator locator-name [ unicast-locator unicast-locator-name ]

      The device is enabled to add SIDs to EVPN routes to be advertised.

      For the command:

      • locator-name must be set to an End.DT2M SID, with the args parameter specified. unicast-locator-name must be set to an End.DT2U or End.DT2UL SID, without having the args parameter specified. If the locator-name and unicast-locator-name parameters are both required, you need to run the locator locator-name [ ipv6-prefix ipv6-address prefix-length [ static static-length | args args-length ] ^* ] command to create two corresponding locators before setting the two parameters.

      • In EVPN VPLS dual-homing scenarios, the args parameter is used to stitch ESI labels for End.DT2M SIDs only, which causes a waste of End.DT2U SIDs. In this case, you can separately configure a locator for End.DT2U SIDs and another locator for End.DT2M SIDs. The former locator does not require the args parameter to be specified. The two locators can then be bound to the same EVPN instance to conserve SIDs.

      • If static SIDs are configured for the locator specified using locator-name or unicast-locator-name, use the static SIDs. Otherwise, use dynamically allocated SIDs.

   3. Run segment-routing ipv6 best-effort

      The device is enabled to perform route recursion to SRv6 BE paths based on the SIDs carried by routes.

   4. Run commit

      The configuration is committed.