CloudLabBox
Try the free demo

JNCIS-SP lab 1 of 16

Protocol-independent routes and martians

Build the routes no protocol owns on Junos: a static route with a floating backup, recursive next hops, aggregates, a conditional default from a generated route, and martian handling.

Run this lab

It needs Lite: its 3 nodes are set to 5 vCPU and 7,680 MB in total. That fits the free demo too.

In your workspace: Shared, then JNCIS-SP JN0-364 guided labs, then 01 - Protocol-independent routes and martians

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 75 minutes
Nodes need
5 vCPU, 7,680 MB
Smallest plan
Lite

The scenario

Skerry Networks is a regional carrier, AS 64510. Its new Whitby point of presence has two routers: EDGE, with two links to an upstream provider, and CORE, which serves customer LANs. The two already run OSPF between them, for their loopbacks and the link. Nothing else is routed yet, so the customer LANs can't reach the upstream network. You'll build the routes that don't belong to any routing protocol, and see how Junos treats each of them.

DeviceInterfaceAddressNotes
UPSTREAMGi0/0 / Gi0/1203.0.113.1/30 / 198.51.100.1/30Routes 10.0.0.0/8 back to EDGE, over the primary link first
UPSTREAMLoopback0198.18.0.1/24The upstream network
EDGEge-0/0/0 / ge-0/0/1203.0.113.2/30 / 198.51.100.2/30Primary and backup links
EDGEge-0/0/2, lo010.0.12.1/30, 10.255.0.1/32OSPF area 0
COREge-0/0/0, lo010.0.12.2/30, 10.255.0.2/32OSPF area 0
COREge-0/0/110.20.1.1/24, 10.20.2.1/24, 10.20.3.1/24Three customer LANs on one port

There are no hosts in this lab. A ping from CORE with source 10.20.1.1 stands in for a customer.

What you’ll practise

  • Add static routes with qualified next hops and resolve
  • Find unusable routes with show route hidden
  • Build and export aggregate and generated routes, and compare their next hops
  • Read and change the martian list

The tasks

  1. A static route with a backup
  2. A next hop that is not connected
  3. An aggregate route
  4. A generated route
  5. Martian addresses

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 routes and martians3 nodes and 1 network, 4 links. Every link is listed as text below the diagram.UPSTREAMEDGECORECustomerLANsGi0/0ge-0/0/0Gi0/1ge-0/0/1ge-0/0/1ge-0/0/2ge-0/0/0
3 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • UPSTREAM Gi0/0 to EDGE ge-0/0/0
  • UPSTREAM Gi0/1 to EDGE ge-0/0/1
  • EDGE ge-0/0/2 to CORE ge-0/0/0
  • CORE ge-0/0/1 to CustomerLANs (network)
Nodes in Protocol-independent routes and martians, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
UPSTREAMCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
EDGEJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 3,584 MB
COREJuniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 3,584 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 01 - Protocol-independent routes and martians 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.