Projects › Service Provider MPLS L3VPN for Two Overlapping Customers
Service Provider MPLS L3VPN for Two Overlapping Customers
A regional carrier is onboarding two enterprise customers onto its MPLS core: Red (a retailer) and Blue (a law firm). Both use 10.1.1.0/24 at their head office and 10.2.2.0/24 at a branch, and both run OSPF with the carrier's PE routers. The core has two PEs (PE1, PE2) and one P router, with Loopback0 addresses 10.255.0.1-3. Design the L3VPN: LDP in the core, a VRF per customer on each PE with its own RD and route targets, MP-BGP VPNv4 between the PEs, and PE-CE OSPF redistributed into BGP and back, so each customer sees only its own sites.
Difficulty: expert · Time: about 80 minutes
Why it matters
MPLS L3VPN is how carriers deliver private WAN services over a shared core, and it is the basis of most enterprise WANs that are not SD-WAN. Explaining how the same prefix stays separate for two customers (RD for uniqueness, RT for membership) is the standard service-provider interview question.
Technologies
- MPLS
- LDP
- VRFs
- MP-BGP
- Route Distinguishers (RD)
- Route Targets (RT)
Related projects
- Dual-Homed eBGP Edge Routing with AS-Path Prepending
- DDoS Mitigation with BGP Flowspec at a Regional ISP
- MPLS Traffic Engineering with RSVP-TE and Fast Reroute
- Replacing LDP with Segment Routing (SR-MPLS) in a Six-Router Core
- Advanced BGP Traffic Engineering with Standard & Extended Communities
- Junos eBGP Peering at a Regional Internet Exchange
- Arista EOS eBGP Between Two Business Units After a Merger
- Arista EOS BGP Prefix Advertisement to an Upstream Provider