In the previous lesson, you learned what each SD-WAN component does.
Now it is time to see how they work together. Everything starts when a WAN Edge router powers on for the first time.
So what exactly happens during onboarding, and how does your router find the controllers?Step 1 — Contact vBond
A brand-new WAN Edge router knows only one thing: the IP address of vBond.
This address is either preconfigured in the bootstrap file or discovered automatically through Cisco PnP (Plug and Play).
Figure 1 — Step 1: the WAN Edge contacts vBond and authenticates using certificates
The WAN Edge initiates a DTLS connection to vBond over each available transport interface.
vBond authenticates the device using signed certificates and checks its serial number against the authorized device list.If the authentication succeeds, vBond sends back a list containing the IP addresses of vManage and vSmart.
This is the only role of vBond. Once it delivers the controller list, the DTLS connection is terminated.Answer the question below
Which controller is the only one a brand-new WAN Edge router knows at boot?
Step 2 — Connect to vManage
Now that your WAN Edge knows where vManage is, it establishes a permanent DTLS connection to it.
This connection uses a single transport interface, specifically the first one that connects successfully. vManage carries configuration and telemetry traffic, which does not require transport-level redundancy.
Figure 2 — Step 2: vBond redirects the WAN Edge to vManage, which pushes the configuration
Through this connection, vManage pushes the device configuration using NETCONF. This includes templates, policies, and VPN definitions.
The vManage connection remains active permanently. It is also used to collect statistics and telemetry from the WAN Edge.
Step 3 — Establish OMP with vSmart
The last step of the onboarding process is the most important one for routing.
The WAN Edge establishes a permanent DTLS connection to vSmart and starts an OMP (Overlay Management Protocol) session.
Figure 3 — Step 3: the WAN Edge establishes an OMP session with vSmart, while vManage stays connected
Unlike the vManage connection, your WAN Edge connects to vSmart over every available transport interface.
Because vSmart carries the routing information your WAN Edge needs to forward traffic, losing this connection on all transports would isolate the site. Multiple DTLS sessions provide control plane resiliency.
Through OMP, the WAN Edge sends its local routes and receives routes from all other sites.
Your WAN Edge is now part of the SD-WAN fabric.
To verify this, runshow control connectionson the WAN Edge:vEdge-Branch1# show control connections PEER PEER PEER SITE DOMAIN PEER PEER LOCAL TYPE PROTOCOL SYSTEM IP ID ID PRIVATE IP PORT COLOR STATE UPTIME ------------------------------------------------------------------------------------------------- vsmart dtls 10.10.10.1 - 1 10.10.10.1 12446 mpls up 0:07:22:15 vsmart dtls 10.10.10.1 - 1 10.10.10.1 12446 biz-internet up 0:07:22:12 vsmart dtls 10.10.10.1 - 1 10.10.10.1 12446 lte up 0:07:22:10 vmanage dtls 10.10.10.2 - 0 10.10.10.2 12646 mpls up 0:07:22:08The output confirms the three steps you just learned.
Three connections to vSmart (one per transport color: mpls, biz-internet, lte) and one connection to vManage.
All four are in state "up".
There is no permanent connection to vBond.
It completed its job during onboarding.Answer the question below
After onboarding, does the WAN Edge keep a permanent connection to vBond? (yes/no)
Answer the question below
A WAN Edge with four colors joins one vSmart, vManage and vBond: how many permanent DTLS connections?
Your WAN Edge is in the fabric and has an active OMP session with vSmart.
But how does routing actually work in SD-WAN?How vSmart Distributes Routes
In traditional networking, routers exchange routes directly with their neighbors using protocols like OSPF or BGP.
SD-WAN works differently. WAN Edge routers never exchange routes directly with each other.
Figure 4 — vSmart distributes routes to all WAN Edges via OMP sessions
Instead, every WAN Edge sends its local routes to vSmart via OMP.
vSmart acts as a centralized route reflector: it receives routes from all WAN Edges, applies policies, and reflects the filtered routes back to every other WAN Edge.This centralized model gives vSmart full control over what each WAN Edge knows about the network.
Note that OMP is a Cisco proprietary protocol, not defined by an RFC.Verifying OMP Routes
On the WAN Edge, run
show omp routes vpn 1to see the routes received from vSmart:vEdge-Branch1# show omp routes vpn 1 Code: C -> chosen, I -> installed, Red -> redistributed, Rej -> rejected L -> looped, R -> resolved, S -> stale, Ext -> extranet Inv -> invalid, Stg -> staged, U -> TLOC unresolved PATH ATTRIBUTE VPN PREFIX FROM PEER ID LABEL STATUS TYPE TLOC IP COLOR ENCAP --------------------------------------------------------------------------------------------------------- 1 10.10.10.0/24 0.0.0.0 1 1003 C,Red,R installed 1.1.1.1 mpls ipsec 1 10.20.20.0/24 10.10.10.1 2 1003 C,I,R installed 2.2.2.2 mpls ipsec 1 10.30.30.0/24 10.10.10.1 4 1003 C,I,R installed 3.3.3.3 biz-internet ipsecThe output confirms that your WAN Edge has learned routes to the two remote sites via OMP.
Every route comes from vSmart, not from another WAN Edge directly.The key takeaway: every route was received from vSmart. Your WAN Edge never exchanges routes directly with another WAN Edge.
Answer the question below
Which component acts as a centralized route reflector in SD-WAN?
Your WAN Edge has routes to every remote site. But routes alone do not carry user traffic.
The data plane is what actually moves packets between sites.The Underlay
The underlay is the physical transport: your MPLS circuits, your broadband Internet connections, your 4G/5G links.
These are the networks provided by your service providers. Each WAN Edge connects to one or more of these transports.
Figure 5 — The underlay: all sites connect to the physical transports
The underlay provides basic IP connectivity between sites. But it does not provide any encryption, any traffic engineering, or any awareness of your enterprise network.
That is where the overlay comes in.Building the Overlay
The overlay is a layer of encrypted IPsec tunnels built automatically between WAN Edges.
These tunnels run on top of the underlay.How do WAN Edges know where to build these tunnels? The answer is OMP.

Figure 6 — IPsec tunnels are built automatically between WAN Edges
When vSmart distributes routes, it also distributes the transport location information for each WAN Edge.
The WAN Edges use this information to establish IPsec tunnels with each other automatically.
Figure 7 — The complete picture: the overlay runs on top of the underlay
You do not configure these tunnels manually. The overlay builds itself.
User traffic is always encapsulated inside an IPsec tunnel. It never touches the underlay directly.Answer the question below
Are IPsec tunnels between WAN Edges configured manually or built automatically?
Verifying the Tunnels
SD-WAN uses BFD (Bidirectional Forwarding Detection) (RFC 5880) to monitor every IPsec tunnel.
BFD sends control packets at regular intervals to detect if a tunnel goes down.Run
show bfd sessionson the WAN Edge to see all active tunnels:vEdge-Branch1# show bfd sessions DST PUBLIC DST PUBLIC DETECT TX SYSTEM IP SITE ID STATE COLOR SOURCE IP IP PORT ENCAP MULTI INTERVAL UPTIME PLIER (msec) --------------------------------------------------------------------------------------------------------- 2.2.2.2 200 up mpls 10.1.1.1 10.1.2.1 12386 ipsec 7 1000 0:02:48:55 2.2.2.2 200 up biz-internet 172.16.1.1 172.16.2.1 12386 ipsec 7 1000 0:02:48:52 2.2.2.2 200 up lte 100.64.1.1 100.64.2.1 12386 ipsec 7 1000 0:02:48:50 3.3.3.3 300 up mpls 10.1.1.1 10.1.3.1 12386 ipsec 7 1000 0:02:48:48 3.3.3.3 300 up biz-internet 172.16.1.1 172.16.3.1 12386 ipsec 7 1000 0:02:48:45 3.3.3.3 300 up lte 100.64.1.1 100.64.3.1 12386 ipsec 7 1000 0:02:48:42Your WAN Edge has six active tunnels: three to site 200 and three to site 300, one per transport color. All sessions are up with IPsec encapsulation.
If a transport goes down, the BFD session detects it and traffic shifts to the remaining tunnels automatically.Answer the question below
What protocol does SD-WAN use to monitor the health of IPsec tunnels?
The End-to-End Packet Flow
Now let's follow a packet from end to end.
A user at Branch 1 sends traffic to Branch 2. Here is what happens:
Figure 8 — End-to-end: a packet travels through the overlay from Branch 1 to Branch 2
The user's packet arrives at the WAN Edge at Branch 1. The WAN Edge looks up the destination in its routing table and finds an OMP route pointing to the WAN Edge at Branch 2.
The WAN Edge encapsulates the original packet inside an IPsec tunnel header and sends it into the underlay.
The encapsulated packet travels through the underlay (Internet or MPLS) like any other IP packet. The service provider has no visibility into the original content.
The WAN Edge at Branch 2 receives the encapsulated packet, decapsulates it, and delivers the original packet to its destination.
From the user's perspective, the tunnel is invisible. Traffic flows between Branch 1 and Branch 2 as if they were on the same private network.
This is the power of SD-WAN: a secure, automated overlay that abstracts the complexity of the underlying transports.Answer the question below
What does the WAN Edge do to a user packet before sending it into the underlay?