CloudLabBox
Try the free demo

MPLS and L3VPN lab 5 of 11

A Junos PE with an IOS PE over an IOS P

Bring a Juniper router into an IOS MPLS core as a PE in a customer's VPN. Build LDP, MP-BGP and the VRF on Junos, read inet.3, mpls.0 and bgp.l3vpn.0, prove the LSP with MPLS ping in both directions and find the MTU difference.

Run this lab

It needs Standard: its 5 nodes are set to 8 vCPU and 7,168 MB in total.

In your workspace: Shared, then MPLS and L3VPN guided labs, then 05 - A Junos PE with an IOS PE over an IOS P

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 8 vCPU and 7,168 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 100 minutes
Nodes need
8 vCPU, 7,168 MB
Smallest plan
Standard

The scenario

Wrenfield Networks has bought a Juniper router for its Bristol exchange. Your IOS core and your IOS PE don't care who made a router, because LDP and MP-BGP are open standards. The team still has to run it, and almost every word for the same idea is different. You'll bring up PE2 as a PE in Alder Foods' VPN, then compare the two vendors' views of the same labels.

DeviceRoleLoopbackNotes
PE1IOS PE10.255.0.1VRF ALDER, RD 65100:1, RT 65100:100
PIOS P10.255.0.2LDP only, no BGP
PE2Junos PE10.255.0.3You build this: RD 65100:3, RT 65100:100
CE1Alder site 1AS 65201, LAN 192.168.1.0/24
CE2Alder site 2AS 65202, LAN 192.168.2.0/24, peers with 172.16.2.1

The same idea has different names on the two systems:

IdeaIOSJunos
Enable labels on a linkmpls ipfamily mpls on the unit, and the unit under protocols mpls and protocols ldp
Label table for next hopsLFIBinet.3 for LSP endpoints, mpls.0 for incoming labels
VPN routesshow bgp vpnv4 unicast allshow route table bgp.l3vpn.0
VRFvrf definitionrouting-instances NAME instance-type vrf
VRF routing tableshow ip route vrf ALDERshow route table ALDER.inet.0
Route targetsroute-target import and exportvrf-target sets both
DeviceInterfaceAddressConnects to
CE1Loopback1192.168.1.1/24
CE1Gi0/0172.16.1.2/30PE1 Gi0/0
PE1Loopback010.255.0.1/32
PE1Gi0/0172.16.1.1/30CE1 Gi0/0
PE1Gi0/110.0.12.1/30P Gi0/0
PLoopback010.255.0.2/32
PGi0/010.0.12.2/30PE1 Gi0/1
PGi0/110.0.23.1/30PE2 ge-0/0/0
PE2ge-0/0/010.0.23.2/30P Gi0/1
PE2ge-0/0/1172.16.2.1/30CE2 Gi0/0
PE2lo010.255.0.3/32, 127.0.0.1/32
CE2Loopback1192.168.2.1/24
CE2Gi0/0172.16.2.2/30PE2 ge-0/0/1

What you’ll practise

  • Enable MPLS and LDP on Junos and read the session from both vendors
  • Explain what inet.3, mpls.0, bgp.l3vpn.0 and the VRF table each hold
  • Build a Junos VRF with an RD, a target and an eBGP customer
  • Use MPLS ping and traceroute across vendors
  • Find and fix the MPLS MTU difference between the two systems

The tasks

  1. Add MPLS and LDP
  2. Build the MP-BGP session
  3. Build the VRF
  4. Use each vendor's MPLS ping
  5. Check the MTU

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of A Junos PE with an IOS PE over an IOS P5 nodes, 4 links. Every link is listed as text below the diagram.CE1PE1PPE2CE2Gi0/0Gi0/0Gi0/1Gi0/0Gi0/1ge-0/0/0ge-0/0/1Gi0/0
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • CE1 Gi0/0 to PE1 Gi0/0
  • PE1 Gi0/1 to P Gi0/0
  • P Gi0/1 to PE2 ge-0/0/0
  • PE2 ge-0/0/1 to CE2 Gi0/0
Nodes in A Junos PE with an IOS PE over an IOS P, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
CE1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE2Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
CE2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder MPLS and L3VPN guided labs.

  3. Open 05 - A Junos PE with an IOS PE over an IOS P and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More MPLS and L3VPN labs

All MPLS and L3VPN labs

Related labs in other courses

CloudLabBox is independent of Cisco, Juniper Networks and MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.