• The VPWS service on PE1 requires the following three elements to be specified at configuration time:
• The VPN ID (EVI)
• The local AC identifier (AC1) that identifies the local end of the emulated service.
• The remote AC identifier (AC2) that identifies the remote end of the emulated service.
PE1 allocates a MPLS label per local AC for reachability.
• The VPWS service on PE2 is set in the same manner as PE1. The three same elements are required and
the service configuration must be symmetric.
PE2 allocates a MPLS label per local AC for reachability.
• PE1 advertise a single EVPN per EVI Ethernet AD route for each local endpoint (AC) to remote PEs
with the associated MPLS label.
PE2 performs the same task.
• On reception of EVPN per EVI EAD route from PE2, PE1 adds the entry to its local L2 RIB. PE1 knows
the path list to reach AC2, for example, next hop is PE2 IP address and MPLS label for AC2.
PE2 performs the same task.
Benefits of EVPN-VPWS
The following are the benefits of EVPN-VPWS:
• Scalability is achieved without signaling pseudowires.
• Ease of provisioning
• Pseudowires (PWs) are not used.
• Leverages BGP best path selection (optimal forwarding).
Prerequisites for EVPN-VPWS
• Ensure BGP is configured for EVPN SAFI.
• BGP session between PEs with 'address-family l2vpn evpn' to exchange EVPN routes.
Restrictions for EVPN-VPWS
• The VPN ID is unique per router.
L2VPN and Ethernet Services Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.3.x
99
Implementing Point to Point Layer 2 Services
Benefits of EVPN-VPWS
To Next Page
Loading...
Need help?
General
