CCNP ENCOR lab 8 of 36
Multi-area OSPFv2: adjacencies, network types and passive interfaces
Join a three-router backbone to two regional areas with OSPFv2, control the DR election, use point-to-point links and passive interfaces, and read the link-state database the way the exam expects.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 3,584 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENCOR 350-401 guided labs, then 08 - Multi-area OSPFv2 - adjacencies network types and passive interfaces
- Level
- Intermediate
- Time
- About 70 minutes
- Nodes need
- 6 vCPU, 3,584 MB
- Smallest plan
- Lite
The scenario
Fernhill Freight runs its Leeds head office core on three routers that share one Ethernet segment (CORE). Two regional offices hang off the core: Bristol through R1 and Glasgow through R3. Today every router has its addresses but there is no routing at all, so Bristol can't reach anything beyond R4.
The design team has chosen multi-area OSPFv2: the core is area 0, Bristol is area 1 and Glasgow is area 2. You'll build it the way a senior engineer would: fixed router IDs, a predictable designated router, point-to-point WAN links, no hellos towards users, and costs that make sense on gigabit links.
| Device | Interface | Address | Area | Connects to |
|---|---|---|---|---|
| R1 | Lo0 | 10.255.0.1/32 | 0 | – |
| R1 | Gi0/0 | 10.0.0.1/24 | 0 | CORE |
| R1 | Gi0/1 | 10.0.14.1/30 | 1 | R4 Gi0/1 |
| R2 | Lo0 / Lo10 | 10.255.0.2/32 / 10.10.30.1/24 | 0 | – (Lo10 = HQ servers) |
| R2 | Gi0/0 | 10.0.0.2/24 | 0 | CORE |
| R3 | Lo0 | 10.255.0.3/32 | 0 | – |
| R3 | Gi0/0 | 10.0.0.3/24 | 0 | CORE |
| R3 | Gi0/1 | 10.0.35.1/30 | 2 | R5 Gi0/1 |
| R4 | Lo0 | 10.255.0.4/32 | 1 | – |
| R4 | Gi0/1 | 10.0.14.2/30 | 1 | R1 Gi0/1 |
| R4 | Gi0/2 | 10.20.10.1/24 | 1 | PC1 (Bristol LAN) |
| R5 | Lo0 / Lo10 | 10.255.0.5/32 / 10.30.10.1/24 | 2 | – (Lo10 = Glasgow LAN) |
| R5 | Gi0/1 | 10.0.35.2/30 | 2 | R3 Gi0/1 |
| PC1 | eth0 | 10.20.10.10/24, gateway 10.20.10.1 | – | R4 Gi0/2 |
Router IDs: R*n* uses n.n.n.n (R1 = 1.1.1.1 … R5 = 5.5.5.5).
Topology: R1, R2 and R3 share the CORE segment · R1 Gi0/1 — R4 Gi0/1 · R3 Gi0/1 — R5 Gi0/1 · R4 Gi0/2 — PC1.
What you’ll practise
- Enable OSPFv2 with both network statements and interface commands, with fixed router IDs
- Control the DR/BDR election on a broadcast segment with interface priorities
- Use the point-to-point network type on routed links and explain what changes
- Stop hellos on user-facing interfaces with passive-interface, and advertise loopbacks with their real mask
- Set a consistent reference bandwidth and read costs, LSA types and inter-area routes
The tasks
- Check the starting point
- Build area 0 with a predictable DR
- Add the regional areas over point-to-point links
- Keep hellos away from users
- Advertise the simulated LANs with their real mask
- Make the costs mean something
- Read the database and prove end-to-end reachability
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
Gi0/0to CORE (network) - R2
Gi0/0to CORE (network) - R3
Gi0/0to CORE (network) - R1
Gi0/1to R4Gi0/1 - R3
Gi0/1to R5Gi0/1 - R4
Gi0/2to PC1eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 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 |
| R5 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| PC1 | 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
CCNP ENCOR 350-401 guided labs.Open
08 - Multi-area OSPFv2 - adjacencies network types and passive interfacesand 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 CCNP ENCOR labs
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.