Cisco Nexus 9000 Series Selection Guide: Which Switch to Buy
For most enterprise leaf, top-of-rack, and fixed-spine projects, start with the Nexus 9300. It has the broadest choice of fixed configurations, from 1G management access to 800G fabrics. Move to another Nexus 9000 family when the architecture creates a specific reason:
- Choose Nexus 9200 for a specialized fixed platform such as the 32-port 800G Nexus 9232E or the 1G management-focused N9K-C92348GC-FX3.
- Choose Nexus 9400 when 400G modularity is required in a compact 4RU chassis.
- Choose Nexus 9500 for a modular 1G-to-400G system with 4, 8, or 16 line-card slots.
- Choose Nexus 9800 for a high-capacity distributed modular spine or super-spine that must scale to 800G.
- Evaluate Nexus 9100 when an AI fabric is being designed around NVIDIA Spectrum-X Ethernet switch silicon.
This family-selection guide builds the shortlist. The data sheet for the final product ID remains required because port breakout, buffer architecture, MACsec scope, ACI support, minimum software, optics, and order status can differ between models that appear to be close relatives. Validate each exact PID before completing the BOM.
Quick Decision: Which Nexus 9000 Family Fits the Design?
Cisco’s current portfolio contains six active Nexus 9000 families. Begin with the deployment role and system architecture. The model numbering does not rank the families by capability.
| Family | System type and speed range | Best starting point when | Important boundary |
|---|---|---|---|
| Nexus 9100 | Fixed 800G AI networking | The design follows an NVIDIA Spectrum-X architecture or requires that silicon and its associated AI networking stack | Software and management options vary by offering; confirm the exact image and reference architecture |
| Nexus 9200 | Specialized fixed platforms, including 1G management and 800G fabric roles | The requirement matches a specific model such as the N9K-C92348GC-FX3 or Nexus 9232E | Older 9200 PIDs have mixed lifecycle states, so the family name alone does not prove orderability |
| Nexus 9300 | Fixed 1G to 800G | A leaf, ToR, border leaf, fixed spine, aggregation, or fixed AI-fabric switch is required | ACI, NX-OS, Hyperfabric, SONiC, MACsec, and buffer support are model-specific |
| Nexus 9400 | 4RU centralized modular, up to 400G | The design needs replaceable expansion modules and mixed port types in a compact chassis | It has one supervisor slot; do not treat it as a smaller version of a dual-supervisor Nexus 9500 |
| Nexus 9500 | 4-, 8-, or 16-slot modular, 1G to 400G | The system needs line-card flexibility, supervisor redundancy, or gradual expansion across multiple speeds | The chassis, supervisor, fabric module, line card, fan, and power combinations must be validated as one system |
| Nexus 9800 | 4- or 8-slot distributed modular, 100G to 800G | A high-density spine or super-spine needs modular 400G or 800G scale | It is an NX-OS platform and is not a direct substitute for an ACI-focused Nexus 9500 design |
The matrix also prevents a common naming error. Nexus 9200, 9300, 9400, and 9500 are data-center platforms, not the similarly numbered Catalyst 9000 campus families. A campus access or collapsed-core project should normally begin with the Catalyst portfolio unless a documented data-center requirement justifies Nexus.
Choose Fixed, Centralized Modular, or Distributed Modular
Form factor changes the failure model, expansion path, rack plan, and BOM. It should be settled before individual ports are compared.
Fixed switches: Nexus 9100, 9200, and 9300
Use a fixed switch when the port layout is known and future growth can be handled by adding another leaf or spine. This is the normal leaf-spine scaling model: the fabric grows horizontally instead of reserving empty line-card slots in one chassis.
The Nexus 9300 is the default fixed family because it covers the widest range of enterprise roles. Nexus 9200 is now a split proposition rather than simply an older alternative: the Nexus 9232E is a current 32-port 800G switch, while the N9K-C92348GC-FX3 addresses 1G management connectivity. Nexus 9100 is more specialized still, pairing an 800G fixed platform with NVIDIA Spectrum-X silicon for AI networking.
Feature equivalence still requires verification. Two 32-port 400G switches can differ in buffer depth, encryption coverage, timing, operating mode, and supported optics. Those differences matter more than rack-unit count once the physical port requirement is met.
Centralized modular: Nexus 9400 and 9500
The Nexus 9400 provides eight expansion-module slots in 4RU. Cisco lists configurations up to 64 ports of 400G, 128 ports of 200G, or 176 ports of 10/25/50G, with one supervisor slot and replaceable switch card, expansion modules, fans, and power supplies. It fits designs that need a compact modular system but do not require the scale or control-plane redundancy of a larger chassis.
The Nexus 9500 uses 4-, 8-, or 16-slot chassis. Current Cloud Scale line cards extend the platform from 1G through 400G, and the chassis supports redundant supervisors, system controllers, fabric modules, power, and cooling. Choose it when the design must mix several port generations, add capacity by installing line cards, or preserve an established Nexus 9500 operational model.
Distributed modular: Nexus 9800
The Nexus 9800 is the modular choice for very high-capacity NX-OS fabrics. The N9804 and N9808 provide four and eight line-card slots, and Cisco’s current data sheet includes a 36-port 800G OSFP line card as well as 400G and mixed 100G/400G options. The platform is designed for spine and super-spine density with redundant supervisors, fabric modules, power, and cooling.
Use a Nexus 9800 when system-level scale requires it. A fixed 800G platform may be more direct when the port count and failure domain fit; the 9800 becomes compelling when multiple line cards, very high chassis density, or a distributed modular architecture is the requirement.
Nexus 9300 Models: Select by Port Type and Platform Branch
Nexus 9300 suffixes are useful identifiers, but they no longer form a simple EX-to-FX-to-GX generation ladder. Cisco’s current data-sheet index includes FX2, FX3, SE1, GX, GX2, H1, H2R, SG2, SG2X, and SP2R branches. Some indicate an access generation, while others distinguish silicon, buffer design, port speed, optics form factor, or a specialized role.
Use the suffix to locate the correct data sheet, then verify every required feature for that PID. The familiar port codes are also only a starting point: GC commonly indicates low-speed BASE-T, TC copper up to 10G, YC SFP-based access, C 100G-class QSFP, and D 400G-class QSFP-DD. Newer E, H, SE, SG, and SP names do not follow that compact decoder.
| Requirement | Models to compare first | Decision that separates them |
|---|---|---|
| 1G copper management or low-speed access | N9K-C9348GC-FX3, N9K-C9348GC-FXP, N9K-C92348GC-FX3 | Current lifecycle, ACI requirement, PoE, and low-speed port behavior |
| 10GBASE-T or multigigabit copper | N9K-C93108TC-FX3, N9K-C93108TC-FX3P, N9396T12C-SE1 | Port density, PoE, supported downlink speeds, and rack power |
| 25G or 50G SFP-based leaf | N9K-C93180YC-FX3, N9K-C93360YC-FX2, N9348Y12C-SE1, N9396Y12C-SE1 | 25G versus 50G need, downlink density, uplink count, timing, and software mode |
| Fixed 100G aggregation or spine | N9K-C9336C-FX2, N9K-C9364C-GX, N9364C-H1 | 36 versus 64 ports, breakout, buffer and table scale, MACsec scope, and lifecycle |
| Fixed 400G fabric | N9K-C9332D-GX2B, N9K-C9364D-GX2A, N9332D-H2R | 1RU versus 2RU density, standard versus deep buffer, encryption scope, and traffic pattern |
| Fixed 800G fabric | N9364E-SG2-Q / N9364E-SG2-O, N9364E-SG2X-Q / N9364E-SG2X-O, N9364E-SP2R-Q / N9364E-SP2R-O | Optics form factor, buffer architecture, ACI requirement, power, and scale-up versus scale-across role |
1G and 10G copper
For 1G management, the current N9K-C92348GC-FX3 and N9K-C9348GC-FX3 both provide 48 BASE-T downlinks plus SFP28 and QSFP28 uplinks. The earlier N9K-C9348GC-FXP remains relevant to installed estates. A new quote should compare it with the newer FX3 options before selecting the older PID.
For server or appliance racks that must keep RJ-45, the N9K-C93108TC-FX3 provides 48 100M/1G/10GBASE-T downlinks and six 40/100G QSFP28 uplinks. The N9K-C93108TC-FX3P extends the downlinks to 2.5G and 5G and adds PoE. Those multigigabit or power requirements are the reason to select the P model.
25G and 50G fiber leaf
The N9K-C93180YC-FX3 remains a practical 25G leaf candidate: 48 1/10/25G SFP28 downlinks and six 40/100G QSFP28 uplinks in 1RU. The N9K-C93360YC-FX2 increases density to 96 downlinks and 12 uplinks in 2RU. When the server-NIC roadmap includes 50G, add the current SE1 models to the 2026 shortlist.
A complete leaf order also confirms the exact optics, DAC or AOC length, Forward Error Correction requirements, minimum software, and breakout mode. For one common PID, the N9K-C93180YC-FX3 transceiver compatibility guide provides the dedicated optics decision path.
Fixed 100G and 400G
The N9K-C9336C-FX2 is a 36-port 40/100G option with breakout on every port. The N9K-C9364C-GX provides 64 40/100G ports and is the official replacement direction for the end-of-sale N9K-C9364C. The newer N9364C-H1 is another 64-port 100G branch, with different forwarding scale and MACsec coverage. Compare those capabilities even when the faceplates show the same port count.
At 400G, the N9K-C9332D-GX2B provides 32 QSFP-DD ports in 1RU, while the N9K-C9364D-GX2A provides 64 in 2RU. The N9332D-H2R adds deep-buffer capability to a 32-port 400G fixed platform. Select H2R when a documented burst, storage, DCI, or congestion-management requirement calls for that buffer design.
400G and 800G: Enterprise Fabric, AI Scale-Out, or Scale-Across
An 800G port count does not identify the right AI switch. The design also has to settle the silicon ecosystem, buffer model, optics form factor, fabric size, cable reach, congestion strategy, and management plane.
| Design requirement | Platform direction | Why it belongs on the shortlist |
|---|---|---|
| General fixed 400G leaf or spine | Nexus 9300 GX/GX2 | Mature fixed 400G QSFP-DD choices with multiple densities |
| Deep-buffer fixed 400G | N9332D-H2R | 32 x 400G with 8GB of high-bandwidth memory in addition to on-die buffer |
| High-density fixed 800G on Cisco Silicon One | N9364E-SG2X-Q or N9364E-SG2X-O | 64 x 800G in 2RU, QSFP-DD or OSFP, with support for lower speeds and breakout |
| Deep-buffer 800G spine or inter-data-center scale-across | N9364E-SP2R-Q or N9364E-SP2R-O | 64 x 800G with Cisco Silicon One P200 and 16GB HBM for burst-heavy, long-distance, or distributed designs |
| Compact 32-port 800G fixed fabric | Nexus 9232E | 32 x 800G in the Nexus 9200 family, based on Cisco Silicon One G100 |
| Modular 400G/800G spine or super-spine | Nexus 9800 | Four- or eight-slot chassis with current 400G and 800G line-card options |
| NVIDIA Spectrum-X AI architecture | Nexus 9100, including N9164E-NS4-O | 64 x 800G fixed platform based on NVIDIA Spectrum-4, aligned with Cisco’s Spectrum-X offering |
The N9364E-SG2X is the general high-density 800G fixed branch in this comparison. The N9364E-SP2R is materially different: Cisco positions it for deep-buffer 800G spine and scale-across designs, and its 3RU chassis, buffer, power, and cooling profile reflect that role. The N9164E-NS4-O introduces another decision boundary because its NVIDIA silicon and AI architecture are different from the Cisco Silicon One platforms.
Before selecting any of them, calculate usable ports after breakout, expected oversubscription, cable reach, transceiver power, rack power, and cooling. For RoCE fabrics, also validate NIC behavior, PFC and ECN design, telemetry, and the tested reference architecture. Those engineering choices should be complete before a procurement team treats two 800G PIDs as commercial substitutes.
Choose NX-OS, ACI, Hyperfabric, or SONiC Before the BOM
Current Nexus 9000 platforms span more than two software operating models. The supported choices vary by family, platform branch, and exact PID.
| Operating model | Use it when | Procurement consequence |
|---|---|---|
| NX-OS | The fabric is operated through standalone NX-OS, VXLAN EVPN, Nexus Dashboard services, or conventional Layer 2/3 designs | Confirm the DCN license tier, minimum NX-OS release, Nexus Dashboard services, and feature support for the exact PID |
| Cisco ACI | APIC-controlled policy, ACI fabric operations, and supported ACI roles are design requirements | Confirm ACI support and role for every leaf or spine PID, then include APIC and the correct ACI licensing and software releases |
| Nexus Hyperfabric | The project uses Cisco’s cloud-managed fabric operating model on a supported platform | Limit the shortlist to the specific supported models and validate the current subscription and management requirements |
| SONiC | The architecture calls for SONiC on a supported N9100 or selected N9300 offering | Confirm the exact hardware, image, feature set, optics, support model, and deployment reference rather than transferring NX-OS assumptions |
Cisco’s current Nexus 9000 comparison shows why the exact check matters: different Nexus 9300 categories list different combinations of ACI, NX-OS, Hyperfabric, and SONiC. The N9100 family page also advertises NX-OS or SONiC, while the N9164E-NS4-O data sheet lists NX-OS and Hyperfabric for that platform. Make the final software and management choice against the exact offering.
Licensing is likewise feature-driven. Cisco’s current N9300-FX3 and N9364E-SG2X data sheets state that Nexus Dashboard is included with tiered switch licenses, while services such as NDFC, NDO, and NDI require the corresponding DCN license tier or add-on. That is a useful planning rule, but the final quote still needs the license navigator or ordering guide for the selected hardware and software release.
Lifecycle: Which Models Should Be Bought for a New Build?
Lifecycle must be checked at the PID level. A current family can contain both available and end-of-sale products. Use a family-level EOL list for discovery, then establish orderability from the exact model status and applicable notice.
| Exact scope | Current lifecycle fact | Official new-build direction |
|---|---|---|
| N9K-C93180YC-EX and N9K-C93108TC-EX | End of sale August 9, 2022; last date of support August 31, 2027 | N9K-C93180YC-FX3 and N9K-C93108TC-FX3P |
| N9K-C93180YC-FX and N9K-C93108TC-FX | End of sale July 31, 2024; last date of support July 31, 2029 | N9K-C93180YC-FX3 and N9K-C93108TC-FX3P; FX3H for the 24-port variants |
| N9K-C9332C and N9K-C9364C fixed spine | End of sale January 30, 2024; last date of support January 31, 2029 | N9K-C93600CD-GX and N9K-C9364C-GX |
| N9K-C92348GC-X | Cisco’s support page marks the PID End of Sale, with support ending August 31, 2030 | Compare the available N9K-C92348GC-FX3, but validate the migration as a model decision rather than assuming an official one-for-one replacement |
End-of-sale hardware can still make sense as an exact spare, a like-for-like expansion, or a controlled bridge to a planned migration. A greenfield BOM should include it only when the business case deliberately accepts the support end date, software ceiling, optics reuse plan, and replacement path.
Final Nexus 9000 Ordering Checklist
Complete these checks in order before requesting a final quote:
- Architecture and role: leaf, ToR, border leaf, spine, super-spine, management, DCI, storage, or AI fabric.
- System type: fixed, Nexus 9400 centralized modular, Nexus 9500 modular, or Nexus 9800 distributed modular.
- Physical port map: media, native speeds, breakout, usable port count, uplink count, and oversubscription.
- Traffic requirements: buffer architecture, forwarding tables, latency, timing, MACsec or IPsec scope, and any storage or RoCE behavior that materially affects the choice.
- Software operating model: NX-OS, ACI, Hyperfabric, or SONiC, limited to the exact supported PID and role.
- Lifecycle: available, end of sale, last date of support, and official replacement where Cisco has published one.
- Optics and cabling: exact transceiver, DAC or AOC, reach, connector type, FEC, breakout cable, and minimum software.
- Power and cooling: airflow direction, PSU type, input voltage, rack depth, rail kit, acoustic limit, and facility power budget.
- Licenses and controllers: DCN tier, Nexus Dashboard services, APIC where required, support contract, and subscription term.
- Spares and migration: exact spare PIDs, software compatibility, configuration migration, and the date by which end-of-sale hardware must leave the design.
Once the requirements have narrowed the field to two or three models, use the Cisco product comparison tool to place their specifications side by side. For current product options, see the Layer23 Nexus 9000 category. For a project BOM, request a quote with the target role, software mode, port map, optics, airflow, and required delivery location so the hardware and dependent line items can be checked together.
