JNCIP-ENT lab 2 of 19
OSPFv3 realms and virtual links
Build OSPFv3 across three areas, repair a disconnected area with a virtual link, read the OSPFv3 LSA types, and carry IPv4 in an ipv4-unicast realm.
Run this lab
It needs Standard: its 4 nodes are set to 10 vCPU and 11,264 MB in total.
In your workspace: Shared, then JNCIP-ENT JN0-650 guided labs, then 02 - OSPFv3 realms and virtual links
- Level
- Advanced
- Time
- About 80 minutes
- Nodes need
- 10 vCPU, 11,264 MB
- Smallest plan
- Standard
The scenario
Northmere has bought a small haulier in Goole, whose router R3 already runs OSPFv3 in area 3. The only way to reach it is through R2, which sits in area 1, so area 3 doesn't touch the backbone. You'll build OSPFv3 on R1 and R2, see the problem, fix it with a virtual link, and then read how OSPFv3's LSAs differ from OSPFv2's. A later step runs IPv4 through OSPFv3 on one link, as a trial for dropping OSPFv2.
| Device | Interface | Address | OSPFv3 |
|---|---|---|---|
| R1 | ge-0/0/1 | 2001:db8:14::1/64 | Area 0, to R4 |
| R1 | ge-0/0/0 | 2001:db8:12::1/64, 10.0.12.1/30 | Area 1, to R2 |
| R1 | lo0 | 2001:db8:255::1/128, 10.255.0.1/32 | Area 0, passive |
| R2 | ge-0/0/0 | 2001:db8:12::2/64, 10.0.12.2/30 | Area 1, to R1 |
| R2 | ge-0/0/1 | 2001:db8:23::2/64 | Area 3, to R3 |
| R2 | lo0 | 2001:db8:255::2/128, 10.255.0.2/32 | Area 1, passive |
| R3 | Gi0/0, Lo0 | 2001:db8:23::3/64, 2001:db8:255::3/128 | Area 3 |
| R3 | Lo10, Lo11 | 2001:db8:30:1::1/64, 2001:db8:30:2::1/64 | Area 3, Goole LANs |
| R4 | Gi0/0, Lo0 | 2001:db8:14::4/64, 2001:db8:255::4/128 | Area 0 |
| R4 | Lo10 | 2001:db8:40:1::1/64 | Area 0, head office LAN |
All links are point-to-point. R3 and R4 are ready for you.
What you’ll practise
- Configure OSPFv3 on Junos and read its LSA types
- Explain why an area needs the backbone, and repair it with a virtual link
- Summarise with area-range in OSPFv3
- Run an ipv4-unicast realm
- Export external routes into OSPFv3
The tasks
- Build OSPFv3 and find what changed from OSPFv2
- Stretch the backbone with a virtual link
- Summarise area 3
- Carry IPv4 in OSPFv3 with a realm
- Export an external route
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 R2ge-0/0/0 - R1
ge-0/0/1to R4Gi0/0 - R2
ge-0/0/1to R3Gi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| R2 | Juniper vJunos-router | vjunosrouter-24.2R1-S2.5 | 4 vCPU, 5,120 MB |
| R3 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R4 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
JNCIP-ENT JN0-650 guided labs.Open
02 - OSPFv3 realms and virtual linksand 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 JNCIP-ENT labs
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.