NVIDIA AI Infrastructure: Structured Cabling for GPU Data Centers

A practical guide for data-center builders and cabling contractors on how to align structured cabling, power, and cooling decisions with NVIDIA's GPU platform requirements—from H100 to Blackwell-generation systems.

By Todd Taskerud, AWS CCP, RCDD/NTS/OSP/WD, LEED GA
5 min read

NVIDIA GB200 NVL72 AI Infrastructure Rack System

Why GPU Data Centers Demand a Different Cabling Mindset

Traditional enterprise data centers were designed around moderate-density compute, predictable east-west traffic, and copper-dominant horizontal cabling. NVIDIA's current GPU platforms—from the H100 and H200 to the Blackwell-generation B200 and GB200 NVL72—have fundamentally changed the rules. Power densities that once defined an entire row now concentrate in a single rack. Interconnect bandwidth that once described a core switch now lives inside a single GPU baseboard. For network infrastructure designers and cabling contractors, that shift has direct, concrete implications on every layer of the physical plant.

Understanding the GPU Platform Stack Before You Pull a Single Cable

Before specifying cabling pathways, it helps to understand what the hardware actually does internally versus what it requires from the external infrastructure.

NVLink Is Not Your Network

NVLink is NVIDIA's proprietary GPU-to-GPU interconnect. NVLink 4.0 (used in H100) delivers 900 GB/s of bidirectional bandwidth, and NVLink 5.0 in the Blackwell architecture reaches 1.8 TB/s. Within a DGX or HGX node, NVLink runs over proprietary cabling harnesses integrated into the baseboard—these are not installer-serviceable structured cabling. In the GB200 NVL72 configuration, 72 Blackwell GPUs and 36 Grace CPUs are interconnected via NVLink Switch across a single liquid-cooled rack, forming a 72-GPU NVLink domain entirely within that rack. Contractors do not touch this layer. What contractors do own is everything that leaves the node: InfiniBand or Ethernet fabric cabling between nodes, racks, and spine switches.

The External Fabric: InfiniBand and Spectrum-X

Between nodes and racks, NVIDIA AI clusters typically run one of two fabrics. NVIDIA InfiniBand with ConnectX-7 adapters and Quantum-2 switches operates at 400 Gb/s NDR per port. NVIDIA Spectrum-X is a high-performance Ethernet solution running at 400GbE with RoCEv2, adaptive routing, and congestion control optimized for AI workloads. Both fabrics are where structured cabling infrastructure matters enormously. Fat-tree and rail-optimized topologies mean high port counts, high-density patch fields, and very specific reach requirements across the three layers of the interconnect fabric.

Fiber Infrastructure: The Core of an AI Cabling Plant

At 400 Gb/s and emerging 800 Gb/s link speeds, copper's role shrinks and fiber's role expands dramatically. ANSI/TIA-568.3-D governs optical fiber cabling and is the applicable standard for fiber infrastructure in these environments. Your fiber decisions must account for transceiver type, channel reach, and connector density.

Transceiver Technology and Reach Segmentation

At 400G and 800G, QSFP-DD and OSFP transceivers dominate. The selection of Direct Attach Copper (DAC), Active Optical Cable (AOC), or discrete transceivers with structured fiber follows a straightforward reach logic:

  • DAC (Direct Attach Copper): Appropriate for connections of 3 meters or less—typically top-of-rack switch to adjacent servers. No fiber plant required, but bend-radius management in high-density environments is non-trivial.
  • AOC (Active Optical Cable): Practical for 3 to 30 meters—within a row or between adjacent rows. AOCs are factory-terminated and not field-spliced; plan for fixed lengths and adequate slack management.
  • Structured Fiber (single-mode or multimode): Required for longer intra-data-center runs to spine switches and interconnect rooms. Single-mode offers the longest reach and headroom for future speed upgrades; multimode OM4 or OM5 remains viable for shorter structured runs within the AI pod.

High-Density Connectivity and MPO/MTP Infrastructure

GPU clusters generate extreme port counts. A modest cluster of 32 DGX H100 nodes can require hundreds of 400G InfiniBand uplinks. Specifying 144-fiber MPO/MTP trunk assemblies is not optional—it is the only practical way to manage that density in overhead trays and vertical cable managers. Pay close attention to bend-radius requirements for high-fiber-count trunk cables, especially where pathways make 90-degree turns around busway or liquid cooling runs. Labeling and documentation per ANSI/TIA-606-C is essential: in a fat-tree or rail-optimized topology, a single mispatched link can asymmetrically degrade an entire training job's throughput.

Power Infrastructure: The Real Design Driver

Power density is arguably the most disruptive aspect of GPU cluster design for the physical plant. The DGX H100 system draws approximately 10.2 kW per node at eight GPUs per node. Blackwell-generation systems scale substantially higher—the GB200 NVL72 rack is rated at approximately 120 kW per rack. These are not edge cases; they are the baseline design targets.

Raised-floor power distribution, traditional PDUs, and branch circuit wiring sized for conventional servers cannot serve these loads. Facility design should target 480 V three-phase power distribution with overhead busway systems to deliver flexible, high-amperage capacity directly to rack positions without the floor-penetration constraints of legacy infrastructure. N+1 UPS architecture is the minimum acceptable availability model for AI training infrastructure, where a job interruption may represent days of lost compute time. ANSI/TIA-942 provides the data center infrastructure framework within which power, cooling, and cabling systems must be coordinated.

Cooling and Cabling: Learning to Share the Pathway

At H100 densities, rear-door heat exchangers can augment air cooling effectively. At Blackwell densities—particularly with the GB200 NVL72—direct-to-chip liquid cooling is required. This is where cabling contractors encounter an entirely new constraint: liquid cooling supply and return hoses now run in the same overhead pathways, cable trays, and vertical managers as fiber trunks and copper power cabling.

Practical implications for the cabling contractor include:

  • Segregate fiber pathways from liquid cooling lines wherever possible; liquid leaks and fiber don't mix.
  • Design cable tray fill rates with cooling hose diameter and weight in mind—a 4-inch supply/return pair consumes significant tray volume.
  • Provide dedicated vertical cable managers for fiber and copper patch cords that do not share space with coolant distribution manifolds.
  • Coordinate with the mechanical contractor early—cooling rough-in sequence directly affects where and when overhead cabling infrastructure can be installed.

Administration and Labeling: Non-Negotiable at Scale

An AI cluster is a precision instrument. The fat-tree and rail-optimized topologies used in GPU fabrics are sensitive to cabling errors in ways that a traditional three-tier LAN is not. A single transposed cable in a two-tier InfiniBand fabric can create bandwidth bottlenecks that are extremely difficult to isolate without meticulous documentation. ANSI/TIA-606-C administration practices—unique identifiers for every link, port, and pathway—are the baseline. In practice, most serious AI infrastructure deployments add asset management software and structured naming conventions that tie physical port IDs to logical fabric topology diagrams. Build that documentation discipline into your installation scope from day one.

Key Takeaways for Infrastructure Teams

  • NVLink cabling is proprietary and factory-integrated; your scope begins at the external InfiniBand or Ethernet ports.
  • Design fiber infrastructure to ANSI/TIA-568.3-D with high-density MPO/MTP trunking and single-mode headroom for 800G evolution.
  • Power design must account for up to 120 kW per rack at Blackwell densities; overhead busway at 480 V three-phase is the practical solution.
  • Liquid cooling and structured cabling must be coordinated in pathway design—these systems now coexist in the same physical space.
  • Labeling and administration per ANSI/TIA-606-C is operationally critical, not a nice-to-have, in GPU fabric environments.
  • Engage mechanical, electrical, and low-voltage contractors in a single coordinated design process—siloed design produces unresolvable conflicts at installation time.

GPU data centers are among the most demanding infrastructure environments the structured cabling industry has ever encountered. The physics of the hardware—extreme power, extreme bandwidth, extreme density—flow directly into decisions that cabling designers and contractors make every day. Getting those decisions right requires connecting NVIDIA's platform specifications to real installation practice, and doing that work before the first conduit stub is set.

Todd Taskerud, RCDD, is a network infrastructure specialist at Heather Technologies.