Network labs Docs Open simulator →

MPLS L3VPN — an IOS PE and a Junos PE across a P router

A provider core of three routers already runs OSPF, LDP and an iBGP VPNv4 session between its two PEs: PE1 runs IOS, PE2 runs Junos. Configure the customer VRF on both PEs — route distinguisher, route targets, the customer port and the eBGP session to the CE — then ping from site 1 to site 2 and read the MPLS labels in a traceroute.

Open this lab in your browser →

Free · no install · no account

Scenario

An MPLS Layer 3 VPN carries a customer's routes across a provider network without putting them in the provider's own routing table. Each PE keeps the customer in a VRF, a routing table of its own: - The route distinguisher (RD) makes the customer's prefixes unique in BGP: 65000:1 + 192.168.1.0/24 is a VPNv4 prefix. - Route targets (RT) decide which VRFs import which routes. A route exported with RT 65000:1 is imported by every VRF that imports 65000:1. The RDs may differ; the RTs must match. - MP-BGP carries the VPNv4 routes between the PEs, each with a VPN label. - LDP gives the PEs a transport label to reach each other's loopback across the P router. A packet from site 1 to site 2 leaves PE1 with two labels: the transport label on top, the VPN label below. P swaps the transport label. PE2 is the last hop, so P pops the transport label (penultimate-hop popping), and PE2 reads the VPN label to know which VRF the packet belongs to. Already configured: the core (OSPF, LDP on the core links, loopbacks 10.255.0.1/2/3), the iBGP session PE1 ↔ PE2 with the VPNv4 family, and the CEs. CE1 (AS 65101) peers with 10.1.1.1 and announces 192.168.1.0/24; CE2 (AS 65102) peers with 10.2.2.1 and announces 192.168.2.0/24. Missing: the customer VRF CUST on both PEs. The two PEs are different vendors and say the same things in different words.

Topology

5 × router · Cisco IOS-style, Junos-style

What you will do

  1. On PE1 (IOS), create VRF CUST with RD 65000:1 and route target 65000:1 (import and export), put GigabitEthernet2 into it, and add the CE1 session under address-family ipv4 vrf CUST, with redistribute connected.

  2. On PE2 (Junos), create the routing instance CUST of type vrf with interface ge-0/0/1.0, RD 65000:2 and vrf-target target:65000:1, and an eBGP group to CE2 (10.2.2.2, AS 65102) inside it. Commit.

  3. From CE1, ping 192.168.2.1 (site 2), then run traceroute 192.168.2.1 and read the labels on each hop.

Open this lab in your browser →

More labs on this topic

This lab in other languages

MPLS L3VPN — ein IOS-PE und ein Junos-PE über einen P-RouterMPLS L3VPN — un PE IOS y un PE Junos a través de un router PMPLS L3VPN — um PE IOS e um PE Junos através de um roteador PMPLS L3VPN — un PE IOS et un PE Junos de part et d'autre d'un routeur PMPLS L3VPN — एक P router के आर-पार एक IOS PE और एक Junos PEMPLS L3VPN——经 P 路由器互连的 IOS PE 与 Junos PEMPLS L3VPN — un PE IOS e un PE Junos attraverso un router PMPLS L3VPN — P ルータを挟んだ IOS の PE と Junos の PEMPLS L3VPN — P 라우터를 사이에 둔 IOS PE와 Junos PEMPLS L3VPN — PE на IOS и PE на Junos через маршрутизатор PMPLS L3VPN — bir P yönlendirici üzerinden bir IOS PE ve bir Junos PEMPLS L3VPN — một PE IOS và một PE Junos qua một router P