NVIDIA Networking PRODUCT LIST

How to plan an NVIDIA Networking product set

NVIDIA Networking projects combine a fabric, server adapters and the physical links between them. Start by deciding whether the application requires InfiniBand or Ethernet, then compare the exact switch and adapter models for that fabric. Quantum and Quantum-2 belong to the InfiniBand switch portfolio. Spectrum belongs to the Ethernet switch portfolio, while Spectrum-X describes an Ethernet platform for AI networking. ConnectX adapters provide the host connection, and LinkX cables or transceivers complete the link. A family name helps organize the shortlist; it does not establish compatibility or guarantee a particular performance result.

Build the bill of materials around the complete connection path. Record each server model, PCIe slot, adapter OPN, switch port, cable or optic and intended link rate. Check connector and lane requirements, port mode, supported breakout combinations and cable distance. Also record rack power, airflow direction and available cooling. A faster port cannot deliver its advertised rate when the host slot, peer device or link media imposes a lower limit. For mixed generations, verify the supported negotiated rate rather than assuming backward compatibility from connector shape alone.

Software is part of the selection boundary. For InfiniBand, review the driver or OFED branch, adapter firmware and subnet management plan. For Ethernet and RoCE, review the switch software, host driver, MTU and congestion policy required by the intended workload. Record the supported versions from the manufacturer documentation and distinguish published capability from a configuration that has actually been tested. Lifecycle, replacement stock and upgrade requirements also matter when expanding an existing production network.

Use the InfiniBand switch collection, InfiniBand adapters and cable collection together for an InfiniBand design. For an Ethernet design, compare Ethernet switches with Ethernet adapters. Keep exact part numbers in the shortlist so substitutes can be assessed against the same requirements.

Before volume procurement, define a representative proof of concept with the planned host image, peer switch and application traffic. Measure link negotiation, throughput, latency, errors and stability against agreed acceptance criteria. An inquiry should include topology, quantities, delivery region, target date and spare policy. These details allow a compatibility review and quotation to address the actual rollout, with availability and delivery confirmed for the requested models at the time of inquiry.