Configure Evpn Vpws On Demand Next Hop With Sr-Te; Topology - Cisco ASR 9000 Series Configuration Manuallines

L2VPN Services over Segment Routing for Traffic Engineering Policy
Restrictions
• Maximum number of auto-provisioned TE policies is 1000.
• L2VPN services over PWHE with EVPN VPWS On-Demand Next Hop with SR-TE is not supported.
• PWHE over SR-TE with ECMP paths is not supported.
• EVPN VPWS SR policy is not supported on EVPN VPWS dual homing.

Configure EVPN VPWS On Demand Next Hop with SR-TE

Perform the following steps to configure EVPN VPWS On Demand Next Hop with SR-TE. The following
figure is used as a reference to explain the configuration steps:
• Configure Prefix-SID in ISIS
• Configure SR-TE
• Configure PCE and PCC
• Configure SR color
• Configure EVPN route policy
• Configure BGP
• Configure EVPN VPWS
• Configure VPWS with pseudowire headend

Topology

Consider a topology where EVPN VPWS is configured on PE1 and PE2. Traffic is sent from PE1 to PE2
using SR-TE in the core. The PCE, which is configured on the P router, calculates the best path from PE1 to
PE2. Path computation client (PCC) is configured on PE1 and PE2.
EVPN validates if the route is for a single home next hop, otherwise it issues an error message about a
dangling SR-TE policy, and continue to setup EVPN-VPWS without it. EVPN relies on ESI value being
zero to determine if this is a single home or not. If the AC is a Bundle-Ether interface running LACP
then you need to manually configure the ESI value to zero to overwrite the auto-sense ESI as EVPN
VPWS multihoming is not supported.
To disable EVPN dual homing, configure bundle-Ether AC with ESI value set to zero.
evpn
interface Bundle-Ether12
ethernet-segment
identifier type 0 00.00.00.00.00.00.00.00.00
/* Or globally */
evpn
ethernet-segment type 1 auto-generation-disable
L2VPN and Ethernet Services Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.3.x
Configure EVPN VPWS On Demand Next Hop with SR-TE
651