Cisco Catalyst SD-WAN CLI lab 6 of 14
Data policy and traffic engineering
Write a centralised data policy on the vSmart that sends one application over MPLS, drops another and counts both, then read the proof on the WAN edge.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 5,120 MB in total. That fits the free demo too.
In your workspace: Shared, then Cisco Catalyst SD-WAN CLI guided labs, then 06 - Data policy and traffic engineering
- Level
- Advanced
- Time
- About 60 minutes
- Nodes need
- 6 vCPU, 5,120 MB
- Smallest plan
- Lite
The scenario
Both Meridian branches have internet and MPLS, and OMP shares traffic across both. The stock system at Leeds listens on TCP port 8080 and the business wants it on MPLS. Security wants Telnet (TCP 23) to the Leeds LAN blocked from Manchester. You do both with one centralised data policy, and you read the counters that prove it.
| Node | System IP | Site | INET (ge0/0) | MPLS (ge0/2) | LAN, VPN 10 (ge0/1) |
|---|---|---|---|---|---|
| BR1 | 10.255.0.11 | 11 | 198.51.100.11 | 172.16.0.11 | 10.11.10.1/24 |
| BR2 | 10.255.0.12 | 12 | 198.51.100.12 | 172.16.0.12 | 10.12.10.1/24 |
| H1, H2 | 10.11.10.10, 10.12.10.10, fixed |
vBond is 198.51.100.1 and vSmart is 198.51.100.2.
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 you'd build this policy in the Manager's Policy Builder. Here you write it on the vSmart CLI and read the counters at the CLI. 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
- Match traffic by prefix, protocol and port
- Steer it to a transport with set local-tloc
- Drop and count traffic, and read the counters on the edge
The tasks
- Start the lab
- Start a service at Leeds
- Write the data policy
- Generate traffic and read the counters
- Prove the transport
- Check nothing else broke
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/2to MPLS (network) - BR2
G0/2to MPLS (network) - BR1
G0/1to H1eth0 - BR2
G0/1to H2eth0
| 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 |
| H2 | Alpine Linux | clbalpinebase-alpine-base-3-20-3 | 1 vCPU, 512 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
06 - Data policy and traffic engineeringand 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.