A Layer 2 VPN (L2VPN) allows service providers to offer transparent Layer 2 connectivity between customer sites over an MPLS network. It essentially extends a customer's Layer 2 domain across geographically dispersed locations, enabling Ethernet or Frame Relay connections without the customer being aware of the provider's infrastructure.
How LDP Works:
Customer Edge (CE) Devices:
Provider Edge (PE) Routers:
P Routers:
End-to-End Connectivity:
Enterprise Layer 2 Connectivity:
Cloud Services:
Carrier Ethernet Services:
Data Center Interconnect (DCI):
Below is a basic configuration for setting up a VPLS in Junos:
Define the VPLS instance and its type:
set routing-instances VPLS1 instance-type vpls
Associate the customer-facing interface with the VPLS instance:
set routing-instances VPLS1 interface ge-0/0/1.0
Set a unique site identifier for the VPLS instance:
set routing-instances VPLS1 vpls-options site-identifier 1
Enable LDP to establish pseudowires for VPLS:
set protocols ldp interface ge-0/0/0.0
Plan Site Identifiers Carefully:
Monitor Pseudowire Status:
show ldp neighbor and show vpls connections to verify the health of pseudowires.Consider EVPN for Scalability:
Test in a Lab Environment:
Seamless Connectivity:
Bandwidth Efficiency:
Support for Multiple Protocols:
Transparency:
Layer 2 VPNs are a powerful solution for providing seamless Layer 2 connectivity over an MPLS backbone. With technologies like VPLS and EVPN, organizations can extend their networks, connect data centers, and support cloud services efficiently. Understanding how LDP signaling, pseudowires, and VPLS instances work is critical for deploying Layer 2 VPNs effectively.
In VPLS, to prevent Layer 2 loops, the split-horizon rule is enabled by default.
A PE router does not forward frames received from one PE to another PE on the same VPLS instance.
This means:
If PE1 receives a broadcast frame from PE2 on a VPLS pseudowire, it does not forward that frame to PE3.
Only local CE-connected interfaces will receive the traffic.
Prevents MAC learning loops and broadcast storms in the virtual LAN domain.
Exam questions often ask about why traffic is not being forwarded between PEs — split-horizon is a common answer.
Both VPLS and EVPN create Layer 2 VPN services, but use different control-plane mechanisms:
| Technology | Control Plane Signaling | Scalability | Typical Use Case |
|---|---|---|---|
| VPLS | LDP (Label Distribution Protocol) | Medium | Simple L2 VPN extensions |
| EVPN | BGP (Multiprotocol BGP with EVPN AFI/SAFI) | High | Data center, large-scale, multi-homed |
“LDP is used for VPLS in the control plane; BGP is used in EVPN for better scalability, multi-homing, and control-plane learning.”
This is frequently tested with “Which protocol provides signaling for EVPN/VPLS?” or “Which method supports better route scalability?”
MAC addresses are learned dynamically in the data plane, via:
Source MAC inspection
Flooding of unknown unicast/broadcast traffic
“VPLS learns MAC addresses via flooding and inspection (data plane), while EVPN uses BGP updates (control plane).”
This is a core differentiator between the technologies and is often tested directly or indirectly in scenario-based or true/false questions.
EVPN uses several specialized BGP route types, known as EVPN NLRI (Network Layer Reachability Information) types.
Advertises a MAC address, optionally along with an IP address.
Used for:
MAC learning and distribution across PEs
Supporting integrated routing and bridging (IRB)
Route Type 2 – MAC/IP Advertisement
Fields include:
- MAC Address
- Optional IPv4/IPv6 address
- Ethernet Segment Identifier (ESI)
Type 1: Ethernet Auto-Discovery (ESI, multihoming)
Type 3: Inclusive Multicast Ethernet Tag (BUM replication)
Type 5: IP Prefix route (for L3 EVPN)
“EVPN uses Type-2 BGP routes to advertise MAC and optional IP addresses in the control plane, allowing fast convergence and multi-homing support.”
Even if configuration isn’t tested, recognizing route types is important for log output interpretation and theoretical questions.
| Feature | VPLS | EVPN |
|---|---|---|
| Signaling Protocol | LDP | BGP (MP-BGP with EVPN SAFI) |
| MAC Learning | Data plane (flooding) | Control plane (BGP Type-2) |
| Split-Horizon Rule | Enabled by default | Not applicable (uses ESI/DF) |
| Route Types | None (MACs not advertised) | Type-1 to Type-5 (esp. Type-2) |
| Multi-Homing Support | Limited | Native (per ESI, per DF) |
| Scalability | Moderate | High |
What is the purpose of VPLS (Virtual Private LAN Service)?
VPLS allows geographically separated sites to appear as if they are on the same Layer-2 LAN.
VPLS extends Ethernet across a service provider MPLS backbone. Customer sites connect to provider edge routers, which use MPLS pseudowires to forward Ethernet frames between sites. From the customer perspective, all locations appear to be on the same broadcast domain. This is useful for enterprises that require Layer-2 connectivity between multiple sites.
Demand Score: 85
Exam Relevance Score: 90
What is a pseudowire in an MPLS Layer 2 VPN?
A pseudowire emulates a Layer-2 point-to-point circuit across an MPLS network.
Pseudowires encapsulate Layer-2 frames and transport them across an MPLS backbone using labels. They allow service providers to offer services such as Ethernet circuits or VLAN extensions between customer sites. Each pseudowire represents a virtual connection between provider edge routers.
Demand Score: 80
Exam Relevance Score: 88
What is the difference between Layer 2 VPNs and Layer 3 VPNs?
Layer 2 VPNs extend Ethernet frames, while Layer 3 VPNs exchange IP routes.
In a Layer 2 VPN, the provider transports customer Ethernet frames without participating in the customer’s routing. The customer network maintains its own routing protocols across the VPN. In contrast, Layer 3 VPNs involve provider edge routers participating in routing with the customer and exchanging IP routes via MP-BGP. The difference affects scalability, control, and operational complexity.
Demand Score: 78
Exam Relevance Score: 89
Why must MAC address learning be handled carefully in VPLS networks?
Because large broadcast domains can lead to excessive MAC table growth.
In VPLS, provider edge routers learn MAC addresses from customer traffic just like a traditional Ethernet switch. As the number of customer sites increases, the MAC table can grow significantly. Excessive broadcast traffic or unknown unicast flooding can also occur. Service providers mitigate this using MAC aging timers, split horizon rules, and careful network design to maintain scalability.
Demand Score: 76
Exam Relevance Score: 88