Moving Beyond ACI: Why Data Center Teams Are Standardizing on Nexus Dashboard and NX-OS VXLAN EVPN

The Question That’s Changed

Not long ago, the central question for a Cisco data center build was: ACI or NX-OS standalone? ACI won a lot of those decisions. Its policy model, APIC-driven automation, and tight integration with VMware NSX made it the go-to answer for enterprise data centers that needed centralized control and microsegmentation at scale.

That question hasn’t disappeared, but it’s evolving. In 2025 and into 2026, the more relevant framing is: how do you operate all of it through a single management layer? And the answer to that question is increasingly Nexus Dashboard — with NX-OS VXLAN EVPN becoming the default fabric choice for new builds.

This isn’t a formal ACI end-of-life announcement. Cisco has not published one, and ACI continues to receive investment, including expanded Group Policy Object (GPO) features, enhanced Border Gateway functionality in ACI 6.2, and improved multi-pod and multi-site capabilities. But the direction of Cisco’s broader data center strategy is getting clearer, and organizations planning their next refresh cycle should understand what’s driving this shift.

What ACI Got Right — and Where It Gets Hard

ACI was genuinely innovative when it launched. The policy model — tenants, application profiles, endpoint groups, contracts — abstracted network policy away from VLANs and ACLs into something closer to how application teams think about connectivity. The APIC gave operators a single controller for the fabric. Multi-site and multi-pod extended that model across geographies.

The friction shows up in operations:

ACI expertise is narrow. An engineer who understands ACI policy constructs deeply — EPGs, bridge domains, VRFs, shadow EPGs, L3Outs, contracts — holds valuable and specific knowledge, but that knowledge doesn’t transfer to Arista, Juniper, Nokia, or even standalone NX-OS environments. In a tight hiring market, that specialization becomes a risk.

Troubleshooting lives in a different mental model. When something breaks in ACI, you’re debugging through policy abstractions. Packet walks, contract drops, shadow EPGs, and zoning rules layer on top of the underlying VXLAN fabric in ways that aren’t always intuitive. Teams running NX-OS VXLAN EVPN deal with BGP route types, VTEP reachability, and ARP suppression — complexity to be sure, but complexity that maps directly to transferable networking knowledge.

APIC is an island. Historically, ACI’s APIC controller didn’t integrate cleanly with the rest of Cisco’s management ecosystem. Nexus Dashboard was built to fix this — ACI is now managed as one of multiple fabric types within ND, alongside NX-OS fabrics, IOS-XE, and SONiC.

The Nexus One Fabric Signal

In late 2024, Cisco announced Nexus One Fabric — arguably the strongest public signal about where the company is taking its data center strategy. The concept is direct: converge ACI and NX-OS VXLAN EVPN fabrics under a single operating model, with Nexus Dashboard as the unified management plane.

What Nexus One Fabric delivers:

• A common data, control, policy, and management plane across NX-OS VXLAN EVPN and ACI fabrics
• Automated multi-fabric connectivity and interoperability between NX-OS VXLAN EVPN and ACI through APIC federation
• Consistent end-to-end segmentation, L4–L7 service insertion, and policy management regardless of underlying fabric type
• Seamless Layer 2/Layer 3 network extension between heterogeneous fabric types

The practical implication: organizations don’t need to rip out ACI to gain the benefits of the Nexus Dashboard operating model. They can run ACI and NX-OS VXLAN EVPN simultaneously, managed through a single Nexus Dashboard cluster, with consistent policy and visibility across both.

Why NX-OS VXLAN EVPN Is Winning New Builds

For greenfield deployments and refresh cycles, NX-OS VXLAN EVPN managed by Nexus Dashboard Fabric Controller (NDFC) is increasingly the default choice. Several factors drive this:

Open standards portability. VXLAN EVPN is an industry-standard overlay used by Cisco, Arista, Juniper, Nokia, and virtually every other data center networking vendor. An engineer who understands BGP EVPN route types (2 for MAC/IP, 5 for IP prefix), symmetric and asymmetric IRB, and multihoming techniques carries that knowledge across vendor environments. ACI expertise is valuable, but it’s vendor-specific.

DCNM end of support. Cisco’s Data Center Network Manager (DCNM) — the longtime management platform for NX-OS fabrics — reached end of support in April 2026. NDFC running on Nexus Dashboard is its replacement. Organizations still running DCNM are already overdue for migration.

Hiring and skill set breadth. Teams can hire engineers with general VXLAN EVPN and BGP skills and get them productive quickly. ACI requires more specialized ramp-up time and the pool of experienced ACI engineers is narrower.

AI workload requirements. The explosion of GPU clusters and AI training workloads is creating new data center network requirements — specifically, fat-tree topologies with lossless fabric, RDMA over Converged Ethernet (RoCE), and very low latency. These workloads don’t fit neatly into ACI’s application-centric policy model, but map well to NX-OS with EVPN overlays and appropriate QoS configuration.

What Nexus Dashboard Brings to This Migration

Whether you’re running ACI, NX-OS, or both, Nexus Dashboard is the operational platform that makes the transition manageable. Here’s what it delivers that standalone APIC or DCNM couldn’t:

Unified Visibility Across Fabric Types

Nexus Dashboard Insights (NDI) provides real-time telemetry, anomaly detection, and assurance across ACI fabrics, NX-OS fabrics, and hybrid combinations simultaneously. Before ND, operators needed separate tools and separate mental models for each fabric type. NDI surfaces everything — interface errors, flow anomalies, policy drops, bug advisories — in one place.

Fabric Controller for NX-OS Automation

NDFC’s Easy Fabric workflow provisions a complete VXLAN BGP EVPN underlay and overlay in minutes: fabric creation, switch discovery, underlay deploy, VRF and network creation, overlay deploy. It auto-generates IS-IS or OSPF underlay, iBGP EVPN overlay, PIM/anycast-RP multicast, and per-VRF route targets — removing most of the manual configuration work and reducing the risk of human error.

Multi-Site Orchestration Without the Complexity

Nexus Dashboard Orchestrator (NDO) manages multi-fabric connectivity across sites — stretching policy, VRFs, and networks between ACI fabrics, NX-OS fabrics, and hybrid combinations. Organizations that previously used NDO purely for ACI multi-site can now use it to manage connectivity between ACI and NX-OS fabrics at different sites — a key enabler for gradual migration strategies.

Infrastructure-as-Code at the Fabric Level

NDI and NDFC both expose APIs and support Terraform and Ansible integration. Network configurations become version-controlled, reviewable, and automatable. Organizations moving toward platform engineering models — where network changes go through the same CI/CD pipelines as application code — get a much cleaner path with NDFC than with standalone ACI APIC.

AI-Driven Anomaly Detection

Nexus Dashboard provides AI-driven intelligence to maximize AI network performance with Cisco Intelligent Packet Flow and advanced analytics to accelerate troubleshooting. For data centers supporting GPU workloads where a single fabric anomaly can cascade into degraded training performance across an entire cluster, proactive detection isn’t a nice-to-have — it’s operationally essential.

Market Trends Driving the Shift

Several broader forces are accelerating this migration beyond the technical merits:

Platform consolidation pressure. According to Cisco’s 2024 Global Networking Trends report, one in five organizations still rely on separate management systems for campus, branch, WAN, data center, and multicloud environments. Encouragingly, 39% of organizations have already begun transitioning to a platform-based architecture, with 72% of IT leaders anticipating platform adoption across at least one network domain by 2026. Nexus Dashboard is Cisco’s answer to that consolidation imperative.

DCNM replacement urgency. With DCNM end of support now reached, any organization running NX-OS fabrics through DCNM is running on unsupported software. The migration to NDFC on Nexus Dashboard isn’t optional — it’s a support lifecycle issue.

ACI renewal economics. ACI’s licensing model has become a point of friction for some organizations at renewal time. NX-OS with NDFC carries a different licensing structure, and for organizations where ACI’s policy model isn’t being fully utilized, the economics of switching become more attractive.

Talent and certification alignment. The market is shifting from ACI-heavy deployments to VXLAN EVPN standalone fabrics managed by NDFC. Engineers who can provision, operate, and troubleshoot NDFC-managed VXLAN EVPN fabrics are positioning themselves for the next wave of data center deployments. Cisco has already updated the CCIE Data Center blueprint to explicitly include Nexus Dashboard with Fabric Controller and remove DCNM.

AI infrastructure demands. The build-out of AI training infrastructure is pulling data center networking toward simpler, high-performance overlays optimized for GPU-to-GPU communication patterns. Treating front-end, storage, and back-end networks as operational islands is a recipe for wasted GPU cycles and inflated costs. The unified management plane spanning Cisco Nexus Dashboard and Cisco Nexus Hyperfabric is what enables organizations to squeeze maximum performance out of their AI investments.

This Isn’t Rip and Replace

The critical point for organizations with existing ACI investments: Nexus One Fabric and Nexus Dashboard are explicitly designed to support coexistence, not forced migration.

The practical path for most organizations looks like this:

1. Onboard existing ACI fabrics into Nexus Dashboard for unified visibility, insights, and orchestration — without changing anything about the ACI fabric itself
2. Migrate DCNM-managed NX-OS fabrics to NDFC — this is not optional given DCNM’s end of support, and it’s a relatively well-defined migration path
3. For new sites or refresh cycles, standardize on NX-OS VXLAN EVPN managed by NDFC as the default fabric choice
4. Use NDO to bridge ACI and NX-OS fabrics at sites where both exist, maintaining consistent policy across the heterogeneous environment
5. Evaluate ACI at renewal on a site-by-site basis rather than making a blanket migration decision

If you run ACI today, this does not mean rip and replace. It does mean the default choice for the next build, expansion, or refresh increasingly looks like EVPN.

The Bottom Line

The data center networking market is converging on a model where the underlying fabric type matters less than the operational platform sitting above it. Nexus Dashboard is Cisco’s answer to that convergence — a unified management, visibility, and orchestration layer that works across ACI, NX-OS VXLAN EVPN, IOS-XE, and SONiC fabrics simultaneously.

For organizations running ACI: Nexus Dashboard adds value immediately, without requiring a migration. For organizations planning new builds: NX-OS VXLAN EVPN managed by NDFC is increasingly the engineering default. For organizations still on DCNM: the migration to NDFC is overdue and should be the immediate priority.

The shift isn’t about ACI being wrong. It’s about where the center of gravity in Cisco’s data center portfolio is moving — and that center of gravity is Nexus Dashboard.