CloudLabBox
Try the free demo

Cisco Catalyst SD-WAN CLI lab 2 of 14

WAN edge onboarding

Add two vEdge routers to a running control plane: enrol them, authorise them on the vBond and vSmart, and pass traffic through the first IPsec tunnel.

Run this lab

It needs Lite: its 6 nodes are set to 6 vCPU and 5,632 MB in total. That fits the free demo too.

In your workspace: Shared, then Cisco Catalyst SD-WAN CLI guided labs, then 02 - WAN edge onboarding

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 60 minutes
Nodes need
6 vCPU, 5,632 MB
Smallest plan
Lite

The scenario

The controllers from lab 01 are running. Now the first two branches join: Manchester (BR1, site 11) and Leeds (BR2, site 12). Both vEdge routers are unconfigured. You configure them, enrol them with the CA, authorise them on the controllers and pass the first real traffic across the overlay, from a PC at Manchester to the Leeds LAN gateway.

NodeRoleSystem IPSite IDInterfaceAddress
vBondValidator (ready)10.255.0.11000ge0/0198.51.100.1/24
vSmartController (ready)10.255.0.21000eth0198.51.100.2/24
CAEnterprise CA, on the management networketh010.254.0.50/24
BR1Manchester WAN edge10.255.0.1111ge0/0, VPN 0198.51.100.11/24
ge0/1, VPN 1010.11.10.1/24
eth0, VPN 51210.254.0.11/24
BR2Leeds WAN edge10.255.0.1212ge0/0, VPN 0198.51.100.12/24
loopback1, VPN 1010.12.10.1/24
eth0, VPN 51210.254.0.12/24
H1Manchester PCeth010.11.10.10/24, fixed, gateway BR1

Chassis numbers (a virtual router's identity, normally issued with your device list):

RouterChassis number
BR123329c4d-5dd7-5f1a-914c-9f0018b2c6b7
BR207a685c6-2ae7-59dd-8eb3-3d8921ba80ee

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. In production edges come from your Smart Account device list and onboard through PnP or zero-touch provisioning. Here you type each chassis and serial number on the controllers. 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

  • Configure a WAN edge for the overlay
  • Authorise chassis and certificate serial numbers
  • Verify control connections, BFD and traffic over the tunnel

The tasks

  1. Start the lab
  2. Configure the WAN edges
  3. Enrol the edges
  4. Authorise the edges
  5. Read the overlay
  6. Pass traffic

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 WAN edge onboarding6 nodes and 2 networks, 8 links. Every link is listed as text below the diagram.vBondvSmartBR1BR2CAH1INETMGMTeth0G0/1eth0ge0/0eth0eth0eth0G0/0G0/0
6 nodes and 2 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • vBond ge0/0 to INET (network)
  • vSmart eth0 to INET (network)
  • BR1 eth0 to MGMT (network)
  • BR2 eth0 to MGMT (network)
  • CA eth0 to MGMT (network)
  • BR1 G0/0 to INET (network)
  • BR2 G0/0 to INET (network)
  • BR1 G0/1 to H1 eth0
Nodes in WAN edge onboarding, 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
BR1Cisco vEdgevtedge-20.12.21 vCPU, 1,024 MB
BR2Cisco vEdgevtedge-20.12.21 vCPU, 1,024 MB
CAEVE-NG GUI server (Docker)eve-gui-server:latest1 vCPU, 1,024 MB
H1Alpine 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 02 - WAN edge onboarding 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.