Cisco Catalyst SD-WAN CLI lab 14 of 14
Capstone - a three-site rollout
Finish a three-site rollout on your own: hub and spoke between branches, application-aware routing to the data centre, direct internet at one branch and QoS at the other.
Run this lab
It needs Standard: its 9 nodes are set to 9 vCPU and 7,680 MB in total.
In your workspace: Shared, then Cisco Catalyst SD-WAN CLI guided labs, then 14 - Capstone - a three-site rollout
- Level
- Advanced
- Time
- About 120 minutes
- Nodes need
- 9 vCPU, 7,680 MB
- Smallest plan
- Standard
The scenario
Meridian's rollout closes this week. The data centre and two branches are on the overlay with both transports, and all that remains is the policy work, which is yours alone. The requirements below came out of the design review. No commands this time: everything here was covered in labs 03 to 10, and the hints and solution are there if you need them.
| Node | System IP | Site | INET (ge0/0) | MPLS (ge0/2) | LAN, VPN 10 (ge0/1) |
|---|---|---|---|---|---|
| DC1 | 10.255.0.10 | 10 | 198.51.100.10 | 172.16.0.10 | 10.10.10.1/24, H3 10.10.10.10 |
| BR1 | 10.255.0.11 | 11 | 198.51.100.11 | 172.16.0.11 | 10.11.10.1/24, H1 10.11.10.10 |
| BR2 | 10.255.0.12 | 12 | 198.51.100.12 | 172.16.0.12 | 10.12.10.1/24, H2 10.12.10.10 |
| WEB | 198.51.100.254, the provider gateway | public site on 203.0.113.80 |
vBond is 198.51.100.1 and vSmart is 198.51.100.2.
What this course leaves out. There is no SD-WAN Manager (vManage) in any of these labs. A virtual edge can't join the Manager's inventory without a signed device list from Cisco, which these labs don't have. So you won't see the Manager's GUI, dashboards, templates, Policy Builder or zero-touch onboarding. You work at the CLI of the controllers and edges, with a private lab CA and device lists typed by hand. The capstone is CLI only as well: no Manager templates and no Policy Builder. The hosts have fixed addresses set at boot, because the DHCP server on these vEdge images can lock up the edge at start-up.
What you’ll practise
- Combine control policy, app-route policy, DIA and QoS
- Check the result end to end
The tasks
- Start the lab
- Hub and spoke
- Application-aware routing to the data centre
- Direct internet access at Manchester
- QoS at Leeds
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
- vBond
ge0/0to INET (network) - vSmart
eth0to INET (network) - WEB
eth0to INET (network) - DC1
G0/0to INET (network) - BR1
G0/0to INET (network) - BR2
G0/0to INET (network) - DC1
G0/2to MPLS (network) - BR1
G0/2to MPLS (network) - BR2
G0/2to MPLS (network) - DC1
G0/1to H3eth0 - BR1
G0/1to H1eth0 - BR2
G0/1to H2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| vBond | Cisco vBond | vtbond-20.12.2 | 1 vCPU, 1,024 MB |
| vSmart | Cisco vSmart | vtsmart-20.12.2 | 1 vCPU, 1,024 MB |
| WEB | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 MB |
| DC1 | Cisco vEdge | vtedge-20.12.2 | 1 vCPU, 1,024 MB |
| BR1 | Cisco vEdge | vtedge-20.12.2 | 1 vCPU, 1,024 MB |
| BR2 | Cisco vEdge | vtedge-20.12.2 | 1 vCPU, 1,024 MB |
| H3 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 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
Cisco Catalyst SD-WAN CLI guided labs.Open
14 - Capstone - a three-site rolloutand 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 Cisco Catalyst SD-WAN CLI labs
All Cisco Catalyst SD-WAN CLI 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.