CloudLabBox
Try the free demo

JNCIS-ENT lab 9 of 17

Protocol-independent routing

Use the routing tools that work whatever the protocol: a static route that resolves through OSPF, an aggregate that advertises one prefix for a whole site, a default route generated only while the ISP is alive, a custom martian, and RIB groups that share routes between a services instance and the main table.

Run this lab

It needs Standard: its 3 nodes are set to 12 vCPU and 15,360 MB in total.

In your workspace: Shared, then JNCIS-ENT JN0-352 guided labs, then 09 - Protocol-independent routing

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 15,360 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
12 vCPU, 15,360 MB
Smallest plan
Standard

The scenario

Ashby Freight's WAN core has three routers: CORE (campus LANs), EDGE (internet hand-off) and DC (data centre). OSPF area 0 runs on the three links and the loopbacks. Several jobs are waiting:

JobRouter
Reach a partner network, 10.99.0.0/16, through DC's loopback 192.168.255.13 (the partner link is not built in this lab)CORE
Advertise the campus as one prefix, 10.20.0.0/22, instead of separate LANs (10.20.0.0/24 to 10.20.2.0/24 today, 10.20.3.0/24 later)CORE
Give the network a default route only while the ISP is reachable. The ISP's monitoring prefix 203.0.113.0/24 (a static route via 198.51.100.1) is the health signalEDGE
Never install routes from the carrier-grade NAT range 100.64.0.0/10; a test route 100.64.10.0/24 from DC shows the problemCORE
Put the services LAN 10.30.0.0/24 in its own routing instance SERVICES on DC, and still make it reachable from the rest of the networkDC

What you’ll practise

  • Configure static routes with resolve and explain hidden routes
  • Configure aggregate routes, read their contributing routes, and choose reject or discard
  • Configure a generated route with a policy so it exists only while its contributor does
  • Explain martian addresses and add your own
  • Share routes between routing instances with RIB groups

The tasks

  1. A static route that resolves through OSPF
  2. Aggregate the campus
  3. A default route generated from the ISP's health
  4. Martian addresses
  5. RIB groups for a services instance

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 Protocol-independent routing3 nodes and 3 networks, 6 links. Every link is listed as text below the diagram.COREEDGEDCCampus-LANsISP-HandoffServices-LANge-0/0/2ge-0/0/2ge-0/0/2ge-0/0/0ge-0/0/0ge-0/0/1ge-0/0/0ge-0/0/1ge-0/0/1
3 nodes and 3 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • CORE ge-0/0/0 to EDGE ge-0/0/0
  • CORE ge-0/0/1 to DC ge-0/0/0
  • EDGE ge-0/0/1 to DC ge-0/0/1
  • CORE ge-0/0/2 to Campus-LANs (network)
  • EDGE ge-0/0/2 to ISP-Handoff (network)
  • DC ge-0/0/2 to Services-LAN (network)
Nodes in Protocol-independent routing, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
COREJuniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
EDGEJuniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
DCJuniper 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 JNCIS-ENT JN0-352 guided labs.

  3. Open 09 - Protocol-independent routing 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-ENT labs

All JNCIS-ENT 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.