Hello,
vSmart advertise TLOCs, Service VPN Prefixes and Enforce Overlay Routing Policies to the Edges. The Edges advertise to the vSmarts 3 types of routes
- OMP routes: OMP Routes, also referred to as vRoutes, are prefixes learned at the local site via connected interfaces, static routes, and dynamic routing protocols (such as OSPF, EIGRP, and BGP) running on the service side of the vEdge. These prefixes are redistributed into OMP and advertised to the vSmart controller so that they can be carried across the overlay fabric to all other WAN edge nodes. OMP routes resolve their next-hop to a TLOC. An OMP route is installed in the forwarding table only if the next-hop TLOC is known and there is a BFD session in UP state associated with that TLOC;
- TLOC routes advertise Transport Locators of the connected WAN transports, along with additional attributes such as public and private IP addresses, color, TLOC preference, site ID, weight, tags, and encryption keys.
- Service routes advertise embedded network services such as firewalls and IPS that are connected to the vEdge local-site network
Think the vSmart as a Route Reflector, if an Edge has learned a new network on its LAN it will send OMP Updates to the vSmart and vSmart will send OMP Updates to rest of Edges from what TLOC IP this new network can be reached. This procedure is happening through the control tunnels.
Between the Edges you don't have control tunnels you have data tunnels and you don't exchange routes only data. This why if your fabric loose the control plane the data plane it still working.
I hope this sort explanation helped you.
Best Regards
Anestis
