Aruba CX lab 6 of 16
OSPF from one area to a multi-area campus
Route a three-switch campus with OSPFv2 on AOS-CX: point-to-point backbone links with authentication, passive user interfaces, a second area summarised at its ABR, a totally stubby area that only needs a default route, and a default route from the core.
Run this lab
It needs Standard: its 5 nodes are set to 8 vCPU and 10,240 MB in total.
In your workspace: Shared, then HPE Aruba Networking CX switching guided labs, then 06 - OSPF from one area to a multi-area campus
- Level
- Intermediate
- Time
- About 75 minutes
- Nodes need
- 8 vCPU, 10,240 MB
- Smallest plan
- Standard
The scenario
Northwind's campus has a core switch (core1) and two distribution blocks: dist1 for the office (area 1) and dist2 for a small depot (area 2) that only needs a way out, not the whole routing table. The addressing is done. Build OSPF to the design, so that the core's table stays small, the depot switch carries almost nothing, and nobody can inject routes on the backbone without the key.
| Device | Router ID (loopback 0) | Interfaces and areas |
|---|---|---|
| core1 | 10.255.0.1 | 1/1/1 10.0.1.1/30 area 0 · 1/1/2 10.0.2.1/30 area 2 · loopback 0 area 0 · loopback 1 203.0.113.1 (not in OSPF) |
| dist1 | 10.255.0.11 | 1/1/1 10.0.1.2/30 area 0 · loopback 0 area 0 · vlan 10 10.1.10.1/24 area 1 · loopback 1 10.1.11.1/24 area 1 |
| dist2 | 10.255.0.12 | 1/1/1 10.0.2.2/30 area 2 · loopback 0 area 2 · vlan 20 10.2.20.1/24 area 2 |
| h1 / h2 | – | 10.1.10.11/24 via .1 · 10.2.20.12/24 via .1 |
Backbone authentication: MD5, key ID 1, key NWospf1.
What you’ll practise
- Enable OSPF per interface with ip ospf, using loopback router IDs
- Use point-to-point network type on routed links and passive user interfaces
- Build a multi-area design and identify ABRs and LSA types in the routing table
- Summarise an area at its ABR with area range
- Configure a totally stubby area and originate a default route
- Authenticate OSPF on the backbone with MD5
The tasks
- Start OSPF in one area
- Point-to-point links and passive user interfaces
- Go multi-area
- Summarise area 1
- A totally stubby area and a default route
- Authenticate the backbone
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
- core1
1/1/1to dist11/1/1 - core1
1/1/2to dist21/1/1 - dist1
1/1/2to h1eth0 - dist2
1/1/2to h2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| core1 | Aruba AOS-CX virtual switch | arubacx-10.14 | 2 vCPU, 3,072 MB |
| dist1 | Aruba AOS-CX virtual switch | arubacx-10.14 | 2 vCPU, 3,072 MB |
| dist2 | Aruba AOS-CX virtual switch | arubacx-10.14 | 2 vCPU, 3,072 MB |
| h1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| h2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 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
HPE Aruba Networking CX switching guided labs.Open
06 - OSPF from one area to a multi-area campusand 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 Aruba CX labs
Related labs in other courses
CloudLabBox is independent of Hewlett Packard Enterprise. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.