Cisco ACI’s standalone architecture is being absorbed into the broader NX-OS VXLAN EVPN ecosystem. While Cisco hasn’t issued a formal end-of-life notice, their Nexus One strategy, aggressive EVPN feature additions to NX-OS, and industry feedback all point to the same conclusion: CCIE Data Center candidates should be investing the majority of their study time in EVPN fabric skills, not ACI-specific knowledge.
Key Takeaway: Cisco’s Nexus One initiative is converging ACI and NX-OS under unified VXLAN/EVPN standards — if you’re preparing for CCIE DC or planning your next data center refresh, EVPN fabric expertise is the skill with the longest career runway.
What Is Actually Happening to Cisco ACI?
Cisco ACI is not being killed overnight — it’s being strategically absorbed. In November 2025, Cisco launched the Nexus One Fabric initiative, which Cisco’s own blog describes as “bringing together the power of Cisco ACI and NX-OS through a unified architecture built entirely on the open standards we helped define.”
That’s corporate language for: ACI’s proprietary policy model is being replaced by open VXLAN/EVPN standards, and both fabrics will be managed through Nexus Dashboard.
Here’s the convergence roadmap based on Cisco’s public announcements:
| Component | ACI (Legacy) | Nexus One (Future) |
|---|---|---|
| Data Plane | VXLAN with ACI-specific headers | Standard VXLAN/EVPN (RFC 7432) |
| Control Plane | APIC controller (proprietary) | BGP EVPN (open standard) |
| Policy Model | ACI contracts, EPGs, tenants | Unified policy via Nexus Dashboard |
| Management | APIC GUI/API | Nexus Dashboard (unified for both) |
| Multi-site | ACI Multi-Site (MSO) | EVPN Multi-Site (standards-based) |
According to CRN (2026), Cisco enhanced Nexus One at Cisco Live EMEA 2026 to deliver “a consistent experience across the two fabrics by way of the Cisco Nexus Dashboard.” The message is clear: one management plane, one operational model, and that model is built on open EVPN standards — not ACI’s proprietary abstractions.
What Are Network Engineers Actually Seeing in the Field?
The Reddit thread “ACI: Growing, Shrinking, or Staying the Same?” on r/networking is one of the most telling data points. The original poster — a working data center engineer — laid out what they’re observing:
“My perception is that as data center infrastructures come up for renewal, if the current platform is ACI, often the next one will be EVPN/VXLAN (even if the company sticks with Cisco). I also don’t think anyone is moving TO ACI from something else.”
One highly-upvoted comment went further: “I think Cisco will sunset ACI. If you look at the EVPN-related release notes of NX-OS you’ll see they’ve been going HARD making NX-OS the best.”
This matches what I’ve seen across multiple enterprise refreshes. The pattern is consistent:
- ACI renewal comes up → organization evaluates options
- Operational complexity complaints surface — ACI’s policy model requires specialized training, and most network teams find it unintuitive compared to CLI-based NX-OS
- EVPN/VXLAN on NX-OS wins — same Cisco hardware, simpler operations, open standards, multivendor interoperability
- Nobody is moving TO ACI — net new deployments overwhelmingly choose standalone EVPN/VXLAN
Why Did ACI Fail to Deliver on Its Promise?
ACI launched with an ambitious vision: intent-based networking for the data center with a centralized controller (APIC) managing all policy. In theory, it was elegant. In practice, several factors undermined adoption:
Operational Complexity: ACI introduced an entirely new operational model — tenants, application profiles, EPGs, contracts, bridge domains — that didn’t map to how network teams actually think. Engineers who spent years mastering NX-OS CLI had to learn a fundamentally different paradigm.
Underused Features: The original poster on Reddit nailed it: ACI could do things EVPN/VXLAN couldn’t — “tenant-based API configuration, overlapping VLAN IDs, simple zero-trust networking” — but “for various reasons those were features we (the network community) never really used.” The complexity premium had no payoff.
Vendor Lock-in: ACI’s proprietary policy model meant you were locked into Cisco switches and APIC controllers. In an era where organizations increasingly demand multivendor flexibility — especially with AI workloads driving interest in alternatives and open fabrics — this became a liability rather than an advantage.
The AI Workload Shift: According to LinkedIn data (2026), 75% of new data center investment is shifting toward AI-optimized infrastructure. AI workloads demand flexible, programmable fabrics that can scale horizontally — not rigid SDN controllers with fixed policy models. EVPN/VXLAN’s flexibility makes it naturally suited for AI data center networking.
What Does This Mean for CCIE Data Center Candidates?
The CCIE DC v3.1 blueprint already reflects this shift. According to INE’s lab guide (2026), the blueprint covers both ACI and NX-OS VXLAN EVPN, but the EVPN sections are substantially broader:
CCIE DC v3.1 Blueprint Coverage:
- Section 3.0 (Data Center Fabric Connectivity): VXLAN EVPN overlay fabrics, multi-site, multi-pod — all virtualizable and testable
- ACI Topics: Still present but increasingly treated as one of several fabric options, not the primary focus
- Automation: Both ACI API and NX-OS NXAPI/Ansible — but NX-OS automation skills transfer to every other vendor
Here’s my recommended study time allocation for CCIE DC candidates in 2026:
| Topic Area | Recommended Time | Why |
|---|---|---|
| VXLAN EVPN Fundamentals | 30% | Core fabric technology — BGP EVPN, VTEPs, symmetric/asymmetric IRB |
| EVPN Multi-Site/Multi-Pod | 15% | Blueprint weight + real-world demand |
| NX-OS Advanced Features | 15% | vPC, FEX, OTV, FabricPath migration |
| ACI Fabric | 20% | Still on the exam, know the policy model |
| Automation (NXAPI, Ansible) | 10% | Essential for modern DC operations |
| Storage/Compute Integration | 10% | FC, FCoE, UCS — still tested |
For hands-on EVPN practice, our guide on VXLAN EVPN Multi-Homing with ESI on Nexus covers one of the most commonly tested — and interviewed — topics in depth.
Is VXLAN EVPN Really Better Than ACI?
VXLAN EVPN wins on the dimensions that matter most to network teams in 2026. Here’s the honest comparison:
| Dimension | ACI | NXOS VXLAN EVPN |
|---|---|---|
| Operational simplicity | Complex — new paradigm | Familiar — CLI-based, incremental learning |
| Multivendor | Cisco-only | Arista, Juniper, Nokia all support EVPN |
| Scalability | Good (spine-leaf within APIC domain) | Excellent (standards-based multi-site) |
| Automation | ACI API (proprietary) | NXAPI, Ansible, Terraform (transferable) |
| Talent pool | Shrinking (fewer ACI-trained engineers) | Growing (EVPN is industry standard) |
| AI fabric readiness | Limited flexibility | Native fit for GPU cluster fabrics |
| Career transferability | Cisco ACI only | Any EVPN vendor |
Where ACI still has an edge: micro-segmentation policy (contracts between EPGs are genuinely powerful) and Day 0 provisioning for greenfield sites. But Cisco’s Nexus Dashboard is rapidly bringing those capabilities to standalone NX-OS fabrics through the Nexus One initiative.
According to Cisco’s own documentation (2026), Nexus One offers “unified management across NX-OS VXLAN EVPN and Cisco ACI fabrics” with “deep observability” via native Splunk integration. Translation: everything ACI did differently is being made available in NX-OS, removing the last reasons to choose ACI.
What Should You Do If You’re Running ACI Today?
If you’re currently operating an ACI fabric, don’t panic — but do start planning:
Evaluate your renewal timeline. When does your current ACI hardware hit end-of-support? That’s your migration window.
Start building EVPN skills now. Set up a lab with NX-OS 10.x and practice VXLAN EVPN fabric configurations. CML or EVE-NG both support Nexus 9000v.
Deploy Nexus Dashboard. Even on your existing ACI fabric, Nexus Dashboard gives you the unified management plane. This de-risks the eventual migration.
Document your ACI policies. Map your tenants, EPGs, and contracts to equivalent EVPN constructs (VRFs, VNIs, route-maps). This is the hardest part of migration and benefits from early planning.
Talk to your Cisco SE. Cisco’s field teams are actively helping customers plan ACI-to-EVPN migrations. They have reference architectures and migration playbooks.
Frequently Asked Questions
Is Cisco officially discontinuing ACI?
Cisco hasn’t announced a formal end-of-life for ACI. However, their Nexus One strategy converges ACI and NX-OS under unified VXLAN/EVPN standards, effectively absorbing ACI’s capabilities into the broader NX-OS ecosystem. This is a soft sunset — the technology lives on in a different form, but ACI as a standalone product with a distinct operational model is clearly in its twilight.
Should CCIE Data Center candidates still study ACI?
Yes, but with the right proportions. The CCIE DC v3.1 blueprint covers both ACI and NX-OS VXLAN EVPN. I’d recommend focusing 60-70% of your study time on EVPN fabric fundamentals and 30-40% on ACI — enough to pass the exam but weighted toward the technology with the longer career runway. According to INE (2026), all EVPN topics can be fully practiced using virtualization.
What is Cisco Nexus One?
Nexus One is Cisco’s unified data center fabric solution that brings together ACI and NX-OS VXLAN EVPN fabrics under a single management plane (Nexus Dashboard). According to Cisco (2026), it offers unified management, deep observability with native Splunk integration, and consistent policy enforcement across heterogeneous fabrics. It represents Cisco’s strategic direction for data center networking.
Is VXLAN EVPN harder to learn than ACI?
VXLAN EVPN requires deeper understanding of BGP address families, VTEP configuration, and overlay networking fundamentals. However, this knowledge is more transferable across vendors — Arista, Juniper, and Nokia all use EVPN — compared to ACI’s proprietary policy model. Engineers with strong BGP and MPLS backgrounds (especially CCIE SP holders) will find EVPN concepts very familiar.
Can ACI and NX-OS EVPN fabrics coexist?
Yes, and Cisco’s Nexus One initiative is specifically designed for this. According to Cisco Live presentations (2026), Nexus Dashboard can manage both ACI and NX-OS EVPN fabrics simultaneously, with EVPN border gateways providing inter-fabric connectivity. This allows organizations to migrate incrementally rather than doing a forklift replacement.
Ready to fast-track your CCIE Data Center journey with the right focus on EVPN fabric skills? Contact us on Telegram @phil66xx for a free assessment.