CloudLabBox
Try the free demo

JNCIS-SP lab 6 of 16

Bridging and VLANs with IRB and Q-in-Q

Do Layer 2 the MX way: bridge domains, access ports, trunks and IRB, then separate a customer in a virtual switch, and carry another's tags untouched with Q-in-Q.

Run this lab

It needs Standard: its 6 nodes are set to 12 vCPU and 13,312 MB in total.

In your workspace: Shared, then JNCIS-SP JN0-364 guided labs, then 06 - Bridging and VLANs with IRB and Q-in-Q

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 12 vCPU and 13,312 MB together. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 95 minutes
Nodes need
12 vCPU, 13,312 MB
Smallest plan
Standard

The scenario

Skerry sells Ethernet between its Malton and York PE routers. These are vMX-class routers, so Layer 2 is done MX-style, with bridge domains. Nothing is configured yet except descriptions and loopbacks. You'll serve three kinds of customer: Skerry's own hosts on two VLANs, Birch, which insists on using VLAN 100 even though Skerry already does, and Alder, which wants its own tags left alone.

DevicePortConnectsService
PE1, PE2ge-0/0/0Each otherTrunk for VLANs 100 and 200
PE1, PE2ge-0/0/1Each otherTrunk for Birch
PE1, PE2ge-0/0/5Each otherProvider link for Alder, S-VLAN 500
PE1ge-0/0/2H1, 192.168.100.11/24, gateway .1Access, VLAN 100
PE2ge-0/0/2H2, 192.168.200.12/24, gateway .1Access, VLAN 200
PE1, PE2ge-0/0/3CE1, CE2 Gi0/0.100 (192.168.100.21 and .22)Birch, tagged VLAN 100
PE1, PE2ge-0/0/4CE1, CE2 Gi0/1.10 (172.16.10.1 and .2)Alder, tagged VLAN 10

IRB addresses: PE1 irb.100 192.168.100.1/24 and irb.200 192.168.200.1/24, PE2 irb.100 192.168.100.2/24.

What you’ll practise

  • Explain learning, flooding and VLAN normalisation
  • Configure access and trunk ports in bridge domains
  • Route between VLANs with IRB
  • Reuse a VLAN ID in a virtual switch
  • Build Q-in-Q with VLAN maps

The tasks

  1. Bridge domains and access ports
  2. A trunk
  3. Integrated routing and bridging
  4. A virtual switch
  5. Provider bridging (Q-in-Q)

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 Bridging and VLANs with IRB and Q-in-Q6 nodes, 9 links. Every link is listed as text below the diagram.PE1PE2CE1CE2H1H2ge-0/0/2eth0ge-0/0/2eth0ge-0/0/3Gi0/0ge-0/0/4Gi0/1ge-0/0/3Gi0/0ge-0/0/4Gi0/1ge-0/0/0ge-0/0/0ge-0/0/1ge-0/0/1ge-0/0/5ge-0/0/5
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • PE1 ge-0/0/0 to PE2 ge-0/0/0
  • PE1 ge-0/0/1 to PE2 ge-0/0/1
  • PE1 ge-0/0/5 to PE2 ge-0/0/5
  • PE1 ge-0/0/2 to H1 eth0
  • PE2 ge-0/0/2 to H2 eth0
  • PE1 ge-0/0/3 to CE1 Gi0/0
  • PE2 ge-0/0/3 to CE2 Gi0/0
  • PE1 ge-0/0/4 to CE1 Gi0/1
  • PE2 ge-0/0/4 to CE2 Gi0/1
Nodes in Bridging and VLANs with IRB and Q-in-Q, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
PE1Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
PE2Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
CE1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
CE2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
H1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
H2VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 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 JNCIS-SP JN0-364 guided labs.

  3. Open 06 - Bridging and VLANs with IRB and Q-in-Q 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 JNCIS-SP labs

All JNCIS-SP labs

Related labs in other courses

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