CCNP ENCOR lab 9 of 36
OSPF summarisation, filtering and area types
Shrink Fernhill's OSPF tables with inter-area and external summaries, keep a lab network and a partner extranet where they belong with filters, and turn the regional areas into a totally stubby area and an NSSA.
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 09 - OSPF summarisation filtering and area types
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 6 vCPU, 3,584 MB
- Smallest plan
- Lite
The scenario
The multi-area OSPF design you built in lab 8 is live and has grown. Bristol (area 1) now has four /24 VLANs, Glasgow (area 2) has a test bench and a partner extranet reached over a partner circuit, and every new VLAN appears in every router's table. The core team wants smaller tables, faster SPF runs and less churn when a branch VLAN flaps:
- The core should see one route for Bristol's 10.20.0.0–10.20.3.0 and one for the partner extranet 172.16.0.0–172.16.3.0.
- The Glasgow test bench (10.30.99.0/24) must never leave area 2.
- R2 hosts the internet edge and must be the only source of the default route. It must also never use the partner extranet itself.
- Bristol's small router (R4) should hold only its own area plus a default route. Glasgow must keep importing the partner routes, so it can't simply be a stub area.
OSPF is already running exactly as at the end of lab 8, with the extra VLANs and statics added.
| Device | Role | Prefixes it owns |
|---|---|---|
| R1 | ABR area 0/1 | CORE 10.0.0.1, 10.0.14.1/30 |
| R2 | Area 0, DR, internet edge | 10.10.30.0/24 (HQ servers), CORE 10.0.0.2 |
| R3 | ABR area 0/2 | CORE 10.0.0.3, 10.0.35.1/30 |
| R4 | Area 1 (Bristol) | 10.20.0.0/24 (Gi0/2, PC1), 10.20.1.0/24, 10.20.2.0/24, 10.20.3.0/24 (Lo11–13) |
| R5 | Area 2 (Glasgow), ASBR | 10.30.10.0/24 (Lo10), 10.30.99.0/24 (Lo99, test bench), statics 172.16.0.0/24–172.16.3.0/24 |
| PC1 | Bristol staff PC | 10.20.0.10/24, gateway 10.20.0.1 |
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
- Summarise inter-area routes on an ABR with area range and explain the Null0 discard route
- Redistribute static routes on an ASBR and summarise them with summary-address
- Filter type 3 LSAs between areas with area filter-list, and filter the local RIB with distribute-list
- Configure stub, totally stubby and NSSA areas and predict what each router's table holds
- Originate a default route into OSPF and trace which LSA type carries it into each area
The tasks
- Take a baseline
- Summarise Bristol on the ABR
- Make R5 an ASBR and summarise the extranet
- Keep the test bench in Glasgow
- Stop R2 from using the extranet
- Originate the default route at the internet edge
- Turn Bristol into a totally stubby area and Glasgow into an NSSA
- Prove it still works
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
09 - OSPF summarisation filtering and area typesand 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
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.