CCNP ENARSI lab 5 of 35
OSPF network types, router types and the link-state database
Build a three-area OSPFv2 network that uses broadcast, point-to-point and non-broadcast links, control the DR election, add an ASBR, and then read every LSA type in the database to see how OSPF describes the network.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 2,560 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENARSI 300-410 guided labs, then 05 - OSPF network types router types and the link-state database
- Level
- Intermediate
- Time
- About 75 minutes
- Nodes need
- 5 vCPU, 2,560 MB
- Smallest plan
- Lite
The scenario
Kestrel Engineering is replacing its old routing with OSPFv2. Three core routers (R1, R2, R3) share one Ethernet segment, the core LAN, which is area 0. R3 connects the design office (R4) in area 1 over a dedicated point-to-point circuit. R2 connects the factory (R5) in area 2 over a provider service that, like old Frame Relay, doesn't carry multicast, so OSPF must be told its neighbours by hand. R5 also connects a partner extranet that must be advertised into OSPF as an external route.
Build it, put the right network type on each link, control which router becomes DR on the core LAN, and then use the link-state database to explain exactly how OSPF describes this network.
| Device | Interface | Address | Area | Notes |
|---|---|---|---|---|
| R1 / R2 / R3 | Gi0/0 | 10.0.123.1 / .2 / .3 /24 | 0 | core LAN (one shared segment) |
| R3 | Gi0/1 | 10.0.34.3/24 | 1 | to R4 Gi0/0 |
| R4 | Gi0/0 | 10.0.34.4/24 | 1 | to R3 |
| R4 | Lo1 | 10.4.4.1/24 | 1 | office LAN |
| R2 | Gi0/1 | 10.0.25.2/24 | 2 | to R5 Gi0/0, no multicast |
| R5 | Gi0/0 | 10.0.25.5/24 | 2 | to R2 |
| R5 | Lo1 | 10.5.5.1/24 | 2 | factory LAN |
| R5 | Lo99 | 172.31.99.1/24 | – | partner extranet (external) |
| R*n* | Lo0 | 10.255.0.n/32 | as the router's area | router ID n.n.n.n |
What you’ll practise
- Enable OSPFv2 per interface in three areas with fixed router IDs
- Control the DR/BDR election with priorities and explain why it is non-preemptive
- Configure point-to-point and non-broadcast network types and compare their timers and behaviour
- Make a router an ASBR and identify internal, backbone, ABR and ASBR roles
- Read LSA types 1, 2, 3, 4 and 5 and explain who originates each and how far it floods
The tasks
- Bring up area 0 on the core LAN
- Control the DR election
- Area 1 over a point-to-point link
- Area 2 over a link without multicast
- Make R5 an ASBR
- Read the link-state database
- Test end to end
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) - R3
Gi0/1to R4Gi0/0 - R2
Gi0/1to R5Gi0/0
| 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 |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNP ENARSI 300-410 guided labs.Open
05 - OSPF network types router types and the link-state databaseand 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 ENARSI labs
Related labs in other courses
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.