zNetLaB › Guided labs › Enterprise
SD-WAN control policy: isolate a site on vSmart
Enterprise Advanced 8 devices 3 checked tasks 100 points Plan lab
Build the same two-site fabric, then write a centralized control policy on vSmart that stops site 1 from learning the site 2 LAN, while the control plane stays 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 the same two-site fabric, then write a centralized control policy on vSmart that stops site 1 from learning the site 2 LAN, while the control plane stays up.
Your role: a network engineer on the enterprise team. Level: Advanced Done when: all 3 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, VB, VS, VM, E1, E2, R1, R2 start with an empty configuration.
Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure.
Goals
The fabric is up: edge 1 holds BFD to edge 2 (30 pts) vSmart holds the policy and applies it outbound (30 pts) Edge 1 no longer has the site 2 LAN, and R1 cannot reach R2 (40 pts)
The activity, in order
The fabric is up: edge 1 holds BFD to edge 2 Build the controllers, the edges and VPN 10 as in the fabric lab.Why: Each goal is a state the lab can check on the running device. Verify with: show sdwan bfd sessions vSmart holds the policy and applies it outbound On vSmart: policy, lists, a site-list SITE2 with site-id 2; a control-policy NO-SITE2 whose sequence 10 matches route from site-list SITE2 with action reject, and default-action accept; then apply-policy, site-list SITE2, control-policy NO-SITE2 out. Commit.Why: Each goal is a state the lab can check on the running device. Verify with: show running-config policy Edge 1 no longer has the site 2 LAN, and R1 cannot reach R2 With the policy applied the route is withdrawn from what vSmart sends, while BFD between the edges stays up.Why: Each goal is a state the lab can check on the running device. Verify with: show sdwan omp routes
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 the same two-site fabric, then write a centralized control policy on vSmart that stops site 1 from learning the site 2 LAN, while the control plane stays up.
What you will be able to do
The fabric is up: edge 1 holds BFD to edge 2
vSmart holds the policy and applies it outbound
Edge 1 no longer has the site 2 LAN, and R1 cannot reach R2
The network
Catalyst 9300-24, vBond, vSmart, vManage, cEdge ISR 1100-4G, Catalyst 8000V — 8 devices in all, already cabled.
Gi1/0/1 ge0/0 Gi1/0/2 eth0 Gi1/0/3 eth0 Gi1/0/4 Gi0/0/0 Gi1/0/5 Gi0/0/0 Gi1 Gi0/0/1 Gi1 Gi0/0/1 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
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
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 The fabric is up: edge 1 holds BFD to edge 2 30 On E1: show sdwan bfd sessions output matches 2\.2\.2\.2[\s\S]*up.
2 vSmart holds the policy and applies it outbound 30 On VS: show running-config apply-policy output matches control-policy NO-SITE2 out.
3 Edge 1 no longer has the site 2 LAN, and R1 cannot reach R2 40 On E1: show sdwan bfd sessions output matches 2\.2\.2\.2[\s\S]*up. and On E1: show sdwan omp routes output matches 192\.168\.2\.0 — it must not . and On R1: ping 192.168.2.5 must fail — the policy blocks it.
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:
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 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
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
VS config
policy
lists
site-list SITE2
site-id 2
exit
exit
control-policy NO-SITE2
sequence 10
match route
site-list SITE2
exit
action reject
exit
exit
default-action accept
exit
exit
apply-policy
site-list SITE2
control-policy NO-SITE2 out
commit and-quit
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