JNCIS-ENT lab 11 of 17

OSPF in depth

Build a two-area OSPF network from scratch. You control the DR election on a shared segment, read every LSA type in the database, turn the branch area into a stub, a totally stubby area and finally an NSSA that injects a partner network, summarise the branch at the ABR, and secure the branch link with MD5.

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 11 - OSPF in depth

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

The scenario

Ashby Freight is splitting its OSPF network into areas before it grows any further. CORE will be the area border router (ABR) between the backbone (area 0) and the branch area (area 1). EDGE connects to the ISP and injects the default route and the ISP's monitoring prefix into OSPF. BRANCH is a remote site that also has a partner network, 10.130.0.0/16, behind a partner router at 10.13.0.254.

RouterRouter IDArea 0 interfacesArea 1 interfaces
CORE192.168.255.11ge-0/0/0 (core segment, 172.16.0.11/24), ge-0/0/2 (campus LAN, passive), lo0ge-0/0/1 (to BRANCH, 172.16.13.1/30)
EDGE192.168.255.12ge-0/0/0 (core segment, 172.16.0.12/24), lo0
BRANCH192.168.255.13ge-0/0/0 (to CORE, p2p), ge-0/0/2 (branch LANs, passive), lo0

EDGE already has static routes 0.0.0.0/0 and 203.0.113.0/24 via the ISP (198.51.100.1). BRANCH has 10.130.0.0/16 via 10.13.0.254. No OSPF is configured yet.

What you’ll practise

  • Configure OSPF areas, router IDs and interface types, and follow adjacencies through their states
  • Control the DR and BDR election and read network LSAs
  • Identify router, network, summary, ASBR summary, external and NSSA LSAs and the routers that originate them
  • Configure stub, totally stubby and not-so-stubby areas and predict each one's routing table
  • Summarise an area with area-range and export external routes with policy
  • Secure an adjacency with MD5 authentication and troubleshoot it with OSPF show commands

The tasks

  1. Build two areas
  2. Control the DR election
  3. Inject external routes and read every LSA type
  4. Stub, then totally stubby
  5. Convert to an NSSA for the partner network
  6. Summarise the branch area
  7. Authenticate the branch link, and troubleshoot it

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 OSPF in depth3 nodes and 4 networks, 6 links. Every link is listed as text below the diagram.COREEDGEBRANCHCore-SegmentISP-HandoffCampus-LANBranch-LANge-0/0/0ge-0/0/2ge-0/0/2ge-0/0/2ge-0/0/0ge-0/0/1ge-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 OSPF in depth, 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 11 - OSPF in depth 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.