Configure Virtual Ethernet Segment (Ves); Configure Access Pw - Cisco ASR 9000 Series Configuration Manuallines

L2vpn and ethernet services configuration guide
Hide thumbs Also See for ASR 9000 Series:
Table of Contents

Advertisement

Configure Virtual Ethernet Segment (vES)

blocks the traffic on that particular Ethernet segment. Both DCI1 and DCI2 can do the DF election. DCI1 and
DCI2 perform DF election after they discover each other. Either one of them can be a DF and other a non-DF.
The traffic is forwarded through the DF. The non-DF path is in stand-by mode. DF election is used to prevent
traffic loop. DCI1 or DCI2 sends the traffic to PE3.
Interoperability Between VxLAN and vES
When all-active VxLAN and single-active vES are integrated together, some traffic may take non-optimal
path. Consider a traffic flow from CE2 to PE1. VxLAN is in all-active mode and vES is in single active mode.
CE2 sends the traffic to ToR1, and ToR1 sends the traffic to DCI1 and DCI2. Both DCI1 and DCI2 can receive
the traffic from VxLAN because it is in all-active mode. But, either DCI1 or DCI2 (which is a DF) can forward
the traffic through vES. If DCI1 is a non-DF, the traffic is sent from DCI2 to PE1.
Limitations
The vES feature is supported with the following limitations:
• Core isolation is not supported for vES. MPLS core network must be always up and vES redundant peers
• Only targeted LDP pseudowire is supported.
• Interoperability between VxLAN and classic VFI (legacy L2VPN) is not supported.
• Backup PW is not supported with vES.
• PW-status must be supported and enabled on both sides of PW.
• Up to 400 unique RTs are supported for each ESI. However, multiple ESI can share same the RT. Hence,
Configure Virtual Ethernet Segment (vES)
The following sections describe how to configure access PW and access VFI.

Configure Access PW

This section describes how you can configure access PW.
/* Configure DCI1 */
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# l2vpn
RP/0/RSP0/CPU0:router(config-l2vpn)# bridge group bg1
RP/0/RSP0/CPU0:router(config-l2vpn-bg)# bridge-domain bd1
RP/0/RSP0/CPU0:router(config-bg-bd)# neighbor 70.70.70.70 pw-id 17300001
RP/0/RSP0/CPU0:router(config-bg-bd-pw)# evi 1
RP/0/RSP0/CPU0:router(config-bg-bd-pw-evi)# member vni 10001
/* Configure EVPN */
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# evpn
RP/0/RSP0/CPU0:router(config-evpn)# virtual neighbor 70.70.70.70 pw-id 17300001
RP/0/RSP0/CPU0:router(config-evpn-ac-pw)# ethernet-segment
RP/0/RSP0/CPU0:router(config-evpn-ac-pw-es)# identifier type 0 12.12.00.00.00.01.00.00.03
RP/0/RSP0/CPU0:router(config-evpn-ac-pw-es)# bgp route-target 1212.8888.0003
RP/0/RSP0/CPU0:router(config-evpn-ac-pw-es)# exit
L2VPN and Ethernet Services Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.3.x
542
must be able to exchange type 4 routes while vES is in operation.
this does not restrict the number of vES.
EVPN Features

Advertisement

Table of Contents
loading

Table of Contents