The whole portfolio laid out the way it is actually racked: control towers on top, telemetry and security in the middle, compute / fabric / SAN as the payload, AI rigs at the bottom. Hover or tap any module to trace what it talks to.
Nexus 9000 boots as a classic NX-OS switch or as an ACI leaf/spine. Pick per fabric, before purchase — conversion wipes the box.
| NX-OS mode (+ NDFC) | ACI mode (+ APIC) | |
|---|---|---|
| Control plane | Distributed — BGP/OSPF/IS-IS + VXLAN EVPN on every switch | Centralised — APIC pushes policy; switches run a thin image |
| Configuration model | CLI/NETCONF/gNMI per device; NDFC for fabric intent | Object model (tenant/VRF/BD/EPG/contract); no switch CLI config |
| Segmentation | VLAN/VRF/VNI + ACLs; TrustSec optional | Contracts = default-deny allow-list (zero trust by construction) |
| Multi-site | VXLAN Multi-Site with Border Gateways via NDFC/NDO | Multi-Pod / Multi-Site via NDO; Remote Leaf; Cloud Network Controller |
| Virtualisation | NDFC vCenter plugin only | VMM domains: vCenter, Hyper-V, OpenStack, K8s/OpenShift, AHV |
| Lab | Nexus 9300v/9500v (full control plane) | ACI Simulator (policy/API only, no data plane) |
| Best fit | Open standards, mixed vendors, traditional net-ops | Multi-tenant, regulated, policy-driven, multi-site |
The same request touches every plane. Order matters — identity and fabric before storage, storage before security, security before go-live.
East-west packet walk (VXLAN EVPN + microsegmentation) VM-A (Leaf1, VNI 30010) ─► Secure Workload host policy permits tcp/443 ─► Leaf1 EVPN type-2 lookup for VM-B ─► VXLAN encap (anycast GW, symmetric IRB) ─► ECMP Spine1/Spine2 (IS-IS/OSPF underlay · BGP EVPN overlay) ─► Leaf3 decap ─► (optional) ePBR ─► FTD cluster ─► VM-B Telemetry: flow record → NDI · host flow → Secure Workload · both → Splunk
Every tier keeps the same three zones. Controllers and data plane live in trust; only the bastion, firewall, proxy and probes sit in the DMZ; untrust is the outside world.
DoD baseline first, then the Vanta 38-framework catalog reuses the same 800-53 control evidence. Everything exports to Splunk + Git, so one evidence pipeline serves every framework.