JNCIS-SP lab 3 of 16
OSPF in a provider core with policy
Join a router to a working OSPF core, take over the DR role, read every LSA type, build stub and NSSA areas, and apply OSPF's limited but useful policy tools.
Run this lab
It needs Standard: its 7 nodes are set to 10 vCPU and 15,360 MB in total.
In your workspace: Shared, then JNCIS-SP JN0-364 guided labs, then 03 - OSPF in a provider core with policy
- Level
- Intermediate
- Time
- About 90 minutes
- Nodes need
- 10 vCPU, 15,360 MB
- Smallest plan
- Standard
The scenario
This is Skerry's northern core. R2 and R3 already run OSPF, and ASBR injects two external networks. R1 is new, and isn't in OSPF. You'll bring it in, take over the DR role on the core LAN, read the database, tune two areas and apply policy.
| Device | Interface | Address | OSPF |
|---|---|---|---|
| R1 | ge-0/0/0 | 10.0.100.1/24 | Area 0, core LAN (you configure it) |
| R1 | ge-0/0/1 | 10.0.15.1/30 | Area 2 (you configure it) |
| R1 | ge-0/0/2, lo0 | 10.10.1.1/24, 10.255.0.1/32 | Area 0, passive (you configure it) |
| R2 | ge-0/0/0, lo0 | 10.0.100.2/24, 10.255.0.2/32 | Area 0 |
| R2 | ge-0/0/1 | 10.0.23.1/30 | Area 1 |
| R3 | ge-0/0/0 | 10.0.23.2/30 | Area 1 |
| R3 | ge-0/0/1, lo0 | 10.30.1.1/24, 10.30.2.1/24, 10.255.0.3/32 | Area 1, passive |
| ASBR | Gi0/0 | 10.0.100.3/24 | Area 0, priority 0, redistributes 172.20.1.0/24 and 172.20.2.0/24 |
| PARTNER | Gi0/0 | 10.0.15.2/30 | Area 2, an NSSA, redistributes 172.25.1.0/24 |
| H1 / H3 | eth0 | 10.10.1.10/24 / 10.30.1.10/24 | Gateways .1 |
What you’ll practise
- Explain the packet types, the neighbour states and the DR election
- Read LSA types 1 to 5 and 7 from the database
- Configure stub and NSSA areas
- Summarise, export and import with policy
- Use traceoptions and live captures
The tasks
- Neighbours and the DR
- Read the link-state database
- Stub and NSSA areas
- Policy: summarise, export, import
- Troubleshooting tools
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
- R1
ge-0/0/0to CoreLAN (network) - R2
ge-0/0/0to CoreLAN (network) - ASBR
Gi0/0to CoreLAN (network) - R2
ge-0/0/1to R3ge-0/0/0 - R1
ge-0/0/1to PARTNERGi0/0 - R1
ge-0/0/2to H1eth0 - R3
ge-0/0/1to H3eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| ASBR | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R1 | Juniper vSRX NextGen template | vsrxng-24.4R1.9 | 2 vCPU, 4,096 MB |
| R2 | Juniper vSRX NextGen template | vsrxng-24.4R1.9 | 2 vCPU, 4,096 MB |
| R3 | Juniper vSRX NextGen template | vsrxng-24.4R1.9 | 2 vCPU, 4,096 MB |
| PARTNER | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| H1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| H3 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIS-SP JN0-364 guided labs.Open
03 - OSPF in a provider core with policyand 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
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.