zNetLaB › Guided labs › Telecom
SD-WAN — control plane, TLOCs and an OMP overlay
Telecom Advanced 9 devices 7 checked tasks 100 points Plan lab
Build a Viptela-style fabric: give every node a system-ip and a vBond, turn two WAN interfaces into TLOCs, and watch OMP carry the branch prefixes across an IPsec overlay. The underlay is already routed — the overlay is yours to bring up. 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
Build a Viptela-style fabric: give every node a system-ip and a vBond, turn two WAN interfaces into TLOCs, and watch OMP carry the branch prefixes across an IPsec overlay. The underlay is already routed — the overlay is yours to bring up.
Your role: a network engineer. Level: Advanced Done when: all 7 goals show as passed (100 points).
Network status
Devices: 2 PCs, 6 routers, 1 switch, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. Branch1-PC is a host with 10.1.10.10/24, gateway 10.1.10.1. Branch2-PC is a host with 10.2.10.10/24, gateway 10.2.10.1. Transport starts with addresses (G0/0 172.16.1.1/30, G0/1 172.16.2.1/30, G0/2 192.0.2.1/24). vBond starts with addresses (G0/0 192.0.2.10/24) and static routes already configured. vSmart starts with addresses (G0/0 192.0.2.20/24) and static routes already configured. vManage starts with addresses (G0/0 192.0.2.30/24) and static routes already configured. Branch1, Branch2, CtrlSW start with an empty configuration. 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
Both edges have a system-ip, a site-id and a vBond address (15 pts) Every node reaches vBond and joins the fabric (15 pts) Both edges hold a control connection to vSmart (15 pts) Each edge originates a TLOC on its WAN interface (15 pts) BFD is up between the two branches (15 pts) OMP carries the far branch LAN into VPN 10 (15 pts) Branch1-PC reaches Branch2-PC across the overlay (10 pts) The activity, in order
Both edges have a system-ip, a site-id and a vBond address Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Every node reaches vBond and joins the fabric Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Both edges hold a control connection to vSmart Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Each edge originates a TLOC on its WAN interface Why: Each goal is a state the lab can check on the running device. Verify with: show running-config BFD is up between the two branches Why: Each goal is a state the lab can check on the running device. Verify with: show running-config OMP carries the far branch LAN into VPN 10 Why: Each goal is a state the lab can check on the running device. Verify with: show running-config Branch1-PC reaches Branch2-PC across the overlay Why: A ping needs a route in BOTH directions. This is the end-to-end proof that everything before it worked. Verify with: ping 10.2.10.10 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
Build a Viptela-style fabric: give every node a system-ip and a vBond, turn two WAN interfaces into TLOCs, and watch OMP carry the branch prefixes across an IPsec overlay. The underlay is already routed — the overlay is yours to bring up.
What you will be able to do
Both edges have a system-ip, a site-id and a vBond address
Every node reaches vBond and joins the fabric
Both edges hold a control connection to vSmart
Each edge originates a TLOC on its WAN interface
The network
PC, cEdge ISR 1111, P Router, Switch 8-port, vBond, vSmart, vManage — 9 devices in all, already cabled.
Fa0 Gi0/0/0 Fa0 Gi0/0/0 Gi0/0/1 Gi0/0 172.16.1.1/30 Gi0/0/1 Gi0/1 172.16.2.1/30 Gi0/2 192.0.2.1/24 Fa0/1 Fa0/2 Gi0/0 192.0.2.10/24 Fa0/3 Gi0/0 192.0.2.20/24 Fa0/4 Gi0/0 192.0.2.30/24 Branch1-PC 10.1.10.10/24 · gw 10.1.10.1 Branch1 Branch2-PC 10.2.10.10/24 · gw 10.2.10.1 Branch2 Transport CtrlSW vBond vSmart vManage Drawn from this lab: devices, cables, ports and the addresses already set. Device Model Address already set
Branch1-PC PC 10.1.10.10 / 255.255.255.0 gw 10.1.10.1 Branch1 cEdge ISR 1111 configure it Branch2-PC PC 10.2.10.10 / 255.255.255.0 gw 10.2.10.1 Branch2 cEdge ISR 1111 configure it Transport P Router configure it CtrlSW Switch 8-port configure it vBond vBond configure it vSmart vSmart configure it vManage vManage configure it
Cabling
Branch1-PC Fa0 ↔ Branch1 Gi0/0/0 Branch2-PC Fa0 ↔ Branch2 Gi0/0/0 Branch1 Gi0/0/1 ↔ Transport Gi0/0 Branch2 Gi0/0/1 ↔ Transport Gi0/1 Transport Gi0/2 ↔ CtrlSW Fa0/1 CtrlSW Fa0/2 ↔ vBond Gi0/0 CtrlSW Fa0/3 ↔ vSmart Gi0/0 CtrlSW Fa0/4 ↔ vManage Gi0/0
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
Transport interface g0/0
ip address 172.16.1.1 255.255.255.252
no shutdown
interface g0/1
ip address 172.16.2.1 255.255.255.252
no shutdown
interface g0/2
ip address 192.0.2.1 255.255.255.0
no shutdown vBond interface g0/0
ip address 192.0.2.10 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 192.0.2.1 vSmart interface g0/0
ip address 192.0.2.20 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 192.0.2.1 vManage interface g0/0
ip address 192.0.2.30 255.255.255.0
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 192.0.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 Both edges have a system-ip, a site-id and a vBond address 15 Checked automatically against the device’s live state (sdwanId). and Checked automatically against the device’s live state (sdwanId). 2 Every node reaches vBond and joins the fabric 15 Checked automatically against the device’s live state (sdwanCtrl). and Checked automatically against the device’s live state (sdwanCtrl). and Checked automatically against the device’s live state (sdwanCtrl). and Checked automatically against the device’s live state (sdwanCtrl). 3 Both edges hold a control connection to vSmart 15 Checked automatically against the device’s live state (sdwanCtrl). and Checked automatically against the device’s live state (sdwanCtrl). 4 Each edge originates a TLOC on its WAN interface 15 Checked automatically against the device’s live state (sdwanTlocs). and Checked automatically against the device’s live state (sdwanTlocs). 5 BFD is up between the two branches 15 Checked automatically against the device’s live state (sdwanBfd). and Checked automatically against the device’s live state (sdwanBfd). 6 OMP carries the far branch LAN into VPN 10 15 Checked automatically against the device’s live state (sdwanRoute). and Checked automatically against the device’s live state (sdwanRoute). 7 Branch1-PC reaches Branch2-PC across the overlay 10 On Branch1-PC: ping 10.2.10.10 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:
Branch1 system
system-ip 1.1.1.1
site-id 100
organization-name znetlab
vbond 192.0.2.10
exit
interface g0/0/0
ip address 10.1.10.1 255.255.255.0
no shutdown
exit
interface g0/0/1
ip address 172.16.1.2 255.255.255.252
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 172.16.1.1
sdwan
vpn 10
interface g0/0/0
exit
interface g0/0/1
tunnel-interface
color mpls
exit
exit Branch2 system
system-ip 2.2.2.2
site-id 200
organization-name znetlab
vbond 192.0.2.10
exit
interface g0/0/0
ip address 10.2.10.1 255.255.255.0
no shutdown
exit
interface g0/0/1
ip address 172.16.2.2 255.255.255.252
no shutdown
exit
ip route 0.0.0.0 0.0.0.0 172.16.2.1
sdwan
vpn 10
interface g0/0/0
exit
interface g0/0/1
tunnel-interface
color mpls
exit
exit vBond system
system-ip 10.0.0.1
site-id 1
organization-name znetlab
vbond 192.0.2.10
exit vSmart system
system-ip 10.0.0.2
site-id 1
organization-name znetlab
vbond 192.0.2.10
exit vManage system
system-ip 10.0.0.3
site-id 1
organization-name znetlab
vbond 192.0.2.10
exit Where this is examined
This lab practises these topics in the zNetLaB certification courses:
Related labs
Where to start
The lessons all guided labs plans
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.