Study guide

2.1 Cisco Catalyst SD-WAN: Control, Management, and Data Planes

Cisco ENCOR 350-401 CCNP Enterprise Core

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

0.1 Cisco 350-401 ENCOR Exam Logistics, Blueprint Structure, and Certification Paths 0.2 Preparation Strategy, Lab Environment Setup, and Practical Test Pacing

2 Enterprise Campus Architecture and High Availability

1.1 Enterprise Network Design: Two-Tier, Three-Tier, Fabric, and Cloud Architectures 1.2 High Availability Architecture: Device Redundancy, FHRPs, and Stateful Switchover (SSO) 1.3 Quality of Service (QoS) Architecture, Classification, Queuing, and Configuration Interpretation

3 Cisco Software-Defined Architecture: SD-WAN and SD-Access

2.1 Cisco Catalyst SD-WAN: Control, Management, and Data Planes 2.2 Cisco SD-Access Architecture: Control Plane, Data Plane, and Fabric Node Roles 2.3 SD-Access Campus Interoperability: Integrating Traditional Networks with Fabric

4 Device and Network Virtualization Technologies

3.1 Device Virtualization: Type 1/2 Hypervisors, Virtual Machines, and Virtual Switching 3.2 Data Path Virtualization: VRF-Lite, GRE Tunneling, and IPsec VPN Fundamentals 3.3 Network Virtualization Overlays: LISP and VXLAN Encapsulation Mechanics

5 Layer 2 Infrastructure: Trunking, EtherChannel, and Spanning Tree

4.1 802.1Q Trunking, Native VLAN, and Dynamic Trunking Protocol Troubleshooting 4.2 EtherChannel Bundling: Static, LACP, and PAgP Implementation and Verification 4.3 Spanning Tree Architecture: RSTP, MST, and STP Protection Mechanisms

6 Layer 3 Routing: OSPF Multi-Area and Protocol Comparison

5.1 Enterprise Routing Principles: Distance Vector vs. Link-State, EIGRP, and OSPF 5.2 OSPFv2 and OSPFv3 Multi-Area Architecture: LSAs, Area Types, and Summarization 5.3 Policy-Based Routing (PBR) Architecture, Configuration, and Route-Maps

7 Exterior Routing: BGP Peering and Path Selection

6.1 External BGP (eBGP) Peering, States, Neighbor Adjacencies, and Timers 6.2 BGP Path Attributes and the Step-by-Step Best Path Selection Algorithm

8 IP Services and First-Hop Redundancy

7.1 Time Synchronization: Network Time Protocol (NTP) and Precision Time Protocol (PTP) 7.2 Network Address Translation: Static NAT, Dynamic NAT, and PAT/Overload 7.3 First Hop Redundancy Protocols: HSRP and VRRP Implementation and Failover

9 IP Multicast Architecture and Protocols

8.1 Multicast Addressing, IGMPv2/v3 Host Membership, and the RPF Check 8.2 Protocol Independent Multicast Sparse Mode (PIM-SM) and Rendezvous Point Discovery 8.3 Anycast RP with MSDP, Source-Specific Multicast (SSM), and Bidirectional PIM

10 Network Diagnostics, Monitoring, and Telemetry

9.1 Network Diagnostic Tools: Conditional Debugging, Traceroute, SNMPv3, and Syslog Logging 9.2 Flexible NetFlow (FNF) Architecture: Flow Records, Exporters, and Monitors 9.3 Switched Port Analyzer: Local SPAN, Remote SPAN (RSPAN), and Encapsulated RSPAN (ERSPAN)

11 Performance Monitoring and Model-Driven Assurance

10.1 IP Service Level Agreements (IP SLA) Probes, Responder, and Route Tracking 10.2 Cisco Catalyst Center: Assurance Dashboards, AI Analytics, and Machine Reasoning Workflows 10.3 Model-Driven Telemetry and Programmable Interfaces: NETCONF and RESTCONF Verification

12 Device Access Control and AAA Architecture

11.1 Device Line Protection: Console, Aux, VTY, Local Authentication, and Privilege Levels 11.2 AAA Architecture: Comparing RADIUS vs. TACACS+ and Method List Configuration

13 Infrastructure Security: ACLs, CoPP, and API Security

12.1 IPv4 and IPv6 Access Control Lists (ACLs): Standard, Extended, and Named Rules 12.2 Control Plane Policing (CoPP): Protecting the Route Processor with MQC 12.3 REST API Security: Token Authentication, TLS Transport, and Rate Limiting

14 Enterprise Network Security Design: ISE, TrustSec, and MACsec

13.1 Endpoint Security Architecture: 802.1X, Cisco ISE Posture, and Profiling 13.2 Next-Generation Firewalls (FTD) and Enterprise Threat Defense Design 13.3 Cisco TrustSec (Security Group Tags) and MACsec (802.1AE) Layer 2 Encryption

15 Network Automation Fundamentals: Python, JSON, and YANG

14.1 Python Fundamentals for Network Engineers: Data Types, Control Flow, and Libraries 14.2 JSON Data Encoding: Syntax, Formatting Rules, and Python Serialization 14.3 YANG Data Modeling: Modules, Tree Structures, and Data Representation

16 Controller REST APIs and RESTCONF Implementation

15.1 Cisco Catalyst Center Intent APIs and Authentication Workflows 15.2 Cisco Catalyst SD-WAN Manager (vManage) REST APIs and Device Interaction 15.3 RESTCONF Protocol Operations: HTTP Verbs, Datastores, and Response Codes

17 Event-Driven Automation and Infrastructure Orchestration

16.1 Cisco Embedded Event Manager (EEM) Applet Architecture and Event Detectors 16.2 Configuration Management: Comparing Ansible, Puppet, Chef, and SaltStack 16.3 Infrastructure as Code (IaC) Principles with Terraform in Enterprise Networks

2.1 Cisco Catalyst SD-WAN: Control, Management, and Data Planes

Key Takeaways Explain This Topic AI

Cisco Catalyst SD-WAN separates router functions into four planes: orchestration (SD-WAN Validator, formerly vBond), management (SD-WAN Manager, formerly vManage), control (SD-WAN Controller, formerly vSmart), and data (WAN Edge).

The Overlay Management Protocol (OMP) executes inside secure DTLS or TLS control tunnels between WAN Edges and vSmart controllers to distribute OMP routes, TLOC routes, and service routes.

Transport Locations (TLOCs) uniquely identify the egress transport interface of a WAN Edge router using a 3-tuple consisting of System IP, Color, and Encapsulation (IPsec or GRE).

Mutual device authentication and zero-touch provisioning rely on enterprise Public Key Infrastructure (PKI) certificates, hardware roots of trust (Cisco SUDI or TPM chips), matching organization names, and authorized serial number whitelists.

WAN Edge data traffic travels directly over dynamic IPsec tunnels formed across arbitrary underlay transports, with continuous link quality evaluation performed by Bidirectional Forwarding Detection (BFD).

Last updated: October 2026

Cisco Catalyst SD-WAN: Control, Management, and Data Planes

Traditional enterprise WANs relied on distributed routing where branch routers independently maintained BGP or OSPF peering, calculated forwarding tables, and enforced security policies configured box by box via CLI. As enterprise workloads migrated to multi-cloud and SaaS environments, this model produced operational rigidity, complex full-mesh configurations, and unpredictable transport performance.

Cisco Catalyst SD-WAN addresses these limitations by decoupling network operations into four discrete planes: orchestration, management, control, and data. This separation establishes an automated, encrypted overlay network spanning heterogeneous underlay transports.

Architectural Planes and Core Components

Catalyst SD-WAN assigns specialized responsibilities across dedicated physical or virtual appliances. In recent releases Cisco renamed the controllers: vBond is now the SD-WAN Validator , vSmart is the SD-WAN Controller , and vManage is SD-WAN Manager . Exam items and older documentation use both sets of names.

Plane Component Platform Options Core Responsibilities

Orchestration SD-WAN Validator (vBond) ESXi, KVM, Cloud Facilitates initial onboarding, validates certificate whitelists, performs NAT traversal via STUN, and orchestrates connections to vSmart and vManage.

Management Catalyst SD-WAN Manager (vManage) Virtual cluster, Cloud Centralized single pane of glass for configuration templates, multi-tenant provisioning, REST APIs, software upgrades, and network telemetry.

Control Catalyst SD-WAN Controller (vSmart) Virtual cluster, Cloud Centralized intelligence engine; acts as an OMP route reflector, distributes IPsec encryption keys, and enforces centralized control and data routing policies.

Data WAN Edge (cEdge / vEdge) Catalyst 8000, ASR 1000, C8000v Forwards IP packets across the overlay, establishes dynamic IPsec tunnels, runs BFD probes for link telemetry, and enforces local QoS/AAR.

Device Identity, Trust, and Zero-Touch Provisioning (ZTP)

Mutual trust and onboarding rely on strict Public Key Infrastructure (PKI) validation, hardware root-of-trust anchors, and administrative identifiers:

Hardware Root of Trust: Cisco IOS-XE cEdge routers embed an x.509 certificate inside a tamper-proof Cisco Secure Unique Device Identifier (SUDI) chip. Legacy vEdge devices use an onboard Trusted Platform Module (TPM).

Authorized Whitelist: Administrators upload a signed WAN Edge Authorized Serial Numbers file to vManage, which distributes approved chassis IDs and serial numbers to vBond and vSmart.

Administrative Parameters: Every node requires a matching Organization Name (case-sensitive string embedded in certificates), a unique 32-bit System IP (non-routable overlay identifier), and a Site ID identifying its physical location.

Step-by-Step Onboarding Walkthrough

Bootstrap: An unconfigured WAN Edge boots, acquires an IP address, gateway, and DNS via DHCP on its WAN interface, and resolves the vBond FQDN.

Transient Tunnel: The edge initiates a transient DTLS tunnel (UDP port 12346) to vBond.

Authentication & NAT Discovery: Edge and vBond perform mutual certificate validation. vBond verifies the edge serial against its whitelist and uses STUN to identify the edge's translated public IP and port.

Controller Distribution: vBond sends the IP addresses of authorized vSmart controllers and vManage to the edge, while notifying vSmart and vManage of the new device.

Control Connections: The edge terminates the transient vBond tunnel and establishes permanent DTLS/TLS control connections to vManage and vSmart. vManage pushes configuration templates, and vSmart establishes OMP peering.

Overlay Management Protocol (OMP) Route Distribution

OMP is an extensible routing protocol operating exclusively within secure DTLS/TLS tunnels between WAN Edges and vSmart controllers. WAN Edge routers never establish OMP peering with each other.

OMP distributes three routing update types:

OMP Routes (vRoutes): Prefixes learned from the local branch LAN (connected subnets, static routes, OSPF, or BGP) within customer Service VPNs (VPNs 1–511 and 513–65530). Attributes include TLOC, Preference, Origin, and Site ID.

TLOC Routes: Advertisements of physical transport attachment points connecting the router to the underlay.

Service Routes: Advertisements declaring specialized branch network services (such as firewalls or intrusion prevention appliances) available at a designated site.

Transport Location (TLOC) Attributes

A TLOC uniquely identifies an egress interface connecting a WAN Edge to the transport underlay. It is defined by an immutable 3-tuple :

System IP: 32-bit logical loopback address of the originating edge router.

Color: Administrative keyword identifying transport type (e.g., mpls , public-internet , biz-internet , lte ). Categorized into private colors (direct underlay routing without NAT) and public colors (which trigger STUN NAT traversal).

Encapsulation: Tunnel protocol, either ipsec (standard secure tunnel) or gre .

OMP carries critical TLOC metadata: private and public IP/port combinations, preference (prioritizes outbound paths), weight (active/active load-balancing), Site ID (loop prevention), and dynamic Security Parameter Index (SPI) keys.

Packet Forwarding Walkthrough [Branch 1 Host] ---> [Edge 1] ========= IPsec Tunnel =========> [Edge 2] ---> [Branch 2 Host]

  • | |
  • (OMP) (OMP)
  • v v
  • +--------------------------------------------------+
  • | vSmart Controller |
  • | (Reflects Routes, TLOCs, and SA Keys) |
  • +--------------------------------------------------+

Ingress: A host in Service VPN 10 sends a packet destined for 192.168.20.50 at Site 2.

FIB Lookup: Edge 1 checks its local VPN 10 forwarding table. The matching OMP route points to next-hop TLOC (10.255.0.2, biz-internet, ipsec) .

Tunnel Verification: Edge 1 references its crypto table for Edge 2's TLOC. Because vSmart previously distributed Edge 2's public IP, port, and symmetric encryption keys, an IPsec tunnel is already active.

Encapsulation: Edge 1 wraps the packet in an IPsec ESP header with an outer IP header addressed to Edge 2's underlay IP, inserting a VPN 10 label.

BFD Telemetry: BFD probes running continuously over the tunnel measure latency, jitter, and loss. If circuit thresholds breach SLA parameters, Application-Aware Routing (AAR) immediately shifts matching traffic to an alternate compliant TLOC.

Decapsulation: Edge 2 strips the IPsec header, identifies VPN 10 from the label, and routes the packet to the destination host.

Benefits and Limitations of Catalyst SD-WAN

Topic 1.2.b asks for both sides of the trade-off:

Benefits Limitations and design considerations

Transport independence: MPLS, broadband, and 4G/5G circuits join one encrypted overlay and can be used active/active. Controller dependency: onboarding, policy changes, and new route or key distribution require the Validator, Controller, and Manager. Edges keep forwarding on existing state during a controller outage, but only until timers expire.

Centralized policy: topology, application-aware routing, QoS, and security policies are defined once in SD-WAN Manager and distributed by the controllers. Timer-bound headless operation: the OMP graceful-restart timer (default 43,200 seconds, or 12 hours) and the IPsec rekey interval (default 86,400 seconds) limit how long edges run without controllers.

Zero-touch provisioning: new routers authenticate with certificates and pull their configuration without an on-site engineer. Encapsulation overhead: IPsec and SD-WAN headers add tens of bytes per packet, so MTU and TCP MSS must be planned (for example, clamping MSS to 1350 to 1400 bytes).

Application-aware routing: BFD probes measure loss, latency, and jitter on every tunnel, and matching traffic moves to a path that meets its SLA. Tunnel scale: a full mesh of n sites needs n(n-1)/2 tunnels per transport color pair, so large fabrics use hub-and-spoke or regional designs to limit tunnels and BFD sessions.

Cloud and SaaS integration: Cloud OnRamp features steer SaaS and IaaS traffic directly from branches instead of backhauling it. Operational change: teams must manage certificates, templates or configuration groups, licensing, and controller upgrades rather than box-by-box CLI.