SD-WAN Overview

1. What Is SD-WAN and Why Was It Created?

SD-WAN (Software-Defined Wide Area Networking) is a technology approach that applies software-defined networking (SDN) principles to the enterprise WAN. It decouples the WAN's control plane (routing decisions, policy, management) from the data plane (packet forwarding), centralising intelligence in a software controller while allowing edge devices to forward traffic over any available transport — MPLS, broadband internet, LTE/5G, or satellite — simultaneously.

SD-WAN emerged as a direct response to the limitations of traditional MPLS-centric WAN architectures in a world where cloud computing, SaaS applications, and mobile workforces have fundamentally changed where enterprise traffic goes. In the early 2000s, most enterprise traffic stayed inside the corporate network — MPLS was ideal. By the mid-2010s, 60–80% of enterprise traffic was destined for the internet and cloud, yet WAN architecture still forced all branch traffic through the corporate data centre before reaching the internet — adding latency, consuming expensive MPLS bandwidth, and creating a bottleneck.

Problem with Traditional WAN	SD-WAN Solution
High MPLS cost for growing bandwidth needs	Use cheap broadband internet alongside (or replacing) MPLS; significant cost reduction
All traffic backhauled through HQ before reaching cloud/internet	Direct cloud breakout from branches — SaaS traffic goes directly to the internet from the branch
Manual per-device CLI configuration for each branch router	Centralised policy management via GUI/API; zero-touch provisioning for new branches
Static routing decisions — no awareness of real-time link quality	Application-aware routing with real-time path selection based on measured latency, jitter, and loss
Internet transport is insecure — no native encryption	Built-in IPsec encryption on all overlay tunnels, regardless of transport
Weeks to provision a new branch circuit	Zero-touch provisioning — a new branch can join the fabric in hours, not weeks
Single-vendor, single-transport lock-in	Transport-agnostic — mix any combination of transports and switch providers freely

2. Traditional WAN vs SD-WAN — Side by Side

Understanding the limitations of traditional WAN architecture is the key to appreciating what SD-WAN changes. The comparison below covers the most important dimensions.

Dimension	Traditional WAN (MPLS-centric)	SD-WAN
Transport	Single provider MPLS circuit per site	Any transport: MPLS + internet + LTE simultaneously
Control plane	Distributed — each router runs its own routing protocol (OSPF, BGP) independently	Centralised — SD-WAN controller (vSmart) distributes policy to all edge devices
Configuration	Per-device CLI configuration — every router configured individually	Centralised GUI/API (vManage) — policies defined once, pushed to all devices
New branch provisioning	Weeks — MPLS circuit order, physical installation, manual CLI configuration	Hours — zero-touch provisioning; device connects and auto-downloads configuration
Internet/cloud access	Branch traffic backhauled through HQ (data centre) then out to internet — adds 30–100+ ms latency to cloud apps	Direct cloud breakout — branch sends SaaS/internet traffic directly to internet; HQ traffic stays on MPLS/SD-WAN fabric
Path selection	Static or protocol-based (OSPF metric, BGP) — no real-time awareness of jitter or loss	Real-time per-path measurement (BFD) — routes traffic based on measured latency, jitter, loss per application
Security	MPLS is logically private but unencrypted; internet requires separate IPsec VPN infrastructure	Built-in IPsec on all paths — internet and MPLS both encrypted in the overlay; integrated next-gen firewall available on some platforms
Visibility	Limited — per-device logs and SNMP polling; no application-level visibility	Centralised application-level telemetry — see which apps use which paths in real time
Cost	High MPLS circuit costs; expensive to scale bandwidth	Lower — cheap broadband for bulk traffic; MPLS only where QoS SLA is needed

3. Overlay and Underlay — The Core Concept

The single most important conceptual distinction in SD-WAN is the separation between underlay and overlay networks. Understanding this split explains how SD-WAN achieves transport-independence.

3.1 Underlay — The Physical Transport

The underlay is the physical or logical network that provides raw IP connectivity between SD-WAN edge devices. The underlay can be any combination of transport technologies — MPLS, broadband internet, LTE/5G, satellite, or Metro Ethernet. SD-WAN does not care what the underlay is; it uses whatever is available to build the overlay.

3.2 Overlay — The SD-WAN Fabric

The overlay is a virtual network of IPsec-encrypted tunnels that SD-WAN edge devices (vEdge / cEdge) build on top of all available underlay transports. The overlay creates a full-mesh (or hub-and-spoke) logical topology of encrypted tunnels between all sites — regardless of which underlay each tunnel uses. Applications and routing policies operate on the overlay; the underlay is invisible to them.

Concept	Underlay	Overlay
What it is	Physical/logical transport infrastructure	Virtual encrypted tunnel network built on top
Examples	MPLS, internet DSL, LTE, satellite	IPsec tunnels, OMP routes, BFD sessions
Who sees it	vEdge device — uses underlay for tunnel endpoints	Applications, policies, routing — operate on overlay
Routing	Standard IP routing (BGP, OSPF, static) to reach far-end vEdge IPs	OMP distributes overlay routes; application policies steer traffic
Security	May be unencrypted (internet) or logically private (MPLS)	Always encrypted — all overlay tunnels use IPsec

4. Cisco SD-WAN / Viptela Architecture

Cisco's SD-WAN solution is based on technology acquired from Viptela in 2017. It uses a set of clearly defined components — each with a distinct role — that together form the complete SD-WAN fabric. Understanding these components and their interactions is essential for the CCNA and CCNP Enterprise exams.

5. The Four SD-WAN Planes and Their Components

5.1 vManage — Management Plane

vManage is the centralised network management system (NMS) and orchestration platform for the entire SD-WAN fabric. It is the single pane of glass through which administrators define policies, monitor the network, and manage all devices. All configuration and policy changes flow from vManage to the rest of the fabric.

vManage Function	Description
Centralised GUI dashboard	Web-based interface showing real-time topology, device health, tunnel status, and application performance across all sites
REST API	Northbound API for integration with ITSM tools (ServiceNow), automation platforms, and custom scripts (Python, Ansible)
Policy definition	Centralised point for all data plane policies — QoS, application routing, security, AAR (Application-Aware Routing) rules
Device templates	Configuration templates pushed to vEdge/cEdge devices; separates device-specific variables from policy structure
Software upgrades	Centralised IOS XE / vEdge software image management across all WAN edge devices
Telemetry and alerts	Real-time streaming telemetry from all vEdge devices; configurable alerts for link failures, SLA violations, security events

5.2 vSmart — Control Plane

vSmart is the centralised control plane controller. It runs OMP (Overlay Management Protocol) — the SD-WAN fabric's own routing protocol — communicating with all vEdge devices over TLS-secured connections. vSmart is responsible for distributing routes, keys, and policies to every edge device, making the path-selection intelligence centralised rather than distributed.

5.3 vBond — Orchestration Plane

vBond is the orchestrator — the first component a new SD-WAN edge device contacts when it boots for the first time. vBond authenticates the device's certificate, discovers its public IP address (important for NAT traversal), and tells it the IP addresses of the vSmart controllers to connect to. Once initial orchestration is complete, vBond is no longer in the regular data or control path.

5.4 vEdge / cEdge — Data Plane

vEdge routers are Viptela's original purpose-built hardware and virtual SD-WAN edge devices. cEdge routers are Cisco IOS XE-based routers (e.g., ISR 4000, ASR 1000, CSR 1000v) running the Cisco SD-WAN software. Both perform the same data plane functions. All user traffic flows through these devices.

vEdge / cEdge Function	Description
IPsec tunnel termination	Builds and maintains encrypted IPsec tunnels to all other SD-WAN edge devices across all available transports
BFD path monitoring	Sends BFD hello packets every second on each tunnel to measure latency, jitter, and packet loss in real time
OMP participation	Peers with vSmart over OMP; advertises local prefixes; receives overlay routes and policies
Application-aware routing	Classifies application traffic using DPI; applies policy to forward each application on the best-performing path based on BFD-measured metrics
LAN connectivity	Connects to local LAN switches/VLANs; can run OSPF or BGP with LAN-side routers for local route distribution
Security enforcement	Can enforce application-level firewall, URL filtering, IPS (on advanced platforms); segment traffic using VPNs

6. OMP — Overlay Management Protocol

OMP (Overlay Management Protocol) is the SD-WAN fabric's proprietary routing and signalling protocol that replaces BGP/OSPF for the overlay network. OMP runs between vEdge devices and vSmart controllers over TLS-secured TCP connections. It carries three types of information: routes, TLOCs, and policies.

OMP Information Type	What It Carries	Purpose
OMP Routes	Prefixes reachable via the overlay (analogous to BGP NLRIs — Network Layer Reachability Information)	Tells all vEdge devices what subnets are reachable at each site, and via which TLOC
TLOCs (Transport Locators)	Identifies each tunnel endpoint: System IP + Colour (transport type) + Encapsulation (IPsec/GRE)	Each vEdge can have multiple TLOCs (one per WAN interface); vSmart uses TLOCs to build the overlay topology
Service Routes	Information about services available at a site (firewall, IPS, load balancer)	Allows traffic to be steered to security service nodes in a service-chaining topology

7. Application-Aware Routing (AAR)

Application-Aware Routing (AAR) is one of SD-WAN's most compelling capabilities. Instead of routing traffic based purely on destination IP prefix (as traditional routing protocols do), AAR routes traffic based on application identity and real-time measured path quality — choosing the best transport for each application dynamically, and switching paths automatically when quality degrades.

AAR Configuration Concepts

AAR Component	Description
SLA Class	Defines acceptable thresholds for latency, jitter, and packet loss. Named policy objects (e.g., "VOIP-SLA", "BUSINESS-SLA") referenced in data policies
Data Policy	Defines which traffic matches which SLA class and which TLOCs (transports) to prefer. Configured in vManage and distributed by vSmart to relevant vEdge devices
BFD measurement	BFD sends probe packets on each tunnel every 1 second (configurable). Rolling average of loss/latency/jitter is maintained per tunnel per color
Fallback behavior	If no path meets the SLA threshold, configurable fallback: use best available path, drop traffic, or use a backup transport

8. Zero-Touch Provisioning (ZTP)

Zero-Touch Provisioning (ZTP) is the SD-WAN feature that allows a new branch router to join the fabric and receive its full configuration automatically — without any engineer needing to physically touch or pre-configure the device. An IT administrator ships a factory-fresh vEdge or cEdge device to the branch; a local non-technical user plugs it in and connects the WAN cables. The device does the rest.

ZTP benefit for large deployments: An organisation deploying 500 new branch locations can pre-provision all 500 devices in vManage before any device ships. Each location goes live automatically when the device is connected — reducing deployment time from months to days and eliminating the cost of sending engineers to each site.

9. SD-WAN Security — Built-In vs Bolted-On

Security in SD-WAN is fundamentally different from traditional WAN. Rather than relying on a separate VPN concentrator or firewall to secure internet traffic, SD-WAN builds security into the fabric at every layer.

9.1 Overlay Encryption

All SD-WAN overlay tunnels use IPsec with AES-256-GCM encryption by default. Every packet traversing the overlay — even over MPLS — is encrypted and authenticated. Keys are automatically distributed and rotated by vSmart via OMP. No manual IKE configuration is required on edge devices.

9.2 Authentication and PKI

Every SD-WAN device (vEdge, cEdge, vSmart, vBond, vManage) has a unique certificate signed by a trusted Certificate Authority. All control-plane connections (OMP between vEdge and vSmart) use TLS with mutual certificate authentication — no device can join the fabric without a valid certificate. This prevents rogue devices from inserting themselves into the fabric.

9.3 Security Services on the Edge

Advanced SD-WAN platforms integrate security functions directly into the WAN edge device, eliminating the need for separate security appliances at each branch:

Security Function	Description
Zone-Based Firewall	Stateful inspection between LAN segments and internet breakout traffic — same ZBF concepts as Cisco IOS Zone-Based Firewall
URL Filtering	Blocks or monitors web access by URL category — malware, gambling, social media — without backhauling to HQ proxy
IPS / IDS	Intrusion Prevention / Detection System integrated into the cEdge — inspects traffic for known threats without a separate security appliance
DNS Security	Integration with Cisco Umbrella — blocks malicious domains at DNS resolution time before the connection is even established
Segmentation (VPNs)	SD-WAN uses separate VPN segments (not the same as IPsec VPN — these are traffic segmentation groups) to isolate guest, corporate, and IoT traffic end-to-end across the fabric

10. SD-WAN Design Patterns and Use Cases

10.1 Hub-and-Spoke vs Full Mesh

10.2 Common SD-WAN Use Cases

Use Case	SD-WAN Capability Used
Replace or augment expensive MPLS	Use cheap internet broadband for bulk traffic; retain MPLS only for voice and latency-critical applications; AAR steers traffic appropriately
Direct cloud access from branches	Direct internet breakout at branch with URL filtering and DNS security; Office 365, Salesforce, AWS reach directly without HQ backhaul
WAN resilience and failover	Multiple transports per site; BFD detects path degradation in <1 second; AAR automatically reroutes before users notice
Rapid branch deployment	Zero-Touch Provisioning; new branches live in minutes; no on-site engineer required
Consistent security policy across all sites	Centralised security policies in vManage; same firewall, URL filter, and IPS rules enforced at every site automatically
Visibility and troubleshooting	vManage real-time telemetry; application-level flow visibility; identifies which path each application uses and its quality metrics

10.3 SD-WAN vs DMVPN — Key Differences

Feature	DMVPN	SD-WAN
Control plane	Distributed (EIGRP/OSPF/BGP over mGRE tunnels)	Centralised (vSmart + OMP)
Management	Per-device CLI (or Cisco DNA Center for some)	Fully centralised vManage GUI/API
Multi-transport	One tunnel per transport; manual failover policy	Automatic multi-transport with real-time BFD steering
Application awareness	Limited — routing based on prefix, not app identity	Full DPI / NBAR application classification and AAR
Zero-touch provisioning	Manual spoke config required	Full ZTP — factory-new device joins automatically
Cloud integration	Manual configuration for cloud breakout	Native direct cloud breakout; cloud gateway integrations

Test Your Knowledge — SD-WAN Quiz

What is the fundamental architectural principle that distinguishes SD-WAN from traditional WAN?

A. SD-WAN uses faster physical links than traditional MPLS circuits B. SD-WAN replaces IP routing with MPLS label switching C. SD-WAN decouples the control plane from the data plane, centralising routing intelligence and policy in a software controller while allowing edge devices to forward traffic over any available transport simultaneously D. SD-WAN uses satellite links instead of terrestrial circuits for all WAN traffic

Correct answer is C. The defining principle of SD-WAN — and of Software-Defined Networking in general — is the separation of the control plane from the data plane. In traditional WAN, each router independently runs routing protocols and makes its own forwarding decisions. In SD-WAN, a centralised controller (vSmart) makes policy decisions and distributes them to all edge devices, which only forward packets. This separation enables centralised visibility, policy management, and application-aware routing. See: Controller-Based Networking

In Cisco SD-WAN (Viptela architecture), what is the role of vBond?

A. vBond is the orchestrator — the first component a new SD-WAN edge device contacts. It authenticates the device's certificate, discovers its public IP, and provides the vSmart controller addresses so the device can join the fabric B. vBond is the centralised management dashboard where administrators configure policies and monitor the network C. vBond is the data plane router that forwards user traffic between branches D. vBond runs OMP and distributes routing policies to all vEdge devices

Correct answer is A. vBond is the SD-WAN orchestrator. When a new vEdge or cEdge device powers on, it contacts vBond first. vBond validates the device's certificate, handles NAT traversal to discover the device's public IP address, and provides the IP addresses of the vSmart controllers. vBond must be publicly reachable from the internet. After initial onboarding, vBond is no longer in the regular control or data path. vManage is the management dashboard; vSmart runs OMP.

What is the difference between the SD-WAN overlay and underlay networks?

A. The overlay is the physical WAN circuits; the underlay is the virtual management network B. The underlay is the physical transport infrastructure (MPLS, internet, LTE) that provides basic IP connectivity between edge devices; the overlay is the virtual network of IPsec-encrypted tunnels built on top of the underlay across which SD-WAN routing and policies operate C. The underlay is the customer LAN; the overlay is the internet connection D. They are the same — overlay and underlay refer to inbound and outbound traffic directions

Correct answer is B. The underlay is the raw transport — MPLS, broadband internet, LTE — that simply delivers IP packets between the public-facing interfaces of vEdge devices. The overlay is the virtual network of IPsec tunnels that SD-WAN builds on top of all available underlays simultaneously. Applications, routing (OMP), and policies all operate on the overlay. The underlay is transport-agnostic infrastructure; the overlay is where SD-WAN intelligence lives.

What protocol does Cisco SD-WAN use as its overlay routing protocol, and what does it replace?

A. BGP — replaces OSPF for the WAN B. EIGRP — replaces OSPF for the overlay C. IS-IS — replaces BGP between CE and PE routers D. OMP (Overlay Management Protocol) — replaces BGP/OSPF for the SD-WAN fabric. Runs between vEdge devices and vSmart over TLS, carrying routes (OMP routes), tunnel endpoints (TLOCs), and policies

Correct answer is D. OMP (Overlay Management Protocol) is Cisco SD-WAN's proprietary routing and signalling protocol for the overlay. It runs between vEdge/cEdge devices and vSmart controllers over TLS-secured TCP connections. OMP distributes three types of information: OMP routes (reachable prefixes), TLOCs (tunnel endpoint identifiers including color and encapsulation), and service routes. Traditional routing protocols (OSPF, BGP) are still used on the LAN side and for underlay connectivity, but not for the SD-WAN overlay fabric.

A branch vEdge device has three WAN connections: MPLS, internet broadband, and LTE. How does SD-WAN monitor the quality of each path?

A. vSmart pings each vEdge device every 30 seconds to measure latency B. BFD (Bidirectional Forwarding Detection) runs on every IPsec tunnel between vEdge devices, sending probe packets every second to continuously measure latency, jitter, and packet loss on each path C. SNMP traps are sent by each vEdge to vManage when a path degrades D. The ISP provides SLA reports to vManage via BGP communities

Correct answer is B. SD-WAN uses BFD (Bidirectional Forwarding Detection) on every IPsec overlay tunnel to continuously monitor path quality. BFD sends probe packets approximately every second on each tunnel — one per TLOC pair — and maintains a rolling average of measured latency, jitter, and packet loss. When a path's measured metrics exceed the SLA thresholds defined in an AAR policy, the vEdge automatically steers affected application traffic to a path that meets the SLA — within seconds of the degradation.

What is a TLOC in Cisco SD-WAN, and what three values uniquely identify one?

A. TLOC (Transport Link Overhead Calculator) is a tool for measuring WAN bandwidth; identified by site ID, device name, and interface speed B. TLOC is the SD-WAN tunnel IP address; identified by source IP, destination IP, and port number C. TLOC (Transport Locator) identifies an SD-WAN tunnel endpoint by three values: System IP (the vEdge's stable identifier), Color (the transport type label — mpls, biz-internet, lte, etc.), and Encapsulation (IPsec or GRE) D. TLOC is the management IP of the vBond orchestrator

Correct answer is C. A TLOC (Transport Locator) is the SD-WAN equivalent of a BGP next-hop — it identifies a specific tunnel endpoint on a vEdge device. Each TLOC is uniquely identified by: (1) System IP — the stable identifier for the vEdge device, (2) Color — a label indicating the transport type (mpls, biz-internet, lte, public-internet, etc.), and (3) Encapsulation (IPsec or GRE). A vEdge with three WAN links has three TLOCs. vSmart distributes all TLOCs to all vEdge devices via OMP so every device knows how to reach every tunnel endpoint.

An enterprise currently sends all branch internet traffic through the HQ data centre before it reaches cloud applications. How does SD-WAN improve this?

A. SD-WAN enables direct cloud breakout — SaaS and internet traffic (Office 365, Salesforce, AWS) is sent directly from the branch to the internet, eliminating the latency and MPLS cost of backhauling through HQ, while built-in security (URL filtering, firewall) protects the direct breakout B. SD-WAN compresses all internet traffic to reduce the bandwidth needed for backhaul C. SD-WAN caches cloud application data at the HQ to reduce repeated downloads to branches D. SD-WAN uses MPLS QoS to prioritise cloud traffic through the backhaul path

Correct answer is A. Direct cloud breakout is one of the most important SD-WAN use cases for modern cloud-first enterprises. Backhauling Office 365 and Salesforce traffic from Dubai through a London HQ before it reaches a regional cloud instance adds unnecessary latency, wastes expensive MPLS bandwidth, and creates a bottleneck at the HQ internet connection. SD-WAN allows branches to send SaaS and internet traffic directly to the internet locally, while integrated security (firewall, URL filtering, Cisco Umbrella) ensures the direct breakout is protected.

Which SD-WAN component is responsible for distributing routing policies to all vEdge devices, and what protocol does it use?

A. vManage — uses RESTCONF/NETCONF to push routing tables B. vBond — uses BGP to distribute route advertisements C. vEdge — each device runs OSPF with neighbouring vEdges to exchange routes D. vSmart — uses OMP (Overlay Management Protocol) over TLS connections to receive routes from all vEdge devices, apply centralised policy, and re-distribute modified routes back to all vEdge devices

Correct answer is D. vSmart is the control plane controller that runs OMP. All vEdge/cEdge devices establish OMP sessions with vSmart (not directly with each other for control plane). vEdge devices advertise their locally reachable prefixes and TLOCs to vSmart. vSmart applies centralised policy (e.g., "prefer MPLS for voice") and re-advertises the policy-modified routes back to all vEdge devices. This centralised model means policy changes take effect across the entire fabric by updating only vSmart — no per-device configuration changes needed.

What happens to SD-WAN traffic forwarding if the vSmart controller becomes temporarily unreachable?

A. All traffic immediately stops — vEdge devices cannot forward packets without vSmart B. Existing forwarding continues based on the last policy state received from vSmart — the data plane is not dependent on vSmart being up. New policy changes cannot be applied until vSmart recovers C. vEdge devices switch to running their own local OSPF/BGP to maintain routing D. vBond takes over the control plane automatically

Correct answer is B. SD-WAN follows the SDN principle that the data plane operates independently of the control plane once policy has been distributed. If vSmart goes offline, vEdge devices retain the routes and policies they last received and continue forwarding traffic normally. BFD continues to measure path quality and AAR continues to steer traffic. However, no new policy changes can be pushed, and no new OMP route advertisements will propagate until vSmart recovers. This is why vSmart is typically deployed in a highly available cluster (2–3 controllers).

How does Zero-Touch Provisioning (ZTP) in SD-WAN reduce branch deployment time compared to traditional WAN?

A. ZTP pre-configures the CLI on each device at the factory using a standard template, which the engineer applies on-site B. ZTP allows branches to reuse existing router configurations from neighbouring sites C. ZTP allows a factory-fresh edge device to automatically contact vBond, authenticate via certificate, download its full configuration from vManage, and join the SD-WAN fabric without any manual CLI configuration — a non-technical user only needs to plug in cables and power D. ZTP automatically orders and provisions the WAN circuit from the ISP

Correct answer is C. Zero-Touch Provisioning eliminates the need for a network engineer to physically visit a new branch or pre-configure a device before shipment. The administrator pre-registers the device (by serial number) in vManage and assigns it a template. When the device is powered on at the branch, it contacts vBond, gets authenticated via its factory-installed certificate, receives vSmart/vManage addresses, downloads its configuration template, and builds tunnels to all other SD-WAN sites — all automatically. Deployment that previously took weeks (MPLS circuit + engineer visit + CLI config) takes minutes with ZTP. See: Cisco SD-WAN Lab

SD-WAN Overview

1. What Is SD-WAN and Why Was It Created?

2. Traditional WAN vs SD-WAN — Side by Side

3. Overlay and Underlay — The Core Concept

3.1 Underlay — The Physical Transport

3.2 Overlay — The SD-WAN Fabric

4. Cisco SD-WAN / Viptela Architecture

5. The Four SD-WAN Planes and Their Components

5.1 vManage — Management Plane

5.2 vSmart — Control Plane

5.3 vBond — Orchestration Plane

5.4 vEdge / cEdge — Data Plane

6. OMP — Overlay Management Protocol

7. Application-Aware Routing (AAR)

AAR Configuration Concepts

8. Zero-Touch Provisioning (ZTP)

9. SD-WAN Security — Built-In vs Bolted-On

9.1 Overlay Encryption

9.2 Authentication and PKI

9.3 Security Services on the Edge

10. SD-WAN Design Patterns and Use Cases

10.1 Hub-and-Spoke vs Full Mesh

10.2 Common SD-WAN Use Cases

10.3 SD-WAN vs DMVPN — Key Differences

Test Your Knowledge — SD-WAN Quiz

What is the fundamental architectural principle that distinguishes SD-WAN from traditional WAN?

In Cisco SD-WAN (Viptela architecture), what is the role of vBond?

What is the difference between the SD-WAN overlay and underlay networks?

What protocol does Cisco SD-WAN use as its overlay routing protocol, and what does it replace?

A branch vEdge device has three WAN connections: MPLS, internet broadband, and LTE. How does SD-WAN monitor the quality of each path?

What is a TLOC in Cisco SD-WAN, and what three values uniquely identify one?

An enterprise currently sends all branch internet traffic through the HQ data centre before it reaches cloud applications. How does SD-WAN improve this?

Which SD-WAN component is responsible for distributing routing policies to all vEdge devices, and what protocol does it use?

What happens to SD-WAN traffic forwarding if the vSmart controller becomes temporarily unreachable?

How does Zero-Touch Provisioning (ZTP) in SD-WAN reduce branch deployment time compared to traditional WAN?

Related Topics & Step-by-Step Tutorials