Cisco Catalyst SD-WAN CLI lab 11 of 14
Troubleshoot control connections
The new branches never joined the overlay. Find four faults with the control-connection history and its error codes, and fix each one.
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 11 - Troubleshoot control connections
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 6 vCPU, 5,632 MB
- Smallest plan
- Lite
The scenario
A contractor configured the Manchester and Leeds routers last night and left. Neither branch has joined the overlay, and the ticket says only "it doesn't work". There are four separate faults on the devices. Your tool is the history of failed connections: each failure leaves an error code, and each code points at one thing.
| Node | System IP | Site | INET | Other |
|---|---|---|---|---|
| vBond | 10.255.0.1 | 1000 | 198.51.100.1 | |
| vSmart | 10.255.0.2 | 1000 | 198.51.100.2 | |
| BR1 | 10.255.0.11 | 11 | 198.51.100.11 | LAN ge0/1 10.11.10.1/24, H1 10.11.10.10; VPN 512 eth0 10.254.0.11/24 |
| BR2 | 10.255.0.12 | 12 | 198.51.100.12 | loopback1 10.12.10.1/24 in VPN 10 |
| CA | 10.254.0.50/24 on the management network |
The organisation name is MeridianFoods. CA works as in labs 01 and 02: user ca, password Cl@ssLab1, and it signs anything dropped into /home/ca/incoming, numbering from 5001.
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. You diagnose from the CLI only. The Manager's alarms, events and device views aren't here. 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
- Read show control connections-history and its error codes
- Compare local properties with the authorised lists
- Fix identity, reachability and list faults
The tasks
- Start the lab
- Learn the method
- Leeds can't find anyone
- The vBond turns Leeds away
- Manchester's organisation
- Update the lists
- Prove the overlay
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) - BR1
G0/0to INET (network) - BR2
G0/0to INET (network) - BR1
G0/1to H1eth0 - BR1
eth0to MGMT (network) - CA
eth0to MGMT (network)
| 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 |
| BR1 | Cisco vEdge | vtedge-20.12.2 | 1 vCPU, 1,024 MB |
| BR2 | Cisco vEdge | vtedge-20.12.2 | 1 vCPU, 1,024 MB |
| H1 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 MB |
| CA | EVE-NG GUI server (Docker) | eve-gui-server:latest | 1 vCPU, 1,024 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
11 - Troubleshoot control connectionsand 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.