Study guide
3.1 Cisco Catalyst SD-WAN Architecture & Orchestration
CCNP Enterprise ENCOR 350-401
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Enterprise Architecture & Hierarchical Design
1.1 Enterprise Network Design Models & Hierarchical Campus Architecture 1.2 On-Premises, Cloud & Hybrid Infrastructure Deployment Models 1.3 Hardware Switching Architecture & Packet Forwarding
2 Chapter 2: Enterprise Quality of Service (QoS)
2.1 QoS Components: Classification, Marking & Trust Boundaries 2.2 QoS Policy: Queuing, Shaping, Policing & Interpreting MQC Output
3 Chapter 3: Software-Defined WAN (Catalyst SD-WAN)
3.1 Cisco Catalyst SD-WAN Architecture & Orchestration 3.2 SD-WAN Policies, Traffic Engineering & Application-Aware Routing
4 Chapter 4: Software-Defined Access (Catalyst SD-Access)
4.1 Catalyst SD-Access Fabric Architecture & Plane Separation 4.2 Cisco TrustSec, Security Group Tags (SGT), SXP & MACsec
5 Chapter 5: Device & Data Path Virtualization
5.1 Server & Network Device Virtualization 5.2 VRF-Lite & Virtual Routing Multi-Tenancy 5.3 GRE & IPsec Tunnel Virtualization Mechanics
6 Chapter 6: Network Virtualization & Overlay Technologies
6.1 LISP Architecture & EID-to-RLOC Mapping Mechanics 6.2 VXLAN & EVPN Overlay Architecture
7 Chapter 7: Layer 2 Infrastructure & Switching
7.1 VLANs, 802.1Q Trunking & VTPv3 7.2 Spanning Tree Protocol Mechanics 7.3 Advanced STP Protection Mechanisms 7.4 EtherChannel Link Aggregation
8 Chapter 8: Layer 3 Routing Foundations & EIGRP
8.1 IP Routing Foundations & Administrative Distance 8.2 Enhanced Interior Gateway Routing Protocol (EIGRP)
9 Chapter 9: OSPFv2 & OSPFv3 Operations
9.1 OSPFv2 Architecture & Neighbor State Machine 9.2 OSPF LSA Types & Multi-Area Design 9.3 OSPFv3 for IPv4 and IPv6 Address Families
10 Chapter 10: Border Gateway Protocol (BGP)
10.1 BGP Architecture, Neighbor States & Peering 10.2 BGP Path Attributes & Best Path Selection Algorithm
11 Chapter 11: Policy-Based Routing & Route Redistribution
11.1 Policy-Based Routing (PBR) & Route Maps 11.2 Route Redistribution & Loop Prevention
12 Chapter 12: IP Services & High Availability
12.1 First Hop Redundancy Protocols (HSRP, VRRP & GLBP) 12.2 Network Time Protocol (NTPv4) & Precision Time Protocol (PTP) 12.3 Network Address Translation (NAT/PAT) & VRF-Aware NAT
13 Chapter 13: IP Multicast Operations
13.1 IP Multicast Addressing, Group Management (IGMPv1/v2/v3) & IGMP Snooping 13.2 Protocol Independent Multicast (PIM-SM, PIM-SSM & Bidir-PIM) 13.3 Rendezvous Point (RP) Distribution Mechanisms
14 Chapter 14: Network Assurance & Monitoring
14.1 Diagnostic Utilities, Conditional Debugging & Path MTU Discovery 14.2 Syslog Architecture, Logging Facilities & Severity Levels 14.3 SNMPv1/v2c/v3 Security & Flexible NetFlow (FNF) Architecture 14.4 Switched Port Analyzer (SPAN, RSPAN, ERSPAN) & IP SLA Object Tracking
15 Chapter 15: Catalyst Center Assurance & Controller Operations
15.1 Cisco Catalyst Center (DNA Center) Assurance & AI Network Analytics 15.2 Cisco Catalyst Center Device Onboarding & Software Image Management (SWIM)
16 Chapter 16: Enterprise Security & Access Control
16.1 Device Hardening, AAA Architecture & RADIUS/TACACS+ 16.2 Access Control Lists (ACLs) for Infrastructure Security 16.3 Control Plane Policing (CoPP) & Control Plane Protection (CPPr) 16.4 Layer 2 Infrastructure Security Features 16.5 IEEE 802.1X Port-Based Authentication & MAB
17 Chapter 17: Threat Defense & API Security
17.1 Enterprise VPN Technologies (DMVPN Phase 1/2/3 & FlexVPN) 17.2 Next-Generation Threat Defense & Secure Access Service Edge (SASE)
18 Chapter 18: Network Automation, Programmability & Data Modeling
18.1 Python Fundamentals for Network Engineers & Cisco Libraries 18.2 YANG Data Modeling Language (RFC 6020/7950) & Model Types 18.3 REST API Architecture, HTTP Verbs, Security & Cisco Controller APIs 18.4 Model-Driven Telemetry (MDT) & NETCONF/RESTCONF Operations
19 Chapter 19: Orchestration, EEM & AI Operations
19.1 Configuration Management & Infrastructure as Code (Ansible & Terraform) 19.2 Cisco Embedded Event Manager (EEM) & Intent-Based Networking
3.1 Cisco Catalyst SD-WAN Architecture & Orchestration
Key Takeaways Explain This Topic AI
Cisco Catalyst SD-WAN separates network functions into four decoupled planes: Orchestration (vBond), Management (Catalyst SD-WAN Manager, formerly vManage), Control (vSmart), and Data (vEdge/cEdge routers), with vBond acting as the initial gatekeeper on a public or 1:1 NAT IP so it can perform STUN-based NAT traversal and orchestrate temporary onboarding sessions.
Zero-Touch Provisioning (ZTP) for vEdge and Cisco Plug-and-Play (PnP) for cEdge establish automated cryptographic trust using hardware SUDI/TPM chips, Enterprise Root CAs, and signed serial number whitelists.
Edge routers maintain permanent DTLS/TLS control connections to vSmart and vManage, using port hopping across UDP ports 12346-13146 and falling back to TLS over TCP 23456 when UDP is filtered.
Control plane failure does not disrupt existing data plane forwarding: edge routers retain established IPsec tunnels and forwarding tables in Graceful Restart mode during temporary vSmart outages.
ENCOR v1.2 reworded topic 1.2.b from "traditional WAN and SD-WAN solutions" to "benefits and limitations of Catalyst SD-WAN solution", so candidates must be able to name real constraints such as tunnel overhead, per-platform crypto and BFD scale ceilings, PKI lifecycle burden, and continued dependence on underlay quality -- not just the benefits.
Last updated: August 2026
1. Architectural Foundations & Plane Separation
Traditional WAN architectures rely on distributed control planes where every branch edge router independently computes routing decisions, negotiates complex pairwise point-to-point IPsec tunnels (often requiring full-mesh IKE/ISAKMP peering), and requires box-by-box configuration management. As multi-cloud adoption, direct internet access (DIA), and hybrid workforce models expanded, this legacy operational model proved rigid, operationally expensive, and difficult to secure.
Cisco Catalyst SD-WAN addresses these limitations by disaggregating network operations into four distinct planes of separation : +-----------------------------------------------------------------------------------+
- | MANAGEMENT PLANE - SD-WAN Manager (formerly vManage) |
- | * Single Pane of Glass (GUI / REST API) * Feature & Device Templates |
- | * Policy Configuration & Central Repository * Telemetry, Syslog & Analytics |
- +-----------------------------------------------------------------------------------+
- ^
- | Management (DTLS/TLS)
- v
- +------------------------------------+ +-----------------------------------+
- | ORCHESTRATION - SD-WAN Validator | | CONTROL - SD-WAN Controller |
- | (formerly vBond) | | (formerly vSmart) |
- | * Initial Fabric Gatekeeper | | * SD-WAN Fabric 'Brain' |
- | * NAT Traversal / STUN Discovery |<-------->| * OMP Route Reflection |
- | * Transient DTLS/TLS Onboarding | | * Crypto Key & Policy Exchange |
- +------------------------------------+ +-----------------------------------+
- ^ ^
- | Transient Discovery | Permanent OMP Control
- +-----------------------+-----------------------+
- |
- v
- +-----------------------------------------------------------------------------------+
- | DATA PLANE (WAN Edge Routers) |
- | * cEdge (Catalyst 8000, ISR, ASR) & vEdge (Viptela OS / Cloud) |
- | * Zero-Trust IPsec Data Tunnels * BFD Real-Time SLA Probing |
- | * Local & Centralized Policy Enforcement * Hardware Crypto Acceleration |
- +-----------------------------------------------------------------------------------+
- Detailed Breakdown of the Four SD-WAN Planes
Plane Component Primary Functions & Architectural Scope Protocols Used Session Nature
Orchestration vBond Orchestrator Initial gatekeeper; performs mutual identity authentication; executes STUN-like NAT traversal; distributes IP lists of vManage and vSmart controllers to onboarding edge routers. DTLS / TLS (UDP 12346 / TCP 23456) Transient (torn down post-onboarding)
Management vManage NMS Centralized dashboard (single pane of glass); Day-0/1/2 configuration management via Feature/Device Templates; centralized policy creation; analytics, telemetry, alarm collection, and software image management. HTTPS / REST / NETCONF over DTLS/TLS Permanent
Control vSmart Controller Centralized intelligence ("fabric brain"); establishes Overlay Management Protocol (OMP) peering; acts as an OMP route reflector; distributes data encryption keys (TLOC SPIs) to edges; calculates and distributes centralized control/data policies. OMP over DTLS / TLS Permanent
Data (Forwarding) WAN Edge Routers (cEdge & vEdge) Forwards user application traffic across transport underlays; establishes dynamic IPsec / GRE tunnels to peer edges; runs BFD probing for latency, jitter, and loss; enforces localized QoS and centralized data policies. IPsec / GRE, BFD Permanent (Edge-to-Edge)
- Current Product Names vs. Legacy Viptela Names (Exam-Critical)
- Cisco renamed every Catalyst SD-WAN control component in Release 20.12.1 . The ENCOR
- v1.2 blueprint uses the new names (topic 1.2 reads "Cisco Catalyst SD-WAN solution"
and topic 6.4 reads "APIs for Cisco Catalyst Center and SD-WAN Manager"), while the CLI, show output, and most field documentation still print the legacy Viptela names. You must
be able to translate in both directions on exam day.
- Current Cisco name Legacy Viptela name Plane Role in one line
- Cisco Catalyst SD-WAN Manager vManage Management GUI, REST API, templates, policy authoring, telemetry
- Cisco Catalyst SD-WAN Controller vSmart Control OMP route reflection, centralized policy, key distribution
- Cisco Catalyst SD-WAN Validator vBond Orchestration Authenticates and introduces devices; STUN/NAT discovery
- Cisco Catalyst SD-WAN Analytics vAnalytics Management Cloud predictive analytics and forecasting
- Cisco IOS XE Catalyst SD-WAN device cEdge Data IOS XE WAN Edge router (Catalyst 8000, ISR, ASR)
- Cisco vEdge device vEdge Data Legacy Viptela-OS WAN Edge router
- Exam trap: a question can name the component either way in the stem and the other way
- in the options. "Which device performs OMP route reflection?" and "Which device is the
- SD-WAN Controller?" have the same answer. This guide keeps the legacy names in CLI blocks
because that is literally what the device prints, and uses the current names in prose.
Loading diagram... Cisco Catalyst SD-WAN Plane Separation & Control Connections
2. Zero-Touch Provisioning (ZTP) & Cisco Plug-and-Play (PnP) Lifecycle
Deploying hundreds or thousands of remote branch routers manually via console cables is error-prone and costly. Cisco Catalyst SD-WAN provides automated onboarding workflows:
Zero-Touch Provisioning (ZTP) : Used by legacy vEdge routers running Viptela OS (contacts ztp.viptela.com ).
Cisco Network Plug-and-Play (PnP) : Used by cEdge routers running Cisco IOS XE SD-WAN software (contacts devicehelper.cisco.com ).
The End-to-End Automated Onboarding Sequence +----------------------------------------------------------------------------------------------------+
- | ZTP / PNP ONBOARDING LIFECYCLE |
- +----------------------------------------------------------------------------------------------------+
- [1. Power On & DHCP Discovery]
* WAN Edge boots with factory-default configuration.
* Edge sends DHCP Requests on all WAN interfaces in default Transport VPN (VPN 0).
* Obtains IP address, default gateway, and DNS server addresses.
- |
- v
- [2. DNS Resolution of Provisioning Redirect Portal]
* cEdge resolves: 'devicehelper.cisco.com' (Cisco PnP Connect Portal).
* vEdge resolves: 'ztp.viptela.com' (Viptela ZTP Portal).
* (Alternatively, DHCP Option 43 specifies the enterprise vBond IP/FQDN directly).
- |
- v
- [3. Mutual Certificate Authentication with Provisioning Server]
* Edge initiates TLS/DTLS connection to the cloud redirect server.
* Hardware validation: cEdge presents hardware SUDI certificate; vEdge presents Viptela cert.
* Redirect portal checks device serial number against customer's Smart/Virtual Account.
* Portal returns the enterprise vBond IP address/FQDN and Organization Name.
- |
- v
- [4. Initial Contact with Enterprise vBond Orchestrator]
* Edge initiates DTLS connection to enterprise vBond on UDP port 12346.
* Mutual authentication: Edge and vBond validate each other using the Enterprise Root CA.
* vBond checks device serial against the signed WAN Edge Authorized Serial List.
* vBond performs STUN reflection: detects edge's public IP and translated UDP port.
* vBond sends edge the IP addresses of vManage and vSmart controllers.
* vBond informs vManage and vSmart that a new edge device is joining.
* Edge tears down transient DTLS connection to vBond.
- |
- v
- [5. vManage Connection & Configuration Push]
* Edge establishes permanent DTLS/TLS control connection to vManage.
* vManage verifies chassis ID and token / certificate serial.
* vManage checks device template assignment: pushes target software image if needed,
then pushes full system configuration template over NETCONF.
- |
- v
- [6. vSmart Connection & Data Plane Activation]
* Edge establishes permanent DTLS/TLS control connection to assigned vSmart controller(s).
* Establishes Overlay Management Protocol (OMP) peering session.
* Edge advertises local TLOCs, prefixes, and IPsec crypto keys (SPIs) via OMP.
* vSmart reflects remote TLOCs, prefixes, policies, and peer crypto keys back to the edge.
* Edge dynamically forms direct IPsec data tunnels to remote peers and starts BFD probing.
+----------------------------------------------------------------------------------------------------+
- 3. DTLS/TLS Control Plane Connections & NAT Traversal
- Control Plane Protocol Comparison
All control connections between SD-WAN components operate inside encrypted tunnels using either DTLS (Datagram Transport Layer Security, RFC 6347) or TLS (Transport Layer Security, RFC 5246): +-----------------------+-----------------------------------------------------------------------------+
- | Feature | DTLS (Datagram TLS) | TLS (Transport Layer Security) |
- +-----------------------+-----------------------------------------------------------------------------+
- | Transport Layer | UDP | TCP |
- | Default Port | Base UDP 12346 (hops: 12366, 12386, etc.) | Base TCP 23456 / 23457 |
- | Performance | Lower latency; avoids TCP head-of-line | Higher overhead due to 3-way |
- | | blocking over unreliable underlays. | handshake and ACK verification. |
- | Firewall Friendliness | Frequently filtered by restrictive | Easily traverses enterprise |
- | | enterprise edge firewalls. | firewalls permitting TCP egress.|
- | Default Setting | **Default protocol** on all devices | Configurable fallback protocol |
- +-----------------------+-----------------------------------------------------------------------------+
- Control Connection Mesh Summary
Edge to vBond : Transient DTLS/TLS connection (active only during bring-up or WAN interface IP change).
Edge to vManage : Permanent DTLS/TLS connection (for NETCONF configuration, statistics collection, DPI telemetry).
Edge to vSmart : Permanent DTLS/TLS connection (for OMP routing updates and crypto key distribution).
vManage to vSmart : Permanent DTLS/TLS connection.
vManage to vBond : Permanent DTLS/TLS connection.
vSmart to vBond : Permanent DTLS/TLS connection.
vSmart to vSmart : Permanent full-mesh DTLS/TLS connections (for OMP topology synchronization across controllers).
Port Hopping & STUN NAT Traversal
When a WAN edge router resides behind a NAT device:
Base Port Assignment : In Cisco Catalyst SD-WAN, the default base control port for VPN 0 transport interfaces is UDP 12346 .
Port Hopping : If the edge cannot establish a DTLS session on port 12346 (e.g., due to a stateful firewall or port collision), it increments the port number by 20 (testing 12366, 12386, 12406, up to 13146) to attempt connection.
STUN (Session Traversal Utilities for NAT) : Because vBond resides on a public IP address, it inspects the incoming UDP packet header from the edge. Even if the edge configured a private IP (e.g., 192.168.1.50:12346 ), vBond detects the post-NAT public IP and translated port (e.g., 203.0.113.10:25432 ) and transmits this public reflection back to the edge. The edge then advertises this public TLOC to vSmart so remote peers know where to direct incoming IPsec tunnels. +-------------------+ +--------------------+ +--------------------+
- | Branch WAN Edge | | NAT Gateway | | vBond Orchestrator |
- | (192.168.1.50) | | (203.0.113.10) | | (198.51.100.1) |
- +-------------------+ +--------------------+ +--------------------+
- | | |
- |--- DTLS Request (Src: 12346) ---->| |
- | |--- Translated (Src: 25432) -------->|
| | | [vBond records:
- | | | Public IP: 203.0.113.10
- | | | Public Port: 25432]
- | |<-- DTLS Response (Reflected IP/Port)|<------|
- |<-- Forwarded Response ------------| |
4. Security Architecture, SUDI Certificates & Trust Fabric
The Cisco Catalyst SD-WAN Trust Fabric guarantees zero-trust operational security. Every device attempting to join the overlay fabric must pass strict cryptographic validation based on three core pillars: +---------------------------------------------+
- | SD-WAN ZERO-TRUST SECURITY TRIAD |
- +---------------------------------------------+
- |
- +-------------------------------------+-------------------------------------+
- | | |
- v v v
- +-----------------------+ +-----------------------+ +-----------------------+
- | 1. ENTERPRISE ROOT CA | | 2. DEVICE IDENTITY | | 3. AUTHORIZED SERIAL |
- | TRUST CHAIN | | CERTIFICATES | | WHITELIST |
- +-----------------------+ +-----------------------+ +-----------------------+
- | * Identical Root CA | | * cEdge: Cisco SUDI | | * Signed serial file |
- | installed on all | | X.509 in TPM chip | | from Cisco Portal |
- | controllers & edges.| | * vEdge: Viptela cert | | * Uploaded to vManage |
- | * Validates all TLS/ | | * Controllers: Signed | | and distributed to |
- | DTLS connections. | | by Enterprise CA | | vBond and vSmart. |
- +-----------------------+ +-----------------------+ +-----------------------+
- The Three Security Pillars Explained
Enterprise Root Certificate Authority (Root CA) :
Every controller (vManage, vSmart, vBond) and edge device must have the identical Root CA certificate installed in its local trust store.
Used to validate peer certificates during the TLS/DTLS mutual handshake.
Can be Cisco's cloud Root CA (DigiCert/Symantec) or an internal Enterprise Root CA.
Hardware Identity & SUDI Certificates :
cEdge (Cisco IOS XE SD-WAN) : Houses a hardware-tamper-proof Trust Anchor Module (TAM) / TPM chip burned during manufacturing with a Secure Unique Device Identifier (SUDI) X.509 certificate. The SUDI provides immutable cryptographic proof of the router's serial number and Cisco hardware authenticity.
vEdge (Viptela OS) : Uses an integrated Avnet TPM chip with a factory-installed Viptela certificate.
Cloud/Virtual Routers (Catalyst 8000v / vEdge Cloud) : Lack hardware TPMs; authenticate using a unique Chassis ID and a cryptographically generated one-time Token (OTP) generated from Cisco vManage / Smart Account.
WAN Edge Authorized Serial Number Whitelist :
A cryptographically signed file ( smart-account-provisioning.viptela ) generated on the Cisco Plug and Play Connect portal.
Contains the authorized list of serial numbers, chassis IDs, and model types entitled to join the customer's SD-WAN overlay.
Uploaded to vManage and synchronized with vBond and vSmart. If an unauthorized edge attempts to connect, vBond rejects the DTLS session immediately.
Mandatory Identity Validation Checks
For a control connection to succeed, all four conditions must match simultaneously:
Organization Name : Case-sensitive exact string match across all controllers and edge devices.
Certificate Validity : Unexpired certificate chain validated against the installed Root CA.
Serial Number Whitelist : The edge device's serial number must be present in the active authorized device list.
System Clock / NTP : Time must be synchronized; certificate validation fails if clock skew is outside valid validity windows.
5. Control Plane Verification & Troubleshooting CLI Reference
Essential Cisco IOS XE SD-WAN (cEdge) Verification Commands ! Verify active control connections to vManage, vSmart, and vBond
- Router# show sdwan control connections
- PEER PEER CONTROLLER
- PEER PEER PEER SITE DOMAIN PEER PRIVATE PEER PUB GROUP STATUS
- TYPE PROT SYSTEM IP ID ID PRIVATE IP PORT PUBLIC IP PORT ORGANIZATION ID
--------------------------------------------------------------------------------------------------------------------------------------------------
- vmanage dtls 10.255.0.100 100 1 198.51.100.10 12346 198.51.100.10 12346 EnterpriseNet-Prod 0 up
- vsmart dtls 10.255.0.200 100 1 198.51.100.20 12346 198.51.100.20 12346 EnterpriseNet-Prod 0 up
vbond dtls 10.255.0.1 0 0 198.51.100.1 12346 198.51.100.1 12346 EnterpriseNet-Prod 0 tear_down ! Verify local identity, organization name, certificates, and chassis ID
- Router# show sdwan control local-properties
- personality vedge
- sp-organization-name EnterpriseNet-Prod
- organization-name EnterpriseNet-Prod
- root-ca-chain-status Installed
- certificate-status Installed
- certificate-validity Valid
- chassis-num/unique-id C8300-1N1S-6T-FDO2435A98B
- serial-num 12345678
- system-ip 10.255.1.1
- site-id 101
- public-ip 203.0.113.15
- public-port 12346
- private-ip 192.168.1.10
- private-port 12346 ! Summary count of active control plane and data plane connections
- Router# show sdwan control summary
- BOOTSTRAP SIGN-WITH-CA CERT-ISSUED VMANAGE VSMART
- STATUS OPERSTATE TOTAL TOTAL TOTAL UP UP
- ---------------------------------------------------------------------
- up up 1 1 1 1 1
- Common Control Plane Troubles & Root Causes
Symptom CLI Verification State Root Cause Remediation
vBond Connection Rejected show sdwan control local-properties -> VBOND_AUTH_FAILED Organization name mismatch (case sensitivity) or device not in authorized serial list. Verify organization-name string matches exactly; upload updated serial whitelist file to vManage.
Certificate Validation Failure show sdwan certificate installed -> CERT_INVALID Clock skew or Root CA mismatch between controller and edge. Configure NTP in VPN 0; install correct Enterprise Root CA certificate bundle.
DTLS Blocked by Firewall show sdwan control connections -> state: init / connecting Intermediate ISP/firewall dropping UDP port 12346+. Change control protocol to TLS ( control-plane-protocol tls ) to utilize TCP 23456.
vBond Session Torn Down show sdwan control connections -> vbond: tear_down Normal Behavior : vBond sessions are transient and tear down once the edge learns vManage/vSmart IPs. No action needed; verify vManage and vSmart connections remain up .
6. Benefits and Limitations of the Catalyst SD-WAN Solution
ENCOR v1.2 changed topic 1.2.b from v1.1's neutral "Traditional WAN and SD-WAN solutions" to the explicitly two-sided "Benefits and limitations of Catalyst SD-WAN solution" . The word limitations is new, and it means an exam item can legitimately ask what SD-WAN does not solve. A candidate who can only recite benefits is half prepared.
6.1 Benefits
Benefit What it actually buys you
Transport independence MPLS, broadband, LTE, and 5G are all just TLOC colours. Adding a circuit does not change the routing design, and cheap broadband can carry production traffic
Centralized policy Policy is authored once in SD-WAN Manager and executed on the SD-WAN Controllers. Changing the topology of 500 branches is one policy edit, not 500 CLI sessions
Application-aware routing BFD continuously measures loss, latency, and jitter per tunnel, and traffic is steered per application against an SLA class (Section 3.2)
Zero-touch provisioning A branch router ships to site and onboards itself via PnP and the SD-WAN Validator using its SUDI certificate. No engineer travels
Encryption everywhere by default Every data tunnel is IPsec and every control connection is DTLS/TLS, without designing a single crypto map
Native segmentation Service VPNs give per-segment routing tables end to end across the fabric, without MPLS L3VPN from the carrier
Direct Internet Access and cloud onramp Branches reach SaaS and IaaS locally instead of hairpinning through a data center (Section 1.2)
- Visibility Per-application, per-tunnel telemetry is built in rather than bolted on
- 6.2 Limitations
These are the ones worth memorising, because they are the half candidates skip.
The underlay still matters. SD-WAN measures and reacts to loss, latency, and jitter; it cannot create capacity that the circuit does not have. If both transports are degraded, application-aware routing picks the least bad path and the user still suffers. SD-WAN is not a substitute for adequate bandwidth.
Tunnel overhead is real. Every data-plane packet carries an outer IP header plus ESP encapsulation, which reduces the effective MTU and consumes goodput. Undersized MTU and missing TCP MSS clamping produce exactly the black-hole symptom analysed in Section 14.1.
Per-platform scale ceilings. Crypto throughput, the number of concurrent IPsec tunnels, and the number of BFD sessions a WAN Edge can maintain are all platform-specific hardware limits. A full-mesh topology across many sites multiplies BFD sessions quickly, which is a common reason a design is forced into hub-and-spoke or region-based topologies via centralized control policy.
PKI lifecycle is an ongoing operational burden. The trust model depends on certificates on every controller and edge. Certificate expiry, root CA rotation, and controller certificate renewal are recurring tasks, and an expired controller certificate takes down control connections fabric-wide.
Controller dependency for change, though not for forwarding. Losing all SD-WAN Controllers does not stop forwarding — edges hold their OMP routes in graceful restart, as covered earlier in this section. But while they are down you cannot make policy changes, onboard new sites, or converge around a topology change. Losing SD-WAN Manager additionally stops all configuration, templating, and monitoring.
Template rigidity and a genuine learning curve. Device templates enforce consistency by design, which is a benefit until you need a one-off change on a single router. Operational skills also split in two: engineers must troubleshoot the overlay and the underlay as separate problem domains, and a fault in either presents identically to the user.
Feature parity gaps and vendor lock-in. Not every feature is available on both Cisco IOS XE Catalyst SD-WAN devices and legacy vEdge platforms, and the fabric, its policy language, and its controllers are Cisco-specific. Migrating away is a rebuild, not a reconfiguration.
Exam framing: a stem that says "which of the following is a limitation" is usually testing the underlay point or the controller-dependency point. Remember the precise boundary — control-plane loss stops change, not forwarding .