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
- 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:
| Router | NET | Area | Levels | IS-IS interfaces |
|---|---|---|---|---|
| CORE | 49.0001.1921.6825.5011.00 | 49.0001 | 1 and 2 | ge-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 |
| EDGE | 49.0002.1921.6825.5012.00 | 49.0002 | 2 only | ge-0/0/0 (to CORE, point-to-point), lo0 |
| BRANCH | 49.0001.1921.6825.5013.00 | 49.0001 | 1 only | ge-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
- Addresses for IS-IS
- Levels and adjacencies
- The database, LSPs and TLVs
- The DIS on the branch segment
- Wide metrics
- Export and leak routes with policy
- 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.
Every link, as text
- CORE
ge-0/0/0to EDGEge-0/0/0 - CORE
ge-0/0/1to Branch-Segment (network) - BRANCH
ge-0/0/0to Branch-Segment (network) - CORE
ge-0/0/2to Campus-LAN (network) - EDGE
ge-0/0/2to ISP-Handoff (network) - BRANCH
ge-0/0/2to Branch-LAN (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| CORE | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| EDGE | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| BRANCH | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIS-ENT JN0-352 guided labs.Open
12 - IS-IS levels and areasand 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
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.