Arista EOS lab 5 of 20
Static routing and multi-area OSPF in a leaf-spine
Address a small routed leaf-spine from an addressing plan, connect it first with static routes, then replace them with OSPF: a point-to-point backbone, a non-backbone area on one leaf with a summary at the ABR, passive host interfaces, a default route from the spine and a floating static backup.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 7,168 MB in total. That fits the free demo too.
In your workspace: Shared, then Arista EOS guided labs, then 05 - Static routing and multi-area OSPF in a leaf-spine
- Level
- Intermediate
- Time
- About 75 minutes
- Nodes need
- 5 vCPU, 7,168 MB
- Smallest plan
- Lite
The scenario
Northwind is replacing its old layer 2 aggregation with a small routed leaf-spine: every leaf-to-spine link is a point-to-point layer 3 link and spanning tree disappears from the fabric. The design document says OSPF, with the backbone (area 0) on the fabric and the new analytics pod behind leaf2 in its own area 1, summarised so the rest of the network sees one route. The upstream internet edge (simulated by a loopback on spine1) must reach every host.
| Device | Interface | Address | Area / role |
|---|---|---|---|
| spine1 | Ethernet1 | 10.1.1.0/31 | 0 · to leaf1 |
| spine1 | Ethernet2 | 10.1.1.2/31 | 0 · to leaf2 |
| spine1 | Loopback0 | 10.255.0.1/32 | 0 · router ID |
| spine1 | Loopback100 | 203.0.113.1/32 | not in OSPF · simulated internet |
| leaf1 | Ethernet1 | 10.1.1.1/31 | 0 |
| leaf1 | Loopback0 | 10.255.0.11/32 | 0 · router ID |
| leaf1 | Vlan10 | 10.10.10.1/24 | 0 · passive · gateway for h1 |
| leaf2 | Ethernet1 | 10.1.1.3/31 | 0 |
| leaf2 | Loopback0 | 10.255.0.12/32 | 0 · router ID |
| leaf2 | Vlan20 | 10.20.20.1/24 | 1 · passive · gateway for h2 |
| leaf2 | Loopback21 | 10.20.21.1/24 | 1 · stands in for a second pod subnet |
| h1 / h2 | eth0 | 10.10.10.11/24 / 10.20.20.11/24 | hosts |
What you’ll practise
- Convert switch ports to routed /31 links and add loopbacks from an addressing plan
- Route between leaves with static routes and see why they don't scale
- Run OSPF with router IDs from loopbacks, passive interfaces and point-to-point network type
- Put one leaf's host subnets in area 1 and summarise them at the ABR
- Originate a default route into OSPF and back it up with a floating static route
The tasks
- Build the routed links and loopbacks
- Connect the leaves with static routes
- Bring up the OSPF backbone
- Make the fabric links point-to-point
- Add area 1 behind leaf2 and summarise it
- Default route from the spine, floating static as backup
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
- spine1
Ethernet1to leaf1Ethernet1 - spine1
Ethernet2to leaf2Ethernet1 - leaf1
Ethernet3to h1eth0 - leaf2
Ethernet3to h2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| spine1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| leaf1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| leaf2 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 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
Arista EOS guided labs.Open
05 - Static routing and multi-area OSPF in a leaf-spineand 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 Arista EOS labs
Related labs in other courses
CloudLabBox is independent of Arista Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.