Introduction
Cisco Viptela
SD-WAN solution builds a full-mesh topology between vEdge devices by default
when there are no Control Policies implemented. This means that vEdges tries to
build an IPSec/GRE tunnel to every reachable TLOC public IP addresses no matter
which site or color (transport network) TLOCs belong to. We have already change
the default behavior by using the restrict
option (chapter 2) under tunnel interfaces. In this way, tunnels are only
established between TLOCs belonging to the same color. In this chapter, we are
going to create a Hub and Spoke topology by implementing a Control Policy where
the vSmart advertises TLOC/OMP routes from site 30 to sites 10 and 20 and
TLOC/OMP routes from sites 10 and 20 to site 30. vSmart doesn’t advertise
TLOC/OMP routes between sites 10 and 20. Site 10 and 20 will be our
Branch/Remote sites and site 30 will be the Hub/DataCenter site.
Figure 5-1
recaps the operation of the Overlay Management Protocol (OMP). vEdge1 in site
10 advertises TLOC route advertisement to vSmart where it describes its System
Id, transport color, and encapsulation method as well as Public/Private IP and
restricts attributes (among several other attributes). vSmart forwards TLOC
routes received from vEdge1 to both vEdge2 (site 20) and vEdge3 (site 30). vEdge1
also advertises OMP routes where it describes the reachability information
about its local subnet 172.16.10.0/24 bound to VPN10.
Figure 5-1: TLOC Route advertisement.
