JNCIS-SP lab 4 of 16

IS-IS levels and metrics with policy

Add a new area to a working IS-IS network, read LSPs and TLVs, make a router the DIS, steer traffic with metrics and leak Level 2 routes into Level 1.

Run this lab

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

In your workspace: Shared, then JNCIS-SP JN0-364 guided labs, then 04 - IS-IS levels and metrics with policy

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

Level
Intermediate
Time
About 90 minutes
Nodes need
8 vCPU, 13,824 MB
Smallest plan
Standard

The scenario

Skerry runs IS-IS in two areas. Area 49.0002 works already: R3 is its L1/L2 router and R4 is a Level 1 router with the York LAN. Area 49.0001 is new. You'll build R1 and R2, join the areas over two links, and control which routes and paths are used.

DeviceInterfaceAddressRole
R1ge-0/0/010.0.12.1/30Area 49.0001, Level 1 only
R1ge-0/0/1, lo010.10.1.1/24, 10.255.0.1/32Malton LAN, NET 49.0001.0000.0000.0001.00
R2ge-0/0/010.0.12.2/30Level 1 to R1
R2ge-0/0/1 / ge-0/0/210.0.23.1/30 / 10.0.32.1/30Level 2 to R3, paths A and B
R2lo010.255.0.2/32NET 49.0001.0000.0000.0002.00
R3ge-0/0/0 / ge-0/0/210.0.23.2/30 / 10.0.32.2/30Level 2 to R2
R3ge-0/0/1, lo010.0.34.1/24, 10.255.0.3/32Level 1 to R4, NET 49.0002.0000.0000.0003.00
R4Gi0/0, Lo0, Lo110.0.34.2/24, 10.255.0.4/32, 10.40.1.1/24Level 1, NET 49.0002.0000.0000.0004.00
H1eth010.10.1.10/24Gateway 10.10.1.1

What you’ll practise

  • Configure NETs, family iso and levels
  • Read LSPs and TLVs and explain the attached bit
  • Control the DIS and use point-to-point links
  • Set metrics and export and leak routes with policy

The tasks

  1. Bring up IS-IS
  2. Levels and areas
  3. LSPs, TLVs and wide metrics
  4. The DIS and point-to-point links
  5. Metrics
  6. Export and route leaking with policy

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 IS-IS levels and metrics with policy5 nodes, 5 links. Every link is listed as text below the diagram.H1R1R2R3R4ge-0/0/1eth0ge-0/0/0ge-0/0/0ge-0/0/1Gi0/0ge-0/0/1ge-0/0/0ge-0/0/2ge-0/0/2
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in IS-IS levels and metrics with policy, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
H1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
R1Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
R2Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
R3Juniper vSRX NextGen templatevsrxng-24.4R1.92 vCPU, 4,096 MB
R4Cisco 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 JNCIS-SP JN0-364 guided labs.

  3. Open 04 - IS-IS levels and metrics with policy 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.