Cisco NDFC-Managed Spine-and-Leaf Architecture: An Analytical Model for Deterministic, Automated VXLAN EVPN Data-Center Fabrics
DOI:
https://doi.org/10.70917/ijcisim-2026-5216Keywords:
Spine-and-Leaf, Clos Fabric, VXLAN EVPN, Data-Center Networking, Network Automation, ECMP, Deterministic LatencyAbstract
Data-center workloads driven by artificial-intelligence training, cloud-native services, and distributed microservices have outgrown the three-tier network designs that once served enterprise applications. Hierarchical aggregation with the Spanning Tree Protocol wastes capacity on blocked links and introduces variable path lengths that modern east-west traffic cannot tolerate. Spine-and-leaf fabrics built on the Clos principle answer these challenges by offering equal-cost multipath forwarding, predictable hop counts, and horizontal scale-out, and VXLAN with a BGP EVPN control plane extends multi-tenant Layer-2 semantics across a routed underlay. Operating such a fabric by hand does not scale, so controller-based automation has become central to the design rather than an accessory. This paper analyzes the Cisco Nexus Dashboard Fabric Controller as the automation layer of a spine-and-leaf VXLAN EVPN fabric and develops a compact analytical model that links the number of spine switches to equal-cost path diversity, oversubscription ratio, bisection bandwidth, and fabric availability. The model is evaluated across representative fabric configurations, showing how spine count sets both the performance envelope and the resilience of the fabric and how a non-blocking ratio is reached at a determinable spine count. A mapping of controller functions to fabric lifecycle stages clarifies where automation reduces configuration drift and operational risk. The analysis indicates that deterministic performance at scale is an emergent property of three decisions taken together, namely a Clos topology, an EVPN control plane, and controller-enforced automation, and that treating any one in isolation understates the design. Migration and operational-expertise trade-offs are discussed to frame practical adoption.