DGX Spark Stacking / GB10 Cluster Cable

DGX Spark Stacking and GB10 Cluster Cable: 0.5m QSFP112 400G DAC

To cluster two NVIDIA DGX Spark units, or any GB10 Grace Blackwell workstation, you need one 0.5m QSFP112 400G passive DAC cable plugged into the QSFP112 port on each machine. It is the single cable NVIDIA calls out in its Spark Stacking documentation (Amphenol NJAAKK0006 / Luxshare LMTQF022-SD-R spec), sold at retail as the NVIDIA DGX Spark Stacking DAC Cable, QSFP/CX7, and because every GB10 system shares the same ConnectX-7 NIC, this one cable fits the DGX Spark Founders Edition and every OEM build alike. Petronella Technology Group, Inc. sells it at $159 with free US shipping, in stock, shipping in 1 to 3 business days. As of August 2026, retail listings for the same NVIDIA-approved spec run $176 to $285, NVIDIA's own marketplace lists it at $99.99 but is chronically out of stock, and Amphenol's factory-direct store shows its whole QSFP112 line on backorder.

In stock and shipping now.
Cables are on the shelf and ship in 1 to 3 business days, with more stock already inbound. If a surge empties the shelf, orders stay open and fill in the order they are paid and received, with a typical restock lead of 7 to 10 business days. This part keeps getting harder to source, which is why we placed the two largest orders we have ever placed for it. You get a tracking number by email the moment your cable ships, and you can cancel for a full refund any time before it ships. See our backorder and shipping terms.
In stock - ships in 1 to 3 business days | NVIDIA-approved spec | Free US shipping | Stock and pricing can change at any time; call 919-348-4912 to confirm current stock and pricing before you order
Stack of genuine Amphenol QSFP112 400G DAC cluster cables with blue pull tabs in Petronella Technology Group stock
Our actual shelf stock: genuine Amphenol cables, jacket-stamped AHSP P/N NJAAKR-0006, Rev G. Photographed in-house, ready to ship.
Sealed Amphenol bag labeled AHSP P/N NJAAKR-0006 containing a QSFP112 400G DAC cluster cable
Factory-sealed Amphenol packaging, part label visible.
Amphenol name embossed on the blue pull tab of a QSFP112 400G DAC cluster cable connector
Amphenol embossed on every pull tab.

The one cable every GB10 workstation needs

NVIDIA's GB10 Grace Blackwell superchip put a petaFLOP-class AI machine on the desk, and the way you scale past a single 128 GB node is to cable two or three of them together over their built-in QSFP112 ports. That interconnect is one specific, hard-to-source part, and it is the component distributors rarely keep on the shelf. Whether your box says NVIDIA, Dell, ASUS, MSI, Lenovo, HP, Acer, or Gigabyte on the front, the cable is identical.

Cable0.5m QSFP112 400G passive direct-attach copper (DAC)
Also sold asNVIDIA DGX Spark Stacking DAC Cable, QSFP/CX7 (retail part NJAAKK-N911)
Approved specAmphenol NJAAKK0006 / Luxshare LMTQF022-SD-R (NVIDIA Spark Stacking docs)
FitsBoth QSFP112 ports on the ConnectX-7 (CX7) NIC in every GB10 system
Link rate200 Gb/s class per link (cable is 400G-rated for headroom)
For two unitsOne cable
For a three-node ringThree cables (switchless, each box uses both ports)
Price$159, free US shipping (in stock, ships in 1 to 3 business days)

Clustering DGX Spark and GB10 units: cables, ports, and when you need a switch

Every GB10 system has exactly two QSFP112 ports, so the topology is the same no matter which vendor built it. Two units link directly with one cable. Three units form a switchless ring using three cables, following NVIDIA's "Connect Three DGX Spark in a Ring Topology" playbook, where each box uses both of its ports for full pairwise connectivity. Three nodes is the switchless ceiling: with only two ports per unit, a fourth node cannot be cabled directly to all the others, so four or more units need a 200G-class QSFP switch.

It helps to be clear about what clustering buys you. Linking nodes pools their memory so you can load a model too large for a single 128 GB machine, and it lets a workload span multiple GPUs. It is a capacity play, not a raw speed boost, because each link runs at roughly 25 GB/s. For memory-bound inference and fine-tuning of larger models that is exactly the win you want; for a job that already fits in one node, a second box adds headroom rather than throughput. For the deeper numbers, see our breakdown of what 400G really means for DGX Spark cluster bandwidth.

QSFP56 vs QSFP112: which DAC works for Spark stacking?

This is the most common question on the NVIDIA developer forums, and the confusion is understandable: the ConnectX-7 NIC in every GB10 system negotiates its node-to-node link at 200 Gb/s, which is squarely inside QSFP56 territory, yet NVIDIA's Spark Stacking documentation specifies a QSFP112 400G DAC. Both statements are true at once. The QSFP112 part is the documented, approved cable, rated with headroom above what the link actually negotiates; cable vendors and community testers have also reported 200G QSFP56 DACs linking successfully on DGX Spark pairs, because the port speaks the slower rate natively.

Our advice is simple: for a machine at this price point, buy the cable NVIDIA documents. A QSFP112 400G DAC is guaranteed against the spec the Spark Stacking guide names, works identically on every OEM GB10 build, and removes the one variable you would otherwise be debugging if the cluster link ever misbehaves. Saving a few dollars on an off-spec QSFP56 cable is the wrong trade next to a pair of $4,000 workstations. The connector is the standard QSFP form factor either way, which is why retail listings describe the official part as "QSFP/CX7": a QSFP-family cable for the ConnectX-7 NIC.

DGX Spark stacking cable part numbers, decoded

Retailers list NVIDIA's official stacking cable under part number NJAAKK-N911. The underlying manufactured spec that NVIDIA's Spark Stacking documentation names is Amphenol NJAAKK0006, with Luxshare LMTQF022-SD-R as the equivalent build. Any 0.5m QSFP112 400G passive DAC built to that spec, including the one Petronella Technology Group, Inc. stocks, is the same electrical part: passive copper, no firmware, no vendor lock. That is also why one cable covers the DGX Spark Founders Edition and the Dell, ASUS, MSI, Lenovo, HP, Acer, and Gigabyte GB10 builds interchangeably.

Why the official cable is a passive DAC, and why that matters

A passive direct-attach copper cable has no retimers, no digital signal processing, and no firmware. It is well-shielded twinax copper, terminated in QSFP connectors, and nothing more. That construction gives you three things you want in a cluster interconnect. First, near-zero added latency: there is no electronics in the path to buffer or re-clock the signal. Second, essentially no power draw, well under a tenth of a watt, compared with the several watts an active optical cable burns per end. Third, nothing to fail or to update: a passive DAC either works on day one or it does not, and once it links it stays linked. At 0.5 meters, copper does all of this comfortably; active optics only earn their cost and complexity at lengths a desk-side stack never reaches. Because the cable is rated to 400G while the node-to-node link negotiates at 200 Gb/s, it is over-provisioned by design and will never be the bottleneck in your cluster. The ConnectX-7 NIC and the GB10's PCIe lanes set the ceiling; the cable just carries what they negotiate, with margin to spare.

From unboxing to a working two-node cluster

Here is the whole job, end to end. Physically, you seat one end of the DAC in a QSFP112 port on the first unit and the other end in a QSFP112 port on the second, pressing until the latch clicks; the connector is keyed and cannot be inserted upside down. Either of the two ports on each machine works for a two-node link. There is no switch, no transceiver, and no optics to install, because the DAC's connector ends are the transceivers.

On the software side, NVIDIA's Spark Stacking documentation walks through the short bring-up: confirm the ConnectX-7 interfaces are visible on each node, assign each high-speed interface a static IP address on the same private subnet, and verify the link with a ping across those addresses. From there, distributed inference and training frameworks can be pointed at the direct connection between the nodes and will schedule work across both machines' GPUs and pooled memory. Budget fifteen minutes for the whole exercise, most of it reading rather than doing. If the link does not come up, the checklist is short precisely because the cable is passive: reseat both ends, confirm the interface addresses, and confirm both nodes are on current firmware. There is no cable firmware to suspect and no transceiver compatibility matrix to debug.

Three nodes: the switchless ring, step by step

A three-node cluster uses three cables and zero switches. Label your machines A, B, and C. Run one cable from A to B, a second from B to C, and a third from C back to A. Every box now uses both of its QSFP112 ports, and every pair of nodes has a direct link, which is exactly the full-mesh connectivity NVIDIA's "Connect Three DGX Spark in a Ring Topology" guide describes. Order the three cables together and the ring goes up in one sitting; this is the most common multipack quote we prepare.

Four or more nodes: plan the switch before the cables

With only two ports per unit, direct cabling stops at three nodes, so a fourth machine forces a topology change: every node now connects to a 200G-class QSFP switch instead of to its neighbors. That changes the shopping list from one cable per link to one cable per node plus the switch itself, and it raises questions worth answering before hardware arrives: how many ports you need today versus after the next budget cycle, whether the switch's port speed and form factor match the DACs you already own, and where the switch physically lives relative to a stack of desk-side machines. Petronella Technology Group, Inc. specs these small-fleet builds routinely; call 919-348-4912 with your node count and we will map the ports, cables, and switch model with you before you commit to any of it.

Ordering, shipping, and purchase orders

Single cables order instantly through the $159 checkout button on this page and ship free to US addresses. Cables are in stock and ship in 1 to 3 business days, with additional stock already inbound. International orders are quoted separately. For a three-node ring, ask us about the three-pack rather than ordering three singles; for labs and teams standing up multiple clusters, we quote five, ten, and twenty-unit quantities with volume pricing. If your organization buys on purchase orders or net terms, use the quote form below with your quantity and timeline and an engineer will turn it around within four business hours. Every cable we ship is built to the Amphenol NJAAKK0006 / Luxshare LMTQF022-SD-R spec that NVIDIA's Spark Stacking documentation names, which is the same electrical part regardless of whose logo is on the workstation it plugs into.

One practical buying note: because the GB10 platform sold faster than the accessory channel expected, the stacking cable is the piece that most often holds up an otherwise complete cluster. If your second workstation is on order, put the cable on order the same day. It is the cheapest component in the build and the one most likely to be backordered everywhere else when the machines arrive.

Why 0.5 meters, and when you need a longer run

The half-meter length is not arbitrary. GB10 workstations are desk-side machines designed to sit stacked or side by side, and 0.5m reaches between two stacked units or two neighbors on a bench with a clean service loop and no excess copper to coil. Shorter is better with passive DACs: less length means less signal loss and an easier time holding the negotiated rate. If your layout separates the machines, across a rack, through a desk grommet, or between shelves, tell us the actual port-to-port distance and we will quote the correct longer build rather than guessing; do not buy a long cable "to be safe" when a short one reaches, because the extra copper buys you nothing but loss margin and cable clutter.

Mixed-vendor clusters work, and warranties stay simple

Because every GB10 build carries the identical ConnectX-7 NIC, a Dell unit clusters with an ASUS unit, an HP with a Lenovo, or a Founders Edition with anything else on the compatibility table above. The link does not know or care whose enclosure the NIC sits in. This matters in practice because teams rarely buy all their nodes at once: the workstation that is in stock in March is often a different brand than the one that was in stock in January. The cable is the constant across all of them, and since a passive DAC carries no firmware, adding one to the build changes nothing about any workstation's own support relationship with its vendor. Buy whichever GB10 machines you can get, cable them with the one approved part, and the cluster comes up the same way every time.

GB10 cluster cable compatibility by system

The same 0.5m QSFP112 400G DAC clusters any of these GB10 Grace Blackwell workstations, in matched pairs or mixed-vendor. Pick your machine for the exact fit notes and to order.

WorkstationInterconnectCluster cable page
NVIDIA DGX Spark (Founders Edition)2 x QSFP112, ConnectX-7You are here
Dell Pro Max with GB102 x QSFP112, ConnectX-7Dell Pro Max GB10 cable →
ASUS Ascent GX102 x QSFP112, ConnectX-7ASUS Ascent GX10 cable →
MSI EdgeXpert2 x QSFP112, ConnectX-7MSI EdgeXpert cable →
Lenovo ThinkStation PGX2 x 200Gb QSFP, ConnectX-7Lenovo ThinkStation PGX cable →
HP ZGX Nano G1n2 x QSFP112, ConnectX-7HP ZGX Nano cable →
Acer Veriton GN1002 x QSFP112, ConnectX-7Acer Veriton GN100 cable →
Gigabyte AI TOP ATOM2 x QSFP112, ConnectX-7Gigabyte AI TOP ATOM cable →

Why buy the cluster cable from Petronella

The DGX Spark and its OEM siblings shipped faster than the accessory channel could keep up, so the one cable that turns two boxes into a cluster is routinely backordered at the big distributors, and quoted at $179 to $285 when it is in stock at all. Petronella Technology Group, Inc. carries the NVIDIA-approved 0.5m QSFP112 400G DAC at $159 with free US shipping and can quote multipacks for three-node rings and small fleets. It is in stock now and ships in 1 to 3 business days. This part keeps getting harder to source, which is why we placed the two largest orders we have ever placed for it. If you are standing up more than a handful of nodes, or want the 200G-class QSFP switch guidance for four or more units, call 919-348-4912 and we will spec it with you.

Talk to an engineer

Need a bulk order or a custom cluster quote?

Buying a single cable? Use the $159 order button above. For a three-node ring, a fleet order, a purchase order, or 200G switch guidance for four or more units, tell us the details and a Petronella Technology Group engineer will quote it. Prefer to talk now? Call (919) 348-4912.

By submitting you agree to our privacy policy. A Petronella Technology Group engineer replies within 4 business hours. No sales pressure.

Or schedule a call at a time that works for you.

DGX Spark and GB10 cluster cable FAQ

What cable do I need to cluster two DGX Spark units?
One 0.5m QSFP112 400G passive DAC, one end in each unit's QSFP112 port. NVIDIA's Spark Stacking docs specify the Amphenol NJAAKK0006 / Luxshare LMTQF022-SD-R spec, and the same cable fits every GB10 system because they share the ConnectX-7 NIC. One cable links two units; a switchless three-node ring needs three.
Is the cable the same across every OEM GB10 workstation?
Yes. The NVIDIA DGX Spark Founders Edition and the Dell, ASUS, MSI, Lenovo, HP, Acer, and Gigabyte GB10 builds all use the same ConnectX-7 NIC and dual QSFP112 ports, so the 0.5m QSFP112 400G DAC is the correct part for all of them, including mixed-vendor clusters.
How many units can I cluster without a switch?
Up to three, switchless: two units link directly with one cable, and three units form a switchless ring with three cables, each box using both ports. Four or more units need a 200G-class QSFP switch, since each unit has only two ports.
How much does clustering actually speed things up?
Clustering pools memory so you can run a model too large for one 128 GB node. It is a capacity play rather than a raw speed boost, because each link runs around 25 GB/s. For memory-bound larger-model inference and fine-tuning that is the win; a job that already fits in one node gains headroom, not throughput.
Is it in stock and how fast does it ship?
Yes, it is in stock at $159 with free US shipping and ships in 1 to 3 business days, and we email tracking the moment your cable ships. If a surge empties the shelf, orders stay open and fill in the order they are paid and received, with restock typically 7 to 10 business days. As of August 2026, retail listings for the same NVIDIA-approved spec run $176 to $285, NVIDIA's own marketplace lists it at $99.99 but is chronically out of stock, and Amphenol's factory-direct store shows its whole QSFP112 line on backorder. See full details and multipack bundles.
How do I network two NVIDIA DGX Spark desktop AI supercomputers, and what cable is recommended?
Connect one 0.5m QSFP112 400G passive DAC cable between the two units, one end in each machine's QSFP112 port on the ConnectX-7 NIC; no switch is needed for a two-node cluster. After cabling, assign IP addresses to the high-speed interfaces on each unit and follow NVIDIA's Spark stacking documentation to bring up the cluster link, at which point distributed frameworks can use the direct connection between nodes. The recommended cable is the NVIDIA-approved 0.5m QSFP112 400G DAC (Amphenol NJAAKK0006 / Luxshare LMTQF022-SD-R spec), and the same part fits every GB10 workstation regardless of OEM.
Will a 200G QSFP56 DAC work instead of QSFP112?
The node-to-node link negotiates at 200 Gb/s, and community testing has shown 200G QSFP56 DACs linking successfully on DGX Spark pairs. NVIDIA's Spark Stacking documentation still specifies the QSFP112 400G DAC, so that is the part guaranteed against the documented spec. Next to a pair of $4,000 workstations, the approved cable is the safe choice.
What is the NVIDIA part number for the stacking cable?
Retail listings carry NVIDIA's DGX Spark Stacking DAC Cable (QSFP/CX7) as part NJAAKK-N911. The manufactured spec behind it is Amphenol NJAAKK0006 / Luxshare LMTQF022-SD-R, which is the spec our cable is built to.
Do I need one cable or two for a two-node cluster?
One cable brings the cluster up: a single link between any QSFP112 port on each machine is a working two-node cluster. Each unit has two ports, though, so adding a second cable between the remaining ports doubles the pipe between the pair. Most buyers start with one and add the second when their workload proves link-bound.