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

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 9 vCPU and 7,680 MB together. Every lab plan includes every guided lab.

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.

NodeSystem IPSiteINET (ge0/0)MPLS (ge0/2)LAN, VPN 10 (ge0/1)
DC110.255.0.1010198.51.100.10172.16.0.1010.10.10.1/24, H3 10.10.10.10
BR110.255.0.1111198.51.100.11172.16.0.1110.11.10.1/24, H1 10.11.10.10
BR210.255.0.1212198.51.100.12172.16.0.1210.12.10.1/24, H2 10.12.10.10
WEB198.51.100.254, the provider gatewaypublic 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

  1. Start the lab
  2. Hub and spoke
  3. Application-aware routing to the data centre
  4. Direct internet access at Manchester
  5. 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.

Topology of Capstone - a three-site rollout9 nodes and 2 networks, 12 links. Every link is listed as text below the diagram.vBondvSmartWEBDC1BR1BR2H3H1H2INETMPLSG0/0G0/1eth0G0/1eth0G0/1eth0ge0/0eth0G0/2G0/2G0/2G0/0G0/0eth0
9 nodes and 2 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in Capstone - a three-site rollout, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
vBondCisco vBondvtbond-20.12.21 vCPU, 1,024 MB
vSmartCisco vSmartvtsmart-20.12.21 vCPU, 1,024 MB
WEBEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
DC1Cisco vEdgevtedge-20.12.21 vCPU, 1,024 MB
BR1Cisco vEdgevtedge-20.12.21 vCPU, 1,024 MB
BR2Cisco vEdgevtedge-20.12.21 vCPU, 1,024 MB
H3Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
H2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Cisco Catalyst SD-WAN CLI guided labs.

  3. Open 14 - Capstone - a three-site rollout and 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.