CloudLabBox
Try the free demo

JNCIA-Junos lab 9 of 15

Routing instances

Split one router into three: the corporate network, a guest Wi-Fi network that may reach HQ through a controlled link, and a CCTV network that must stay completely isolated even though it uses the same addresses as the guests.

Run this lab

It needs Lite: its 1 node is set to 4 vCPU and 5,120 MB in total. That fits the free demo too.

In your workspace: Shared, then JNCIA-Junos JN0-106 guided labs, then 09 - Routing instances

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 45 minutes
Nodes need
4 vCPU, 5,120 MB
Smallest plan
Lite

The scenario

Ashby Freight's HQ router is getting two new networks from two different contractors, and both of them used 192.168.100.0/24:

  • Guest Wi-Fi (ge-0/0/3): guests may reach the HQ web portal on the corporate network, but only through a controlled link, so the corporate routing table never learns anything it should not.
  • CCTV (ge-0/0/4): must never reach, or be reached from, anything else.

Rather than buy two more routers, you will split HQ into separate routing instances. To connect the guest instance to the corporate table over a real link, a technician has patched ge-0/0/1 (corporate side, 172.16.99.1/30) to ge-0/0/2 (guest side, 172.16.99.2/30) on the same router.

What you’ll practise

  • Explain what a routing instance is and name the common instance types
  • Create virtual-router instances and move interfaces into them
  • Read instance routing tables such as GUEST.inet.0
  • Route between an instance and the main table over a physical link
  • Run ping and traceroute inside an instance
  • Show that instances may reuse the same addresses

The tasks

  1. The instances you already have
  2. Create the guest instance
  3. Route between the guest instance and the corporate table
  4. Create the isolated CCTV instance
  5. Look at the result

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 Routing instances1 node and 3 networks, 4 links. Every link is listed as text below the diagram.HQHQ-LANGuest-WiFiCCTV-LANge-0/0/1ge-0/0/2ge-0/0/0ge-0/0/3ge-0/0/4
1 node and 3 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • HQ ge-0/0/0 to HQ-LAN (network)
  • HQ ge-0/0/1 to HQ ge-0/0/2
  • HQ ge-0/0/3 to Guest-WiFi (network)
  • HQ ge-0/0/4 to CCTV-LAN (network)
Nodes in Routing instances, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
HQJuniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 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 JNCIA-Junos JN0-106 guided labs.

  3. Open 09 - Routing instances 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 JNCIA-Junos labs

All JNCIA-Junos labs

Related labs in other courses

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