zNetLaB › Guided labs › Enterprise
Troubleshoot: SD-WAN edge that will not join
Enterprise Advanced 8 devices 2 checked tasks 100 points Plan lab
Site 1 is on the fabric, site 2 is not: its edge has no control connection and the branches cannot talk. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Site 1 is on the fabric, site 2 is not: its edge has no control connection and the branches cannot talk.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 2 goals show as passed (100 points).
Network status
Devices: 1 switch, 7 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. WAN starts with addresses (G1/0/1 10.0.1.1/24, G1/0/2 10.0.2.1/24, G1/0/3 10.0.3.1/24, G1/0/4 10.0.4.1/24, G1/0/5 10.0.5.1/24). VB starts with and static routes already configured. VS starts with and static routes already configured. VM starts with and static routes already configured. E1 starts with addresses (G0/0/0 10.0.4.2/24, G0/0/1 192.168.1.1/24) and static routes already configured. E2 starts with addresses (G0/0/0 10.0.5.2/24, G0/0/1 192.168.2.1/24) and static routes already configured. R1 starts with addresses (G1 192.168.1.5/24) and static routes already configured. R2 starts with addresses (G1 192.168.2.5/24) and static routes already configured.
Known problems
The network worked and now does not: the scenario above says what users report. The cause is a configuration fault, not a cable. Find it with show commands (interfaces, routes, neighbours, running-config) before you change anything; fix only what is wrong.
Goals
Edge 2 has its control connection to vSmart up (50 pts) R1 reaches R2 (50 pts)
The activity, in order
Edge 2 has its control connection to vSmart up Edge 2 says organization-name ACME while the fabric is ORG. Set organization-name ORG under system.Why: Each goal is a state the lab can check on the running device. Verify with: show sdwan control connections R1 reaches R2 Once edge 2 joins, OMP brings the LAN over.Why: Each goal is a state the lab can check on the running device. Verify with: ping 192.168.2.5
Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong.
Why this matters
Site 1 is on the fabric, site 2 is not: its edge has no control connection and the branches cannot talk.
What you will be able to do
Edge 2 has its control connection to vSmart up
R1 reaches R2
The network
Catalyst 9300-24, vBond, vSmart, vManage, cEdge ISR 1100-4G, Catalyst 8000V — 8 devices in all, already cabled.
Gi1/0/1 10.0.1.1/24 ge0/0 Gi1/0/2 10.0.2.1/24 eth0 Gi1/0/3 10.0.3.1/24 eth0 Gi1/0/4 10.0.4.1/24 Gi0/0/0 10.0.4.2/24 Gi1/0/5 10.0.5.1/24 Gi0/0/0 10.0.5.2/24 Gi1 192.168.1.5/24 Gi0/0/1 192.168.1.1/24 Gi1 192.168.2.5/24 Gi0/0/1 192.168.2.1/24 WAN VB VS VM E1 E2 R1 R2 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
WAN Catalyst 9300-24 configure it
VB vBond configure it
VS vSmart configure it
VM vManage configure it
E1 cEdge ISR 1100-4G configure it
E2 cEdge ISR 1100-4G configure it
R1 Catalyst 8000V configure it
R2 Catalyst 8000V configure it
Cabling
WAN Gi1/0/1 ↔ VB ge0/0
WAN Gi1/0/2 ↔ VS eth0
WAN Gi1/0/3 ↔ VM eth0
WAN Gi1/0/4 ↔ E1 Gi0/0/0
WAN Gi1/0/5 ↔ E2 Gi0/0/0
R1 Gi1 ↔ E1 Gi0/0/1
R2 Gi1 ↔ E2 Gi0/0/1
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
WAN ip routing
interface GigabitEthernet1/0/1
no switchport
ip address 10.0.1.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet1/0/2
no switchport
ip address 10.0.2.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet1/0/3
no switchport
ip address 10.0.3.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet1/0/4
no switchport
ip address 10.0.4.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet1/0/5
no switchport
ip address 10.0.5.1 255.255.255.0
no shutdown
exit
VB config
system
system-ip 1.1.1.1
site-id 100
organization-name ORG
vbond 10.0.1.2 local
exit
vpn 0
interface ge0/0
ip address 10.0.1.2/24
no shutdown
exit
ip route 0.0.0.0/0 10.0.1.1
commit and-quit
VS config
system
system-ip 1.1.1.2
site-id 100
organization-name ORG
vbond 10.0.1.2
exit
vpn 0
interface eth0
ip address 10.0.2.2/24
no shutdown
exit
ip route 0.0.0.0/0 10.0.2.1
commit and-quit
VM config
system
system-ip 1.1.1.3
site-id 100
organization-name ORG
vbond 10.0.1.2
exit
vpn 0
interface eth0
ip address 10.0.3.2/24
no shutdown
exit
ip route 0.0.0.0/0 10.0.3.1
commit and-quit
E1 interface GigabitEthernet0/0/0
ip address 10.0.4.2 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/0/1
ip address 192.168.1.1 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 10.0.4.1
system
system-ip 2.2.2.1
site-id 1
organization-name ORG
vbond 10.0.1.2
exit
sdwan
interface GigabitEthernet0/0/0
tunnel-interface
color mpls
encapsulation ipsec
exit
vpn 10
interface GigabitEthernet0/0/1
exit
exit
E2 interface GigabitEthernet0/0/0
ip address 10.0.5.2 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/0/1
ip address 192.168.2.1 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 10.0.5.1
system
system-ip 2.2.2.2
site-id 2
organization-name ACME
vbond 10.0.1.2
exit
sdwan
interface GigabitEthernet0/0/0
tunnel-interface
color mpls
encapsulation ipsec
exit
vpn 10
interface GigabitEthernet0/0/1
exit
exit
R1 interface GigabitEthernet1
ip address 192.168.1.5 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 192.168.1.1
R2 interface GigabitEthernet1
ip address 192.168.2.5 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 192.168.2.1
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 Edge 2 has its control connection to vSmart up 50 On E2: show sdwan control connections output matches vsmart\s+dtls\s+1\.1\.1\.2[\s\S]*?up.
2 R1 reaches R2 50 On R1: ping 192.168.2.5 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
E2 system
organization-name ORG
exit
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.
Try the simulator in your browser, no sign-up