JNCIS-ENT lab 12 of 17

IS-IS levels and areas

Run IS-IS across two areas: an L1/L2 core router, an L2-only edge router and an L1-only branch. You read the link-state database and its TLVs, watch a pre-emptive DIS election, switch to wide metrics, export a static route, and leak a level 2 route into level 1.

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 12 - IS-IS levels and areas

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 80 minutes
Nodes need
12 vCPU, 15,360 MB
Smallest plan
Standard

The scenario

Ashby Freight's new service provider partner runs IS-IS, and the network team has decided to move the WAN core to IS-IS as well. You are building the first three routers:

RouterNETAreaLevelsIS-IS interfaces
CORE49.0001.1921.6825.5011.0049.00011 and 2ge-0/0/0 (to EDGE, level 2 only, point-to-point), ge-0/0/1 (branch segment, level 1 only), ge-0/0/2 (campus LAN, passive), lo0
EDGE49.0002.1921.6825.5012.0049.00022 onlyge-0/0/0 (to CORE, point-to-point), lo0
BRANCH49.0001.1921.6825.5013.0049.00011 onlyge-0/0/0 (branch segment), ge-0/0/2 (branch LAN, passive), lo0

EDGE has a static route to the ISP's monitoring prefix 203.0.113.0/24, which the whole network must reach. The branch must also be able to reach EDGE's loopback, 192.168.255.12, directly (a management requirement), not just through a default route.

What you’ll practise

  • Configure NET addresses, family iso and IS-IS levels per router and per interface
  • Read IS-IS adjacencies, the database, LSPs and their TLVs
  • Explain how the DIS is elected on a broadcast segment and why it differs from an OSPF DR
  • Explain narrow and wide metrics and set interface metrics
  • Export external routes into IS-IS and leak level 2 routes into level 1 with policy
  • Troubleshoot missing adjacencies with IS-IS show commands

The tasks

  1. Addresses for IS-IS
  2. Levels and adjacencies
  3. The database, LSPs and TLVs
  4. The DIS on the branch segment
  5. Wide metrics
  6. Export and leak routes with policy
  7. Troubleshoot a missing adjacency

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 areas3 nodes and 4 networks, 6 links. Every link is listed as text below the diagram.COREEDGEBRANCHBranch-SegmentISP-HandoffCampus-LANBranch-LANge-0/0/2ge-0/0/2ge-0/0/2ge-0/0/0ge-0/0/1ge-0/0/0ge-0/0/0
3 nodes and 4 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in IS-IS levels and areas, 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
BRANCHJuniper 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 12 - IS-IS levels and areas 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.