LEVIATHAN SYSTEMS

Cabling

MPO Fiber Counts: Calculate Channels, Assemblies and Spare Capacity

Technical contentPublished Updated

Count the physical channels the approved design needs, identify the fibers each optical interface uses, then map those paths through the actual trunks, cassettes and patch cords. GPU count, port bit rate and ferrule position count are different inputs. None supplies a universal trunks-per-GPU or spare-fiber rule.

Start with the optical interface, not the GPU inventory

A GPU inventory describes compute equipment. The network design identifies server adapters, switch ports, configured modes and optical interfaces. Resolve those connections before multiplying cable quantities. A system may expose several network roles and shared or breakout components; an assumed one-trunk-per-GPU ratio can miscount the package.

Cisco lists QDD-400G-SR8-S with eight multimode fiber pairs and MPO-16 APC. Its QDD-400G-SR4.2-BD uses four pairs and MPO-12 UPC. These are two specific 400G products with different physical requirements, not interchangeable definitions of 400G. Obtain the applicable supported endpoint combination.

References: [C1]

Keep four quantities in separate columns

For each material line, distinguish the connector’s available positions, installed strands, assigned end-to-end paths and supplied assembly count. NVIDIA’s connector examples include 12-position arrangements in which the center positions are unused. Unused positions do not by themselves prove that extra fibers run through the cable.

Ask for the exact assembly specification and mapping. An eight-fiber assembly can use a 12-position interface; a different assembly may contain 12 strands. Calling both MPO-12 without the remaining fields loses information needed for the order and handoff.

References: [N1]

Work through an eight-channel example

Assume a hypothetical approved design requires eight duplex optical channels between two panels. Each channel uses two end-to-end fiber paths. The design specifies one 24-fiber trunk, its compatible terminations/mapping and eight duplex patch cords at each side. This is arithmetic for those stated inputs, not a recommended GPU network or complete optical design.

Scroll the table horizontally on smaller screens.

Illustrative quantities for eight duplex channels
ItemQuantity from the stated designInterpretationSource
End-to-end channels8Eight channel requirementsPlanning analysis
Assigned fiber paths8 × 2 = 16Sixteen paths assigned through the trunk mappingPlanning analysis
Installed trunk strands24 in one trunkEight remain unassigned in this examplePlanning analysis
Duplex patch assemblies8 at each end = 16Two supplied patch assemblies per channelPlanning analysis
Patch-cord fiber segments16 × 2 = 32Patch segments; not 32 additional end-to-end pathsPlanning analysis

Original hypothetical calculation. No transceiver, cassette, polarity or loss-budget design is supplied.

Reconcile shared assemblies before issuing the material schedule

A port-to-port schedule can contain many rows that share one trunk. Count that trunk once in the material schedule and retain the relationship to every affected channel. Conversely, one connection row may need several assemblies along a structured path; counting only rows would understate supplied parts.

If the endpoint mode, route or panel arrangement changes, revisit dependent quantities and orderable lengths. Record the measured route reference and approved allowances. The optical designer must establish the complete channel, component mapping and acceptance criteria before the figures become a released installation package.

References: [L2]

Use the schedule to define the installation inquiry

Provide endpoint pairs, exact component identifiers, approved mappings, route references, customer-furnished quantities and the expected handoff evidence. Identify shortages explicitly so an installer is not asked to choose an unapproved substitute on site. Keep the order quantity separate from what has arrived and been released.

Leviathan can discuss agreed routing, mounting, cable installation, identification and documentation. BOM preparation does not include purchasing materials. Formal optical tests require confirmed personnel, equipment, methods and criteria; this guide supplies no test limit or certification procedure.

References: [L1][L2]

Common planning questions

Can I calculate MPO trunks from the number of GPUs?

Only if the approved system and network design establish that relationship. Resolve the actual interfaces and shared channel components first.

Are unused MPO positions automatically spare fibers?

No. Confirm installed strands, termination and mapping. Unused positions, unassigned strands and stocked replacement assemblies are separate facts.

Primary sources

  1. [C1] Cisco 400G QSFP-DD cable and transceiver data sheetChecked 2026-10-15. Exact QDD-400G-SR8-S, QDD-400G-SR4.2-BD and QDD-400G-BD examples. No generic 400G mapping, host compatibility, test limit or availability inferred. Internal standard-reference inconsistencies are not reproduced.
  2. [N1] NVIDIA cable and connector definitionsChecked 2026-10-15. Connector section and specific interface examples only. Older application-note text is generation-specific; no general speed, reach, NVLink or compatibility claim adopted.
  3. [L2] Leviathan physical planning and CAD scopeChecked 2026-10-15. Physical layouts, coordination, schedules and BOM documentation. Confirm resources, reviewer and formats; no licensed or stamped design.
  4. [L1] Leviathan structured cabling scopeChecked 2026-10-15. Agreed physical installation of customer-furnished materials and defined verification. Purchasing and delivery require an approved scope; no unconfirmed testing or architecture certification.

Reconcile the actual cabling quantities

Share the endpoint/channel schedule, approved assemblies, material responsibilities and unresolved quantity questions.

Discuss a ProjectEmail Project Scope