Can You Build a 4-Node DGX Spark Cluster Without a Switch? Why the QSFP Breakout Trick Doesn't Work

If you own four DGX Spark or GB10 systems and you are trying to avoid buying a switch, you have probably found the same idea circulating on the NVIDIA developer forums: break each 200G QSFP port into 2×100G, give every node four links, and wire a full mesh. It is a clever idea, and on paper the DGX Spark's networking architecture looks like it was built for it. It does not work. NVIDIA does not enable or validate port splitting on the Spark's ConnectX-7, and operators who have tried report only the first lane coming up. The limit is the NIC, not the budget, and no cable choice gets around it. Three units is the ceiling for direct cabling; the fourth node needs a switch.

The Idea, and Why It Looks Like It Should Work

The proposal shows up on the NVIDIA developer forums roughly like this: a switch adds latency that hurts tensor-parallel workloads, so build a switchless full mesh instead. Each DGX Spark has two QSFP ports. Four nodes in a full mesh need three links per node. Two ports cannot do three links — unless you split them. Break each 200G port into 2×100G and suddenly every node has four links, which is more than enough for a four-way mesh.

What makes this more than wishful thinking is that the DGX Spark's networking really is built out of 100G halves. The GB10 Grace Blackwell SoC cannot provide more than a PCIe Gen5 x4 link per device. To reach 200Gbps, NVIDIA ran the ConnectX-7 in multi-host mode across two separate x4 links. The practical result is that each physical QSFP port carries two 100G MACs, each tied to its own PCIe x4 connection, and Linux presents four Ethernet interfaces rather than two. Users have to bind the right interface pairs or they get roughly 100Gbps instead of the full 190–200Gbps.

So the hardware already contains the 2×100G split the mesh idea depends on. It is reasonable to assume a breakout cable could simply expose it.

Why It Doesn't Work

The split exists on the PCIe side, not at the port. Operators who have actually attempted breakout on DGX Spark hardware report that the port will not come up as independent links — in the words of one, they "were not able to split a QSFP port into four links" and "have only been able to establish a link on the first QSFP lane." A second report on 2×100G describes the same outcome: the cable is recognized, but only one leg becomes active.

NVIDIA's own position on the forums is that this would mean "using an untested splitter cable that could cause other issues," with no validation of the thermal or power profile a splitter presents to the port. It is worth being precise about the mechanism here, because adapter-side splitting is not universally impossible: NVIDIA documents port-splitting configurations for specific ConnectX-7 SuperNIC models, applied through mlxconfig and requiring a power cycle. Those configurations are documented for pluggable adapter cards — not for the soldered ConnectX-7 the DGX Spark ships with, where NVIDIA exposes no split mode and validates none.

This matters because it reframes the whole debate. The objections raised against the mesh proposal on the forums were about cost and bandwidth oversubscription — both arguable, and both beside the point. Even with cheap passive copper breakouts instead of optics, and even if you accept the oversubscription, the topology still cannot be built. And the arithmetic is against it before the NIC is: a four-node full mesh needs three links on every node, and a Spark has two ports. Four cables between four Sparks gets you a ring, not a mesh — every node one hop from two neighbors and two hops from the third. That is the shape a switch exists to fix.

What NVIDIA Actually Documents

The DGX Spark user guide is unambiguous: the platform "supports up to three DGX Spark systems connected directly through cables, and up to four systems when using a switch." Two QSFP ports per unit, up to 200Gbps each. The two cable part numbers NVIDIA names as approved are the Amphenol NJAAKK-N911 and the Luxshare LMTQF022-SD-R — both QSFP112, both 0.5 m, and both equivalent to the cable Resilient Tec stocks.

The Four-Node Route That Does Work

Once you accept the switch, the build is straightforward and cheaper than most people expect. There are two ways to cable it, and which one is right depends on how many 400G ports your switch has — not on price.

A port per node: use straight cables. The MikroTik CRS804-4DDQ is the common choice in this class — four 400G QSFP56-DD ports at a $1,295 list price. Four nodes, four ports, so run one 200G DAC from each Spark to its own switch port and skip breakout entirely. QSFP-DD cages are backward compatible with QSFP56 modules, so a standard 200G QSFP56 passive DAC plugs straight in; set the port speed to 200G manually rather than trusting auto-negotiation. Four 2 m cables at $91 each come to $364.

Fewer ports than nodes: break out. The MCP7H60-W002, a 400G QSFP-DD to 2×200G QSFP56 passive breakout DAC at $179.45, turns one switch port into two Spark links. Two of them cover four nodes off two ports — which is the only way to do it on something like the MikroTik CRS812-8DS-2DQ-2DDQ, where only two ports are QSFP-DD. On a four-port switch it still has a use: two breakout cables leave two ports free for growth toward eight nodes.

On cost the two routes are effectively tied — $358.90 for two breakout cables against $364 for four straight ones — so let port count decide. What does not change either way is the direction: the breakout happens on the switch side, where breakout is a supported, documented function. Each Spark still receives one whole 200G QSFP link into an unsplit port. That is the distinction the switchless mesh proposal gets backwards.

The switch-side breakout is not theoretical. A four-node GB10 build documented on the NVIDIA developer forums ran exactly this configuration — a CRS812 fed by QSFP-DD to 2×200G QSFP56 breakout DACs — and measured roughly 196–198 Gb/s per node pair on iperf3 and about 23.8 GB/s bus bandwidth on an NCCL all-reduce, once MTU 9000 was set and both logical halves of each port were driven in parallel.

Budget roughly $1,650 all in for switch and cabling on either route — against a switchless mesh that cannot be built at any price.

One warning worth having before you buy: getting the links up is not the same as getting the throughput. Four-node GB10 clusters on Marvell-based switches have been reported hitting a hard ~10Gbps ceiling on clean 200G links, traced to bridge hardware offload failing, PFC and trust settings blocking RoCE, and duplicate fabric IPs across rails. Plan on MTU 9000, one subnet per rail, and unique IPs per interface, and budget an afternoon for tuning rather than assuming it works out of the box.

What About the 200G to 2×100G Breakout Cable?

Part numbers like the MCP7H50-H001R30 (200G QSFP56 to 2×100G QSFP56) are real, in stock, and genuinely useful — on switch ports and on adapter cards where splitting is documented and configurable. They are not a workaround for the DGX Spark. Buying one to attempt a switchless four-node mesh will get you one active leg and a dead one. If you are cabling a Spark, you want a whole-port cable at the Spark end, every time.

Quick Checklist

• Two or three GB10 systems: direct cabling, no switch, one QSFP112 stacking cable per link
• Three units form a ring using both QSFP ports on each node
• Four units: a 400G switch — one 200G DAC per Spark if the switch has a 400G port per node, or one QSFP-DD to 2×200G breakout cable per pair of Sparks if it does not
• Never split a Spark's QSFP port — breakout belongs on the switch side only
• Set switch port speed to 200G manually; do not rely on auto-negotiation
• MTU 9000, one subnet per rail, unique IP per fabric interface, and verify hardware offload is active before benchmarking

FAQ

Can you build a 4-node DGX Spark cluster without a switch?
No. A four-node full mesh needs three links per node, and each DGX Spark has only two QSFP ports. Splitting a port with a breakout cable does not work — operators report that only the first lane establishes a link, and NVIDIA does not validate splitter cables on these ports. NVIDIA documents direct cabling for up to three systems and a switch for four.

How many DGX Sparks can I connect directly with DAC cables?
Three. Two units take one cable point to point; three units form a ring using three cables, with each unit using both of its QSFP ports. The NJAAKK-N911 QSFP112 400G-rated stacking cable is $187 at Resilient Tec, so a three-node ring is $561 in cabling (prices checked September 13, 2026).

Do I need a breakout cable for a four-node DGX Spark cluster?
Only if your switch has fewer 400G ports than you have nodes. On a four-port switch like the MikroTik CRS804-4DDQ you can run one 200G DAC per Spark and skip breakout entirely. On a switch with two QSFP-DD ports, two breakout cables are the only way to land four Sparks. The cost is close to identical — $358.90 for two breakout cables against $364 for four straight 2 m DACs — so port count should decide it, not price.

Why does the DGX Spark show four network interfaces for two ports?
The GB10 SoC cannot provide more than a PCIe Gen5 x4 link per device, so NVIDIA runs the ConnectX-7 in multi-host mode across two x4 links per port. Each physical QSFP port carries two 100G MACs, which Linux presents as separate interfaces. They aggregate to 200Gbps, but only if you bind the correct pairs — mismatched pairing caps you near 100Gbps.

Which cable connects a DGX Spark to a 400G switch?
Either a straight 200G QSFP56 passive DAC — one per Spark, since QSFP-DD switch cages accept QSFP56 modules — or a 400G QSFP-DD to 2×200G QSFP56 passive breakout DAC, where one switch port serves two Sparks. Resilient Tec sells the MCP7H60-W002 breakout for $179.45 and the 2 m MCP1650-H002E26 200G DAC for $91, both new with a lifetime warranty and free US shipping.

Does a switch add enough latency to hurt tensor-parallel workloads?
A single switch hop adds well under a microsecond on a 400G cut-through switch, which is small next to collective operation times on GB10-class nodes. It is a real cost but rarely the limiting factor — misconfigured RoCE, PFC and MTU settings cost far more throughput in practice than the hop does.

Ready to Buy?

Tested and shipping from Knoxville, Tennessee. New, lifetime warranty, free standard shipping on all US orders, same-day shipping on orders placed before 5:00 pm ET. Prices below checked September 13, 2026.

• NJAAKK-N911 — QSFP112 400G-rated stacking cable, 0.5 m — $187, the two- and three-node link
• LMTQF022-SD-R equivalent — QSFP112 400G-rated stacking cable, 0.5 m — $187, same cable if Luxshare's part number is what you were sent
• MCP1650-H002E26 — 200G QSFP56 passive DAC, 2 m — $91, one per Spark when the switch has a port per node
• MCP7H60-W002 — 400G QSFP-DD to 2×200G QSFP56 breakout, 2 m — $179.45, the switch-side cable when ports are scarce
• MCP1650-V00AE30 — 200G QSFP56 DAC, 0.5 m — $84, the lower-cost two-node link

Going to four nodes, or mixing GB10 vendors? Send us your node count and switch model and we will confirm exactly what to buy before you order.

You Might Also Need

• Why Connect Two (or More) NVIDIA DGX Sparks? — hardware limits, topologies and what scaling actually buys you
• Does the DGX Spark cable work with every GB10 system? — ASUS, Dell, HP, MSI, Lenovo, Gigabyte and Acer
• DGX Spark ports explained — why USB-C isn't your clustering cable
• DGX Spark interconnect reference — approved part numbers, real-world throughput, and what to buy at two, three and four nodes
• Lossless Ethernet for RoCE — what to get right once the switch is in the path

Sources

• NVIDIA DGX Spark User Guide — ConnectX-7 Networking and clustering
• NVIDIA Developer Forums — 4-node DGX Spark cluster without a switch
• NVIDIA Developer Forums — Mellanox QSFP breakout
• NVIDIA Developer Forums — ConnectX-7 200GbE via MikroTik CRS812 and QSFP-DD to 2×200G breakout
• NVIDIA ConnectX-7 Adapter Cards User Manual — Port Splitting Configurations
• NVIDIA MCP7H60-W0xxRyy 400GbE to 2×200GbE DAC splitter cable — specifications
• MikroTik CRS804-4DDQ product page