CloudLabBox
Try the free demo

Cisco Catalyst SD-WAN CLI lab 3 of 14

OMP and TLOCs

Add a second transport to a formed overlay, read how OMP advertises TLOCs and routes, and steer traffic with TLOC preference.

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 03 - OMP and TLOCs

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 60 minutes
Nodes need
6 vCPU, 5,120 MB
Smallest plan
Lite

The scenario

Manchester and Leeds are on the overlay over the internet. Both sites also have an old MPLS circuit, which Meridian wants to keep for its guaranteed bandwidth. You add MPLS as a second transport, read how OMP describes the two paths, and make the overlay prefer MPLS.

NodeSystem IPSiteINET (ge0/0)MPLS (ge0/2)LAN, VPN 10 (ge0/1)
vBond10.255.0.11000198.51.100.1
vSmart10.255.0.21000198.51.100.2 (eth0)
BR110.255.0.1111198.51.100.11172.16.0.11/2410.11.10.1/24
BR210.255.0.1212198.51.100.12172.16.0.12/2410.12.10.1/24
H110.11.10.10, fixed
H210.12.10.10, fixed

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 these transport settings come from the Manager's VPN interface templates. 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

  • Add an MPLS transport with restrict and no control connections
  • Read TLOCs and OMP routes
  • Prefer a transport with TLOC preference

The tasks

  1. Start the lab
  2. Read what OMP knows today
  3. Add the MPLS transport
  4. Read two paths
  5. Prefer MPLS
  6. Prove traffic still flows

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.

Topology of OMP and TLOCs6 nodes and 2 networks, 8 links. Every link is listed as text below the diagram.vBondvSmartBR1BR2H1H2INETMPLSG0/1eth0G0/1eth0ge0/0eth0G0/2G0/2G0/0G0/0
6 nodes and 2 networks, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • vBond ge0/0 to INET (network)
  • vSmart eth0 to INET (network)
  • BR1 G0/0 to INET (network)
  • BR2 G0/0 to INET (network)
  • BR1 G0/2 to MPLS (network)
  • BR2 G0/2 to MPLS (network)
  • BR1 G0/1 to H1 eth0
  • BR2 G0/1 to H2 eth0
Nodes in OMP and TLOCs, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
vBondCisco vBondvtbond-20.12.21 vCPU, 1,024 MB
vSmartCisco vSmartvtsmart-20.12.21 vCPU, 1,024 MB
BR1Cisco vEdgevtedge-20.12.21 vCPU, 1,024 MB
BR2Cisco vEdgevtedge-20.12.21 vCPU, 1,024 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
H2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Cisco Catalyst SD-WAN CLI guided labs.

  3. Open 03 - OMP and TLOCs and 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.