Before you understand SD-WAN, you need to see the problem it solves.
For decades, enterprise WANs have followed a straightforward model: lease MPLS circuits from a service provider, connect every site to the same private network, and manage each router individually through CLI.This model worked well when most traffic stayed inside the enterprise.
But the world has changed.MPLS Only
In a traditional WAN, your Headquarters (HQ) and branch sites connect through MPLS circuits leased from one or more service providers.
MPLS (Multiprotocol Label Switching, a private WAN service leased from a carrier) provides reliable connectivity with built-in QoS guarantees, but it comes at a high price per megabit.
Figure 1 – Traditional WAN: every site depends on expensive MPLS circuits
Every site needs its own MPLS circuit. Adding a new branch means ordering a new line from the provider, which can take weeks or months.
And MPLS is the only transport option. There is no failover, no alternative path, and no way to leverage cheaper broadband Internet.Answer the question below
What is the main drawback of MPLS circuits?
The Backhauling Problem
Today, most enterprise applications live in the cloud: Microsoft 365, Salesforce, AWS, Webex.
Your users at branch sites need fast, direct access to these services.But in a traditional WAN, branches have no direct Internet exit. All traffic must travel back to HQ through MPLS, exit to the Internet at the HQ firewall, and then reach the cloud.
This is called backhauling.
It adds latency, wastes expensive MPLS bandwidth, and overloads the HQ router with traffic it should never handle.
Figure 2 – Backhauling: branch traffic takes a detour through HQ to reach cloud applications
A user at Branch 2 wants to access Microsoft 365. Instead of going directly to the cloud, the traffic follows a two-step detour: first through MPLS to HQ, then out to the Internet.
SD-WAN exists to eliminate this problem.Answer the question below
What is the term for routing cloud traffic through the headquarters instead of sending it directly to the Internet?
SD-WAN (Software-Defined Wide Area Network) solves these problems by introducing two major changes: multiple transports instead of MPLS only, and a centralized controller architecture instead of box-by-box management.
Let’s build this architecture step by step.Multiple Transports
With SD-WAN, your sites are no longer limited to MPLS.
Each site can connect through any combination of transports: MPLS, broadband Internet, 4G/5G, or even satellite.
Figure 3 – Multiple transports: sites connect through MPLS, Internet, and 4G/5G simultaneously
This changes the economics of your WAN completely. You can use a cheap Internet link for bulk traffic and keep MPLS for critical applications.
If one transport fails, traffic automatically shifts to another.But using multiple transports creates a new challenge. How do your routers know which path to use? Who coordinates all of this?
That is where the SD-WAN components come in.Answer the question below
With SD-WAN, if one transport fails, traffic automatically ______ to another.
WAN Edge – The Site Router
At every site, the traditional router is replaced by a WAN Edge router (also called vEdge or cEdge).
This is the device that sits at the boundary of your site and connects to the available transports.
Figure 4 – WAN Edge routers deployed at every site, but what controls them?
If you SSH into a WAN Edge router, it looks familiar. Run
show system statusto see its identity:vEdge# show system status Personality: vEdge Model name: vEdge-Cloud Services: None vBond: 10.0.0.1 Site ID: 100 System IP: 1.1.1.1 Board Type: Virtual Chassis Number: abc12345-1234-1234-1234-abc123456789The Personality field confirms this is a vEdge device. Each WAN Edge has a unique System IP and belongs to a specific Site ID.
Your WAN Edge routers are in place. But they need something above them to coordinate routing, enforce policies, and manage the overlay.
What are those components in the cloud? Let’s reveal them one by one.Answer the question below
In SD-WAN, what device replaces the traditional router at each site?
vSmart – The Control Plane
Your WAN Edge routers are connected, but they have no idea how to reach each other's networks. They need a brain to coordinate routing across the entire fabric.
vSmart distributes routing information to all WAN Edge routers using a protocol called OMP (Overlay Management Protocol). It acts as a centralized route reflector: every WAN Edge sends its routes to vSmart, and vSmart reflects them to all other WAN Edges after applying policies.

Figure 5 – vSmart revealed: the control plane controller that distributes routes via OMP
On the vSmart controller, run
show omp peersto see which WAN Edges are connected:vSmart# show omp peers DOMAIN OVERLAY SITE PEER TYPE ID ID ID STATE -------------------------------------------------------------------------- 1.1.1.1 vedge 1 1 100 up 2.2.2.2 vedge 1 1 200 up 3.3.3.3 vedge 1 1 300 upEvery WAN Edge appears as an OMP peer with state "up". This confirms that vSmart has established control connections with all three sites.
WAN Edge routers never exchange routes directly with each other. All routing intelligence flows through vSmart.vManage – The Management Plane
The next component is vManage, your centralized dashboard.
vManage provides the web-based GUI where you configure device templates, monitor the health of your fabric, push policies, and troubleshoot issues.
It also exposes a REST API for automation and integration with third-party tools.
Figure 6 – vManage revealed: the management plane dashboard for configuration and monitoring
With vManage, you no longer need to SSH into each router individually.
A single template change can be pushed to hundreds of WAN Edge routers simultaneously. This is what makes SD-WAN software-defined: the control is centralized, not distributed across individual boxes.Answer the question below
Which SD-WAN component provides the centralized GUI for configuration and monitoring?
vBond – The Orchestration Plane
There is still one missing piece in the architecture: vBond, the orchestrator.
When a new WAN Edge router powers on for the first time, it has no idea where vManage or vSmart are located.
vBond is the first point of contact for any device joining the SD-WAN fabric.
Figure 7 – vBond revealed: the orchestrator that authenticates and onboards new devices
vBond authenticates the new device using signed certificates, then tells it how to reach vManage and vSmart.
Runshow orchestrator connectionson the vBond to see which devices have been onboarded:vBond# show orchestrator connections PEER PEER PEER TYPE PROTOCOL SITE SYSTEM PRIVATE PUBLIC ID IP IP IP ------------------------------------------------------------------------ 1.1.1.1 vedge dtls 100 1.1.1.1 - - 2.2.2.2 vedge dtls 200 2.2.2.2 - - 10.10.10.1 vsmart dtls - 10.10.10.1 - - 10.10.10.2 vmanage dtls - 10.10.10.2 - -The output shows all devices that have been authenticated: two vEdge routers, one vSmart, and one vManage.
Once the initial handshake is complete, the WAN Edge establishes permanent connections to vManage and vSmart directly. vBond steps back and is only needed again when a new device joins.vAnalytics – Visibility and Insights
Your fabric is running. Devices are onboarded, routes are distributed, policies are enforced. One last component completes the architecture.
vAnalytics collects telemetry data from all WAN Edge routers and provides application-level reporting, performance trends, and capacity planning insights.
Figure 8 – vAnalytics revealed: visibility, reporting, and application performance insights
Unlike the other components, vAnalytics is accessed entirely through a web dashboard integrated with vManage.
There is no CLI interface for vAnalytics.Answer the question below
Which SD-WAN component is the first point of contact for a new WAN Edge router joining the fabric?
Answer the question below
12 sites with one WAN Edge each and one vSmart: how many OMP peers does a WAN Edge have?
Now that you know each component, let’s put them all together.
All Components in Place

Figure 9 – The complete Cisco SD-WAN architecture
Here is how the five components work together:
vBond authenticates new devices and tells them where to find the controllers
vManage pushes configuration and monitors the fabric
vSmart distributes routes and enforces policies via OMP
WAN Edge routers sit at each site and carry user traffic across the available transports
vAnalytics collects telemetry and reports on application performance
What Comes Next
You now know the five components of the Cisco SD-WAN architecture and the role each one plays.
But knowing the components is only the beginning.How does a WAN Edge router actually join the fabric? How does vSmart distribute routes using OMP? How are IPsec tunnels formed automatically between sites? What happens when a transport link goes down?
The next lesson takes you inside How SD-WAN Works and shows you exactly how they orchestrate together to build and operate the overlay.Answer the question below
How many components make up the Cisco SD-WAN architecture?