Study guide

2.2 Cisco SD-Access Architecture: Control Plane, Data Plane, and Fabric Node Roles

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.2 Cisco SD-Access Architecture: Control Plane, Data Plane, and Fabric Node Roles

Key Takeaways Explain This Topic AI

Cisco Software-Defined Access (SD-Access) separates the campus network into an automated, non-blocking Layer 3 routed Underlay and a virtualized multi-tenant Overlay.

The SD-Access Control Plane implements Locator/ID Separation Protocol (LISP) to decouple host identity (Endpoint Identifier - EID) from its current network location (Routing Locator - RLOC), eliminating broadcast ARP flooding.

The SD-Access Data Plane utilizes Virtual Extensible LAN (VXLAN) encapsulation with Group-Based Policy extensions (VXLAN-GPO), carrying a 16-bit Security Group Tag (SGT) inside the VXLAN header.

Fabric node roles provide specialized functions: Fabric Edge Nodes onboard endpoints and perform VXLAN encapsulation; Fabric Border Nodes bridge fabric traffic to external networks; Fabric Control Plane Nodes maintain the central LISP Map-Server/Map-Resolver database.

Intermediate Nodes in the underlay act as standard IP transit routers with no fabric state; Cisco recommends a 9100-byte underlay MTU so the 50 bytes of VXLAN-GPO overhead never forces fragmentation.

Last updated: October 2026

Cisco SD-Access Architecture: Control Plane, Data Plane, and Fabric Node Roles

Enterprise campus networks historically relied on hierarchical models with Layer 2 Spanning Tree Protocol (STP) domains spanning access and distribution layers. These designs suffered from blocked links, complex multi-chassis EtherChannel workarounds, broadcast flooding, and rigid VLAN-to-subnet bindings that restricted mobility. Securing endpoints required complex manual IP-based Access Control Lists (ACLs).

Cisco Software-Defined Access (SD-Access) resolves these limitations by introducing a programmable campus fabric that decouples network services from physical infrastructure, pairing an automated routed underlay with a virtualized overlay to deliver uniform policy, automated segmentation, and seamless mobility.

Underlay vs. Overlay Architecture

SD-Access establishes a strict separation between physical transport and virtualized network services: +--------------------------------------------------------------+

  • | OVERLAY |
  • | Virtual Networks (VRFs) + Group-Based Policy (SGTs) |
  • | Data Plane: VXLAN-GPO | Control Plane: LISP |
  • +--------------------------------------------------------------+
  • |
  • (Encapsulated across Underlay)
  • v
  • +--------------------------------------------------------------+
  • | UNDERLAY |
  • | Physical Switches, Routers, and Point-to-Point Links |
  • | Layer 3 Routed Fabric (IS-IS / OSPF) with MTU >= 9100 |
  • +--------------------------------------------------------------+
  • The Routed Underlay

The underlay comprises the physical switches, routers, and cabling providing base IP connectivity:

Layer 3 Routed Fabric: Spanning Tree is eliminated from the core and distribution layers. Every link between access and distribution switches operates as a routed point-to-point Layer 3 connection.

Equal-Cost Multi-Pathing (ECMP): With Layer 3 routed interfaces, all physical links actively forward traffic simultaneously, delivering deterministic sub-second convergence.

Routing Protocol: Intermediate System to Intermediate System (IS-IS) is standard and automatically deployed by Cisco Catalyst Center LAN Automation; routed OSPF is also supported.

Underlay MTU: Cisco recommends a 9100-byte jumbo MTU on underlay links, and LAN Automation configures it. At a minimum, every link must carry the largest client frame plus the 50 bytes of VXLAN-GPO overhead, so a 1500-byte client packet needs at least 1550 bytes.

The Virtualized Overlay

The overlay is the virtualized network operating over the underlay:

Macro-Segmentation: Implemented via Virtual Networks (VNs) using Virtual Routing and Forwarding (VRF) instances to isolate distinct user groups (e.g., Corporate , IoT , Guests ).

Micro-Segmentation: Granular security enforced within each VN using Cisco TrustSec Security Group Tags (SGTs). Policies apply to endpoints regardless of IP address or switch port.

Control Plane Architecture: Locator/ID Separation Protocol (LISP)

Traditional routing conflates identity (who a device is) with location (where it connects). SD-Access uses Locator/ID Separation Protocol (LISP; originally RFC 6830, now RFC 9300 and RFC 9301) to split the IP address into two namespaces:

Endpoint Identifier (EID): The IP or MAC address assigned to an end host. The EID represents host identity and remains static when roaming.

Routing Locator (RLOC): The Layer 3 underlay loopback IP address of the Fabric Edge switch to which the host attaches. The RLOC represents location and is routable in the underlay.

LISP Control Plane Components

LISP Role Function in SD-Access Fabric

Map-Server (MS) Receives Map-Register messages from Fabric Edge nodes when endpoints connect; maintains the central authoritative EID-to-RLOC database.

Map-Resolver (MR) Receives Map-Request queries from Fabric Edge nodes searching for the destination RLOC for a target EID; responds with a Map-Reply .

Control Plane Node Dedicated or collocated fabric switch running the centralized LISP MS/MR database services. [Host A (EID_A)] ---> [Edge 1 (RLOC_1)] ---------------------> [Edge 2 (RLOC_2)] ---> [Host B (EID_B)]

  • | ^
  • (1) Map-Request (EID_B?) (2) Map-Reply (EID_B is at RLOC_2)
  • v |
  • +-------------------------------------------------+
  • | Fabric Control Plane Node |
  • | (LISP MS / MR) |
  • +-------------------------------------------------+
  • Eliminating Broadcast Flooding

Instead of broadcasting ARP requests across all switches in a VLAN, the Fabric Edge intercepts host ARP requests, queries the Control Plane Node with a unicast LISP Map-Request , receives the target switch's RLOC, and forwards traffic directly via unicast VXLAN.

Data Plane Encapsulation: VXLAN-GPO

SD-Access uses Virtual Extensible LAN with Group-Based Policy (VXLAN-GPO) for data forwarding. Standard VXLAN (RFC 7348) encapsulates Layer 2 frames in UDP (port 4789) with a 24-bit VXLAN Network Identifier (VNI). VXLAN-GPO modifies the 8-byte VXLAN header to carry a 16-bit Group Policy ID (Security Group Tag / SGT) .

VXLAN-GPO Header Breakdown

Layer Header Component Size Function

Outer Layer 2 Outer Ethernet Header 14 Bytes Next-hop physical switch MAC addresses across underlay hops.

Outer Layer 3 Outer IPv4 Header 20 Bytes Source RLOC (ingress edge) and Destination RLOC (egress edge).

Outer Layer 4 Outer UDP Header 8 Bytes Dest port 4789; source port is a hash of inner packet for ECMP entropy.

Overlay Header VXLAN-GPO Header 8 Bytes Contains G flag, 16-bit SGT , and 24-bit VNI (Virtual Network).

Inner Payload Original Client Frame Variable Original Ethernet frame (Source/Dest MAC, IP, TCP/UDP, and data).

Total encapsulation overhead is 50 bytes , allowing policy (SGT) and multi-tenancy (VNI) to travel inline with every packet.

Fabric Node Roles

An SD-Access fabric organizes devices into distinct functional roles:

Fabric Node Role Placement Primary Responsibilities

Fabric Edge Node Campus Access Layer (e.g., Catalyst 9300) Onboards and authenticates endpoints (802.1X, MAB, WebAuth); maps endpoints to VLANs, VNIs, and SGTs; acts as Anycast Layer 3 Gateway; registers local EIDs with Control Plane; encapsulates egress frames into VXLAN-GPO; decapsulates ingress VXLAN frames and enforces SGACLs.

Fabric Control Plane Node Campus Core/Distribution (e.g., Catalyst 9500) Runs the LISP Map-Server and Map-Resolver; maintains the EID-to-RLOC database; tracks host mobility events across the campus.

Fabric Border Node Campus Core/Edge (e.g., Catalyst 9500/9600) Connects the fabric overlay to external networks (WAN, Internet, traditional campus); translates LISP/VXLAN state to external routing protocols (eBGP, OSPF, VRF-Lite).

Intermediate Node Campus Spine/Core (e.g., Catalyst 9500) Standard Layer 3 underlay router (P router); forwards packets using outer IP headers; unaware of VXLAN, LISP, or SGTs; requires jumbo MTU (9100 bytes recommended).

Fabric Extended Node Wiring Closets / Industrial (e.g., Catalyst IE3300) Layer 2 switch connected downstream to a Fabric Edge; extends segmentation to peripheral ports via 802.1Q without terminating VXLAN.

Border Node Classifications

Internal Border: Connects to corporate data centers and internal services; advertises fabric subnets out and imports enterprise routes.

External Border: Connects to uncontrolled external networks (Internet/Cloud); originates and advertises a default route ( 0.0.0.0/0 ) into the fabric.

Anywhere Border: Combines internal and external border responsibilities on a single platform.

Centralized Orchestration: Catalyst Center and ISE

Cisco Catalyst Center (formerly DNA Center): Central automation and assurance engine. Manages LAN Automation (PnP underlay provisioning via IS-IS), fabric design, and telemetry assurance.

Cisco Identity Services Engine (ISE): Integrates via pxGrid to authenticate endpoints, evaluate posture, assign SGTs dynamically, and propagate security matrices to fabric nodes.