Study guide
2.3 SD-Access Campus Interoperability: Integrating Traditional Networks with Fabric
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.3 SD-Access Campus Interoperability: Integrating Traditional Networks with Fabric
Key Takeaways Explain This Topic AI
Phased migration from traditional campus networks to Cisco SD-Access relies on Layer 2 and Layer 3 border handoffs to maintain connectivity, addressing, and default gateways.
Layer 2 Border handoffs extend legacy VLANs across the fabric boundary for temporary brownfield transitions, but carry Spanning Tree dependencies and scale limitations.
Layer 3 Border handoffs map fabric Virtual Networks (VNs) to VRF-Lite instances over routed subinterfaces with dynamic routing (eBGP or OSPF), providing high scalability and Layer 2 fault isolation.
Cisco TrustSec Security Group Tag Exchange Protocol (SXP) propagates SGT-to-IP binding tables over TCP port 64999 to legacy switches and firewalls that lack native VXLAN-GPO hardware support.
Shared enterprise services (DHCP, DNS, ISE, Active Directory) can be accessed across segregated Virtual Networks using fusion router route leaking, border node leaking, or firewall transit inspection.
Last updated: October 2026
SD-Access Campus Interoperability: Integrating Traditional Networks with Fabric
Enterprise campus networks rarely transition to modern software-defined fabrics overnight. Migration occurs incrementally: individual buildings, floors, or wiring closets transition from traditional multi-tier Layer 2/Layer 3 architectures to Cisco SD-Access. During this migration, the SD-Access fabric must interoperate with legacy 802.1Q VLAN trunks, Spanning Tree domains, external firewalls, wireless controllers, and enterprise shared services.
Achieving seamless interoperability requires robust boundary handoffs that preserve network segmentation, maintain policy continuity, and provide uninterrupted client connectivity.
Interoperability Models: Layer 2 vs. Layer 3 Border Handoffs
The Fabric Border Node serves as the architectural demarcation point connecting the SD-Access fabric to traditional networks. Depending on migration requirements, engineers implement Layer 2 or Layer 3 handoffs:
Parameter Layer 2 Border Handoff Layer 3 Border Handoff
Primary Purpose Phased brownfield migration; stretching legacy VLANs across the fabric boundary. Permanent enterprise connection; linking fabric overlays to traditional core, WAN, and DC.
Default Gateway Located on external legacy distribution or core switches. Located on Fabric Edge nodes (Anycast Gateway) or external Layer 3 routers.
Subnet Scope Single IP subnet spans across both fabric and legacy switches simultaneously. Subnets are strictly contained either within the fabric or outside.
Broadcast Handling Broadcast and unknown unicast frames traverse the border into the fabric. Broadcast domains terminate at the border; clean Layer 3 routed boundary.
Spanning Tree (STP) STP BPDUs pass across the border; requires careful STP guard configuration. Zero STP interaction; STP BPDUs are blocked at the routed interface.
Design Longevity Temporary transition mechanism; decommissioned after endpoint migration. Permanent, scalable architectural standard for enterprise production.
Layer 2 Border Handoff Implementation
During early migration phases, renumbering IP addresses on thousands of static endpoints (such as medical devices or printers) is often impractical. A Layer 2 Border Handoff allows endpoints on an existing VLAN to be moved to a Fabric Edge switch while retaining their original IP addresses and keeping their default gateway on the traditional core:
The Fabric Border functions as a bridging node, connecting to the legacy switch over an 802.1Q trunk.
When a migrated host in the fabric communicates with its default gateway on the legacy core, the Fabric Edge encapsulates the frame in VXLAN and sends it to the L2 Border, which decapsulates it and places it on the 802.1Q trunk.
Precautions: Because Layer 2 handoffs extend broadcast domains, administrators must configure spanning-tree bpdufilter or bpduguard selectively to prevent legacy STP Topology Change Notifications (TCNs) from causing widespread MAC flushing. Once all endpoints in a subnet are migrated, the gateway is moved to the Fabric Anycast Gateway and the Layer 2 handoff is removed.
Layer 3 Border Handoff Implementation
A Layer 3 Border Handoff provides a permanent, scalable connection:
The Fabric Border terminates fabric VXLAN encapsulation and connects to an external Fusion Router or Core Switch over routed point-to-point links.
Macro-segmentation is preserved using VRF-Lite : each Virtual Network (VN) in the fabric maps directly to an 802.1Q subinterface and corresponding VRF on the external device.
Routing Protocols: Exterior BGP (eBGP) is preferred between the Fabric Border and the Fusion Router due to granular prefix filtering, independent autonomous system numbers, and BGP community controls; Multi-Area OSPFv2/OSPFv3 is also supported with separate OSPF processes per VRF.
Policy Continuity: Cisco TrustSec SXP
Inside the fabric, micro-segmentation is maintained by carrying the 16-bit Security Group Tag (SGT) inside the VXLAN-GPO header. However, when traffic exits the fabric over a Layer 3 VRF-Lite handoff, the border strips the VXLAN header, converting packets to standard IP frames.
Because legacy switches, data center switches, and firewalls often lack hardware support for inline SGT tagging (Cisco Meta Data, optionally protected by MACsec), security policy context is lost unless an out-of-band protocol is used.
SGT Exchange Protocol (SXP) Architecture
Cisco TrustSec SGT Exchange Protocol (SXP) , published as an IETF informational draft rather than an RFC, transports IP-to-SGT binding tables across network devices lacking inline tagging capability:
Transport: SXP establishes a peering session over TCP port 64999 , authenticated with MD5 passwords.
Roles: The Fabric Border Node (or Cisco ISE) acts as an SXP Speaker , sending IP-to-SGT bindings. Legacy switches or firewalls act as SXP Listeners , receiving the mappings and populating local hardware tables.
Policy Enforcement: When an untagged packet reaches the legacy firewall, the firewall references its SXP table, matches the source IP to its SGT, and enforces role-based Security Group ACLs (SGACLs).
Shared Services Access Architectures
Enterprise infrastructure services (Active Directory, DNS, DHCP, ISE, NTP) must be reachable by endpoints in isolated Virtual Networks (e.g., Users , IoT , Guests ).
Engineers use three primary architectures to provide access across VRF boundaries:
Fusion Router Route Leaking: The Fabric Border hands off VNs to an external Fusion Router via VRF-Lite. The Fusion Router maintains client VRFs alongside a dedicated Shared_Services VRF, using MP-BGP route-target import/export rules to leak shared service prefixes into client VRFs and client subnets back to shared services.
Border Node Local Leaking: High-capacity border platforms (Catalyst 9500/9600) can leak routes between VRFs directly on the border switch using route-target import/export, eliminating separate fusion hardware.
Firewall Transit Inspection: VNs connect via VRF-Lite to distinct zones on a Next-Generation Firewall. The firewall statefully inspects all inter-VN and shared services traffic, preventing lateral movement from compromised endpoints.
Wireless Integration: Fabric-Enabled vs. Over-the-Top (OTT)
Wireless configuration is no longer an ENCOR v1.2 topic, but you still need to recognize how wireless traffic relates to the SD-Access fabric.
Over-the-Top (OTT) Wireless
APs connect to Fabric Edge ports configured as standard access ports and build CAPWAP tunnels to a centralized Wireless LAN Controller (WLC).
Both control signaling and client user data travel inside CAPWAP. The fabric treats CAPWAP packets as opaque IP traffic.
User traffic hairpins back to the central WLC, creating latency and throughput bottlenecks.
Fabric-Enabled Wireless (FEW)
Split Architecture: APs form a CAPWAP control tunnel to the WLC for radio management and client authentication, but user data is handled locally.
Distributed Data Plane: The fabric AP encapsulates client traffic in VXLAN toward the fabric edge switch it connects to, and the edge forwards it across the fabric overlay like wired traffic.
Unified Policy & Anycast Gateway: Wireless clients use the same Anycast Layer 3 Gateway on the Fabric Edge as wired devices. Roaming between APs updates LISP EID-to-RLOC mappings without changing IP addresses or hair-pinning traffic.
Troubleshooting Interoperability
SXP Peering: Check TCP port 64999 connectivity, MD5 authentication, and version negotiation (SXPv4 recommended) using show cts sxp connections and show cts sxp sgt-map .
Border MTU Verification: Ensure subinterface MTUs match external fusion router ports. While underlay links use MTU ≥ 9100, traditional IP links default to 1500 bytes.
Asymmetric Inter-VRF Routing: Verify that return routes for shared services are symmetrically leaked. Route leaks that bypass stateful firewalls cause drops due to state violations.
STP Containment: Use spanning-tree bpdufilter enable on L2 border handoff interfaces where appropriate to prevent legacy STP TCNs from triggering MAC flushing in the fabric.