Networking / Data Center / Procurement / Comparison / Enterprise / Midmarket

Is the fabric ACI on Nexus, or NSX on the host overlay?

DC network virtualization RFQs pair Cisco ACI with VMware NSX-T—not Extreme Fabric or Catalyst Center. Nexus underlay gravity vs hypervisor overlay policy decides TCO.

Quick Take

Quick Take: Cisco ACI and VMware NSX-T (VCF-adjacent) are peer data-center network virtualization planes when the brief is policy segmentation and east-west control—not campus PoE closets. ACI pulls Nexus underlay gravity; NSX pulls vSphere overlay gravity. Peer EPG/contracts vs NSX segments on equal 3–5 year license terms. Soft channel net is an industry estimate / pending confirmation—do not invent optics or SKU list prices. BENQUAN GLOBAL LIMITED supplies both.

Verizon 2025 DBIR (industry-wide, not a product score): exploitation of vulnerabilities opened 20% of breaches; edge devices and VPN were 22% of those exploitation targets; median time to remediate was 32 days. Use that urgency to fund a matched dual-RFQ—not to rank ACI above NSX on a sticker.

When ACI vs NSX Actually Matters

Quick Answer: Use the Cisco ACI versus VMware NSX comparison when procurement must choose a data center network virtualization and policy plane covering segmentation, contracts and distributed firewalling. It is the wrong comparison when the brief is campus access switching or wireless dashboards, which are answered by different peer guides entirely.

Threads titled "ACI vs NSX" fail when buyers compare NSX to Extreme Fabric or Catalyst Center—or when one quote is APIC+Nexus underlay and the other is NSX licenses without stating underlay ownership or VCF bundle scope.
ACI
Nexus Underlay
NSX-T
Hypervisor Overlay
VCF
License Adjacency
Dual
Vendor RFQ
  • DC fabric intent: Application-centric policy, micro-segmentation, and automated provisioning across server racks—not VLAN templates on standalone ToR switches.
  • Dual-vendor discipline: Equalize controller scope, license term, underlay ownership, and change workflow before comparing feature matrices.
  • Not campus fabric: For Extreme Fabric Engine vs ACI campus-to-DC ops, use Extreme Fabric vs ACI—a different peer question.
  • Not leaf SKU peers: For Nexus 9300 vs Arista leaf hardware, use the dedicated leaf guides—this page is the overlay/policy ops plane.

Typical dual-quote scenes (not named customers)

  • Overlay license ranked against full Nexus underlay BOM: NSX subscription alone looks cheaper until APIC + leaf/spine + optics appear on the ACI column—and the award reopens.
  • vSphere estate, Nexus already standard: Dual-RFQ both; do not assume NSX wins on hypervisor gravity alone when fabric-native policy is mandatory.
  • Nexus not locked, NSX still required: Add Arista underlay as a third column so underlay ownership stays explicit.

When Extreme Fabric or DNA Center Is the Wrong Comparison

Quick Answer: Extreme Fabric and Cisco Catalyst Center solve campus policy and switch management, so neither is a fair peer to VMware NSX. Compare NSX with Cisco ACI on data center segmentation, and compare Catalyst Center with Arista CloudVision or Aruba Central on campus operations. Mixing the two axes mis-ranks vendors on price.

Brief type Correct peer guide Why ACI vs NSX is wrong here
Campus+DC policy fabric (non-VMware) Extreme Fabric vs ACI Extreme Fabric Engine competes with ACI on campus segmentation—not NSX hypervisor overlay
Campus management plane CloudVision vs Catalyst Center DNA/Central solve switch onboarding and templates—not DC EPG contracts or NSX DFW
DC leaf hardware only Nexus vs Arista leaf Port counts and optics peers without policy controller scope mis-rank vendors
DC network virtualization This page ACI and NSX-T both sell automated segmentation in the data center

Decision rule

If the stakeholder asks "who manages our campus switches?" → DNA vs Central or CloudVision. If they ask "how do we enforce application policy in the DC with VMware estates?" → ACI vs NSX. Mixing campus ops and DC virtualization on one RFQ produces incomparable quotes.

Underlay vs Overlay Gravity — Nexus Hardware vs Hypervisor Overlay

Quick Answer: Cisco ACI anchors on a Nexus leaf-spine underlay with APIC policy, while VMware NSX anchors on a vSphere or VMware Cloud Foundation hypervisor overlay that can ride a third-party underlay. Whichever platform already owns compute and operations skill usually wins day-two, regardless of which feature matrix looks stronger during evaluation.

Dimension Cisco ACI VMware NSX-T
Policy controller APIC cluster (on-prem or cloud-managed variants per design) NSX Manager / policy plane (VCF-integrated in greenfield builds)
Underlay default Nexus 9300-class leaf-spine (VXLAN EVPN common) Any L3 underlay—often existing Nexus, Arista, or Juniper leaf-spine
Overlay model ACI fabric + EPG/BD abstraction Geneve/VXLAN overlay + logical switches/routers on hypervisor
Gravity source Nexus hardware estate, NX-OS/ACI certifications vSphere clusters, VCF bundles, existing NSX skill
East-west security Contracts between EPGs (service graph optional) Distributed Firewall (DFW) at hypervisor vNIC
Bare metal / containers ACI static paths, opflex adjacency (design-dependent) NSX bare-metal agents, NCP/K8s integrations (design-dependent)

Underlay is not free on either path

ACI quotes must include Nexus leaf/spine SKUs, optics, and APIC. NSX quotes must state who owns the underlay—if Nexus is not already standardized, add a parallel underlay RFQ using Nexus vs Arista spine and leaf peers.

Policy Model Honesty — ACI EPGs vs NSX Segments

Quick Answer: Cisco ACI expresses policy through application network profiles, endpoint groups and contracts, while VMware NSX expresses it through segments, groups and distributed firewall rules. Force both vendors to map the same application tiers and security zones, otherwise the two designs default to different permit assumptions and the quotations stop being comparable.

Policy element Cisco ACI VMware NSX-T
Workload grouping EPG (Endpoint Group) Segment / NSGroup
Traffic permit/deny Contract (filter + action) DFW policy (L2–L7 rules)
Service insertion Service graph / L4–L7 devices Service insertion / advanced security partners
Automation API APIC REST / Terraform providers NSX API / Terraform / VCF automation
Multi-site Multi-Site / Multi-Pod (license-dependent) Multi-site / Federation (license-dependent)
If one vendor maps "three-tier web app" to EPGs and the other maps the same tiers to NSX segments with different default-deny assumptions, stop ranking. Fix the security zone brief first—then re-quote.

Broadcom VMware Licensing Honesty — NSX-T and VCF Adjacency

Quick Answer: After the Broadcom acquisition, VMware NSX entitlements often arrive bundled with VMware Cloud Foundation or vSphere subscription tiers rather than legacy per-socket add-ons. Force every quotation to state edition, scope, term and which modules are included versus optional, and match Cisco ACI license and support years to the same term.

  • No public list prices here: Subscription models change by region, channel, and bundle. Compare quoted 3–5 year TCO from your distributor—not blog sticker numbers.
  • VCF adjacency: Greenfield VMware estates may receive NSX as part of VCF packaging. Confirm whether NSX Advanced Load Balancer, Federation, or security partners are included or add-on.
  • Edition clarity: Force the quote to name NSX edition (e.g., standard vs advanced capabilities relevant to your DFW and multi-site needs) and hypervisor socket/core entitlement.
  • ACI license parity: Match ACI APIC, spine/leaf fabric licenses, and support years to the NSX subscription term—do not compare a 1-year NSX pilot to a 5-year ACI EA.
  • Exit risk: If Broadcom renewal is already stressed, read VMware Broadcom renewal options before locking NSX on a 5-year subscription.

Licensing trap

An NSX line item without VCF/vSphere context is incomplete. An ACI line item without APIC count and fabric mode is incomplete. Both sides must answer: what is automated on day-1 vs CLI-adjacent on day-2?

When Arista / CloudVision Underlay Is the Third Column

Quick Answer: Add an Arista leaf-spine underlay managed by CloudVision as a third column when Nexus is not locked in but data center network virtualization is still required. NSX on an Arista underlay against Cisco ACI on Nexus is a common three-way request for quotation, and it keeps underlay ownership explicit.

  • NSX + Arista underlay: Common when vSphere is standardized but Nexus leaf-spine is not. NSX overlay rides EVPN-VXLAN on Arista 7050X3/7280-class fabric—see Arista vs Juniper leaf for hardware peers.
  • ACI + Nexus underlay: Default Cisco gravity—APIC owns fabric policy end-to-end when Nexus is already the DC standard.
  • CloudVision ops: If campus is EOS/CloudVision and DC must match ops tooling, Arista underlay + NSX may beat ACI + Nexus for NOC consistency—compare on CloudVision vs Catalyst Center skill first.
  • Spine peer: Underlay RFQs should include spine comparison—Nexus vs Arista spine on the same port and optics brief.

Three-column discipline

Column A: ACI + Nexus. Column B: NSX + stated underlay (existing or quoted). Column C (optional): NSX + Arista underlay when Nexus is not approved. Do not drop a column until TCO and ops skill risk close.

HCI and Compute Adjacency — VCF, VxRail, Nutanix

Quick Answer: VMware NSX gravity follows the hypervisor platform underneath it. VMware Cloud Foundation and Dell VxRail estates pull NSX adjacency, while Nutanix AHV estates rarely need NSX at all. Align the network virtualization request for quotation with the compute shortlist, or you may buy an overlay the chosen platform never uses.

Compute path Network virtualization implication Peer guide
VMware VCF / vSphere NSX-T is the natural overlay peer to ACI; VCF bundles affect license scope Nutanix vs vSAN (if HCI is in play)
Dell VxRail VxRail + VCF stacks often include NSX adjacency—confirm bundle vs build-your-own VxRail vs Nutanix HCI
Nutanix AHV Flow microsegmentation replaces NSX for many Nutanix estates—ACI vs NSX may be wrong question VxRail vs Nutanix
Bare metal / mixed ACI static binding or NSX bare-metal agents—state workload mix on RFQ This page + underlay spine guide
If the compute RFQ is pivoting from VMware to Nutanix, revisit whether NSX belongs on the network BOM at all—network and HCI decisions must close together.

RFQ Checklist — Dual Fabric BOM on One Brief

Quick Answer: Write one data center segmentation brief, then request two columns: Cisco ACI with APIC controllers and Nexus fabric, and VMware NSX with its policy plane and a named underlay. Match license years on both sides and add an optional Arista underlay third column when the fabric vendor is still open.

What to put on the RFQ

  • DC scope: rack count, workload types (VM, bare metal, K8s), east-west firewall intent
  • Security zones: map application tiers both vendors must segment
  • ACI: APIC count/HA, fabric mode, Nexus leaf/spine SKUs, optics, license + support term
  • NSX: edition, Manager deployment, hypervisor socket/core count, VCF bundle scope if applicable
  • Underlay ownership: existing fabric vs new leaf-spine quote (name vendor)
  • Multi-site: state if Multi-Site / Federation is required on both sides
  • Service insertion: L4–L7 partners if mandated by security architecture
  • License term: match years; state Broadcom subscription model assumptions
  • Ops skill: ACI-certified vs NSX-certified staff availability
  • Lead time: controllers, switches, optics—quote validity window

Use SKU Lookup for Nexus hardware, then submit the dual-vendor brief on rfq.html.

Frequently Asked Questions

Quick Answer: Compare Cisco ACI and VMware NSX on data center policy scope, underlay ownership and matched license years, then let Nexus hardware gravity or hypervisor gravity decide after a dual request for quotation. Neither platform is universally better, and campus switch management tools are not valid peers in this evaluation.

Yes for data center network virtualization—not for campus fabric or switch management. Dual-RFQ matched segmentation briefs with stated underlay on both sides.

NSX adjacency is strong on vSphere/VCF estates. ACI still wins when Nexus underlay and ACI skill are standardized, or when hardware policy must be fabric-native. Dual-RFQ both before assuming gravity.

NSX often bundles with VCF/vSphere subscriptions. Force edition, scope, and term on the quote—compare 3–5 year TCO, not legacy per-socket assumptions.

When Nexus is not locked but NSX overlay is still required—NSX on Arista EVPN underlay vs ACI on Nexus. Use the Nexus vs Arista spine guide for underlay peers.

Submit one RFQ with the dual-vendor checklist above.

References

Key Takeaway

Key Takeaway: Cisco ACI and VMware NSX-T are peer DC network virtualization planes with different gravity—Nexus underlay vs hypervisor overlay. Win on policy zone mapping, license term honesty, and underlay ownership—then standardize. BENQUAN GLOBAL LIMITED supplies both with competitive pricing and configuration support for global buyers.

Not sure your DC fabric BOM is optimal?

If ACI vs NSX policy scope, Nexus underlay ownership, or Broadcom NSX licensing terms are unclear, click below for a free compatibility and delivery risk assessment. Fast global BOM validation and risk assessment.

Free Compatibility & Delivery Risk Assessment

Or call +852-21349834 · info@benquan.hk

Contents