Quick answer: Use this 400G MPO cable interface guide by starting with the exact transceiver and platform documentation. The speed label alone cannot tell you whether the link needs MPO-16, MPO-12, or duplex LC, or whether the module expects APC, UPC, or a supported breakout.
A 400G MPO cable is not a universal assembly. The same 400G rate can correspond to different fiber media, connector formats, polish, lane arrangements, and breakout support. In Cisco's current examples, QDD-400G-SR8-S uses MPO-16 APC, QDD-400G-SR4.2-BD uses MPO-12 UPC, QDD-400G-DR4-S uses MPO-12 APC, and QDD-400G-FR4-S uses duplex LC/UPC. These are part-number-specific examples, not rules for every vendor. (Cisco 400G QSFP-DD specifications)
Before releasing a cable request:
- Record both endpoint transceiver part numbers and host platforms.
- Confirm the optical standard, module interface, fiber medium, polish, and supported port mode in current vendor documents.
- Record the lane architecture, breakout conditions, and channel-loss ceiling.
- Approve the five-field interface record before route, polarity, BOM, and acceptance work begins.
Scope: This guide is for data-center and network-platform teams validating named 400G optics. It does not specify FTTH drop, aerial, duct, direct-burial, or other outside-plant cable construction.
Missing an endpoint field? Send BWNFiber the optic pair and current module documents before a cable family or breakout harness is selected. Identify the missing or contradictory interface field; this request does not replace equipment-vendor approval.
400G optic-to-cable matrix
The matrix uses five Cisco part numbers so the physical interfaces can be compared within one source family. Read each row as a module-specific example, not a cross-vendor compatibility claim.
| 400G implementation example | Optical path | Module-side interface | Reach in the named example | Breakout boundary | Buyer control |
|---|---|---|---|---|---|
| QDD-400G-SR8-S | Eight multimode pairs | MPO-16 APC | Up to 100 m on OM4 (Cisco datasheet) | Cisco lists 2x200G-SR4 or 8x50G-SR for this module | Verify host platform, remote optics, cable map, and current compatibility matrix. |
| QDD-400G-SR4.2-BD | Four bidirectional multimode pairs | MPO-12 UPC | Up to 70 m on OM3, 100 m on OM4, or 150 m on OM5 (Cisco datasheet) | Cisco lists 4x100G-SR1.2 | Do not substitute an SR8 harness; the interface and lane architecture differ. |
| QDD-400G-DR4-S | Four single-mode pairs | MPO-12 APC | Up to 500 m (Cisco datasheet) | Cisco lists conditional 4x100G and 2x200G use cases | Match the platform, port mode, remote optic, reach, wavelength, and FEC requirements. |
| QDD-4X100G-FR-S | Four independent FR1 lanes on single-mode fiber | MPO-12 APC | Up to 2 km to named FR1 endpoints (Cisco datasheet) | Designed around four independent 100G lanes | Do not call this 400GBASE-FR4; its external lane architecture is different. |
| QDD-400G-FR4-S | Four wavelengths multiplexed onto duplex single-mode fiber | Duplex LC/UPC | Up to 2 km (Cisco datasheet) | No passive four-port Ethernet breakout at the module interface | Specify a duplex single-mode channel; any MPO in the structured cabling is an internal backbone choice, not the transceiver interface. |
A quote for any other part number needs its own current datasheet. Another vendor can use a similar family label but expose a different interface or operating mode.
Why the same 400G rate uses different cables
The aggregate Ethernet rate tells you how much data crosses the link. It does not tell you how the optical lanes are placed on fibers.
Parallel optics assign lanes to separate transmit and receive fiber paths. IEEE's public scope for 400GBASE-SR8 describes eight multimode-fiber pairs for a reach of at least 100 m. (IEEE 802.3cm scope) A named DR4 implementation also uses four single-mode transmit/receive pairs, although its reach and modulation differ from SR8.
400GBASE-FR4 uses wavelength-division multiplexing: four optical lanes share a duplex single-mode path. IEEE describes the FR4 objective as four WDM lanes over single-mode fiber for at least 2 km. (IEEE 802.3cu explainer) A named FR4 module can therefore present duplex LC while a named DR4 module presents MPO-12.
QSFP-DD and OSFP describe package formats. Neither label identifies the front-panel optical interface. Check the interface specification before selecting MPO-16, MPO-12, or duplex LC.
Cable rules by 400G optic
400G SR8: verify MPO-16 and polish from the module
SR8 uses eight multimode transmit/receive pairs. Its sixteen active paths fit an MPO-16 interface, but the module design still determines the polish. Multimode does not automatically mean UPC.
Cisco specifies an MPO-16 APC interface and up to 100 m on OM4 for QDD-400G-SR8-S. (Cisco 400G QSFP-DD specifications) This example is enough to reject the shortcut "multimode MPO always means UPC." It does not define every SR8 module.
For this example, the RFQ should identify QDD-400G-SR8-S and state MPO-16 APC. The downstream cable drawing must then define key orientation, pinning, lane assignment, and cable gender. "MPO-16 multimode cable" is not a complete description.
400G SR4.2: MPO-12 is not interchangeable with SR8
SR4.2 uses a different lane architecture from SR8. Cisco's QDD-400G-SR4.2-BD example uses MPO-12 UPC and supports named multimode reaches of 70 m on OM3, 100 m on OM4, and 150 m on OM5. (Cisco 400G QSFP-DD specifications)
An MPO-12 shell, a familiar polarity label, or a passive harness does not make an SR4.2 channel equivalent to SR8. The bidirectional lane behavior, remote endpoint, and platform mode must match the module documentation.
400G DR4: separate the MPO shell from the active paths
A named DR4 implementation uses four single-mode transmit/receive pairs, or eight active fibers, within an MPO-12 interface. Cisco specifies MPO-12 APC and up to 500 m for QDD-400G-DR4-S. (Cisco 400G QSFP-DD specifications)
"MPO-12" identifies the interface family; it does not mean all twelve fiber positions carry optical lanes. The cable drawing should show the active positions and the transmit-to-receive mapping. HPE equipment guidance shows why pinning must be checked rather than guessed: it describes pinned transceiver receptacles and the unpinned connector normally presented at the equipment port. (HPE MPO connector guidance)
400G FR4 and 4x100G-FR solve different problems
In Cisco's named examples, QDD-400G-FR4-S multiplexes four wavelengths onto a duplex LC/UPC single-mode interface, while QDD-4X100G-FR-S exposes four independent FR1 lanes through MPO-12 APC. Cisco lists up to 2 km for both products, but their external optical architectures are not cable-equivalent. (Cisco 400G QSFP-DD specifications)
FR4 can traverse structured cabling that uses MPO trunks internally, provided the complete duplex path meets the design. But the patch connection to the named FR4 transceiver is duplex LC. An internal MPO backbone does not turn FR4 into a passive four-port breakout.
Can a 400G port break out to four 100G links?
Sometimes. A cable cannot create a breakout mode that the optics and platform do not support. Check all of the following:
- the host 400G transceiver's external lane architecture;
- the switch, router, or NIC breakout mode;
- the four remote 100G transceivers;
- wavelength, lane architecture, and reach compatibility;
- FEC and port-configuration requirements;
- the passive cable's lane and polarity map.
| Host case | Can a passive harness lead to four 100G endpoints? | Why |
|---|---|---|
| Named DR4 implementation | Conditional | Cisco documents 4x100G use for QDD-400G-DR4-S on specific platforms and with named DR1, FR1, or LR1 endpoints; its table limits that cited breakout system to 500 m. (Cisco datasheet) |
| Named 4x100G-FR implementation | Conditional by design | QDD-4X100G-FR-S exposes four independent FR1 lanes and cites up to 2 km to named endpoints, but the platform and remote modules still have to be supported. (Cisco datasheet) |
| Named PLR4 implementation | Conditional, for a different reach class | HPE documents S3N94A as a 400G PLR4 QSFP-DD with an MPO-12 APC single-mode interface and a 10 km reach. Its breakout guidance uses an SMF MPO-to-4xLC assembly to named single-lane 100G LR endpoints and warns that 100G LR4 is not compatible. Platform and module support still control. (HPE PLR4 specifications; HPE breakout guidance) |
| Named SR8 implementation | Depends on the implementation | Cisco lists 2x200G-SR4 and 8x50G-SR for its named SR8, while HPE documents a separate named SR8-to-4x100G-SR2 solution. That difference is evidence that "SR8 to 4x100G" is not a generic cable rule. (Cisco datasheet; HPE breakout example) |
| 400GBASE-FR4 | No passive four-port Ethernet breakout at the module interface | The four wavelengths are multiplexed inside the optic onto one duplex fiber path; a passive MPO-to-LC harness does not create four independent Ethernet interfaces. (IEEE FR4 overview) |
Before requesting an assembly, add a 400G-specific lane map to the MPO polarity planning worksheet. Physical continuity is not enough. If the supplier cannot show the exact endpoint map and current platform support, do not release the breakout. Once those checks pass, review the available MPO breakout and harness configurations.
Use the optic's channel-loss ceiling
Ignore universal rules such as "every 400G connector must be low loss." Start with the maximum supported channel insertion loss in the transceiver document, then allocate that budget across the actual topology.
Cisco's named values show why: 1.9 dB for QDD-400G-SR8-S, 3.0 dB for QDD-400G-DR4-S, and 4.0 dB for QDD-4X100G-FR-S. (Cisco 400G QSFP-DD specifications) These values apply to the cited part numbers and conditions. They are not targets for every SR8, DR4, or breakout channel.
Use this design relationship:
maximum supported channel loss − planned passive loss − engineering margin ≥ 0
The planned passive loss must be calculated against the real route. A component label is not a substitute for an end-to-end channel result.
Record the optic-specific ceiling in the interface record. Use the separate MPO trunk cable guide to count connections and allocate passive loss. Use the MPO polarity planning worksheet for the lane map, BOM, test requirements, and approvals.
Keep inspection and measurement separate. IEC 61300-3-35:2022 covers end-face inspection and says inspection does not replace attenuation or return-loss measurement. IEC 61280-4-5:2020 covers attenuation, polarity, and length for installed cabling that is exclusively MPO-to-MPO. A mixed MPO-to-LC path needs a project-approved method that covers the actual channel. (IEC inspection scope; IEC MPO test scope)
Do not use an OTDR trace as automatic proof that the channel meets its end-to-end insertion-loss allowance. An OTDR can help characterize events along a route, while the acceptance plan must separately name the required end-to-end loss method, reference method, wavelengths, directions, and limits. IEC 61280-4-2:2024 covers attenuation and optical return-loss measurements for installed single-mode cabling. IEC 61280-4-1:2019+A1:2021 covers attenuation measurement for installed multimode cabling with single-fiber test interfaces. IEC 61280-4-5 remains the more specific reference for cabling that is exclusively MPO-to-MPO and tested through MPO interfaces. (IEC single-mode test scope; IEC multimode test scope; OTDR and end-to-end loss distinction)
IEC 61754-7-1 defines one-row MPO interface dimensions, while ANSI/TIA-568.3-E addresses optical-fiber cabling components. Neither reference, by itself, proves that a quoted assembly matches a transceiver or passes a project acceptance plan. (IEC 61754-7-1; TIA announcement)
ISO/IEC 11801-5:2017 specifies generic cabling within and to data-center computer-room spaces. It provides data-center cabling context, but it does not select an optic, prove a breakout mode, or certify a quoted assembly. (ISO/IEC 11801-5 scope)
Create a five-field 400G interface record
Use the BWNFiber five-field 400G interface record before discussing cable construction. It is the optical evidence layer of a 400G MPO cable specification, not the finished drawing or RFQ.
| Interface-record field | Evidence owner | Hold condition |
|---|---|---|
| Endpoint A: exact module part number, host platform, and document revision | Network/optics owner | A family label such as "400G SR8" replaces the exact SKU. |
| Endpoint B: exact peer module or every breakout module, plus the host platform | Network/optics owner | The remote optic or platform is unknown. |
| External optical architecture | Module vendor | SR8, SR4.2, DR4, 4x100G-FR, or FR4 is inferred from connector appearance. |
| Module interface | Module vendor | Fiber medium, MPO row format or LC, polish, reach, and active paths are not explicit. |
| Operating boundary | Equipment/module vendor | Requested breakout mode, compatible remote optics, FEC context, or maximum channel loss is unconfirmed. |
A supplier substitution reopens any affected field. A matching connector is not enough. Compare the replacement part number, interface, polish, active positions, and supported mode against the approved record.
The interface record deliberately does not set the finished cable construction. The downstream project specification must still define route length, bend-radius constraints, assembly type and total fiber count, tensile and crush limits, jacket and fire classification, and any water, UV, or rodent exposure. The exact interface record constrains the connector and active paths; route, topology, installation method, local rules, and controlled product evidence complete the construction specification. Mechanical, jacket, and environmental requirements cannot be inferred from the label "400G," the optic family, or the MPO shell.
When all five fields have evidence, transfer the record to the MPO polarity planning worksheet for the physical route, pin/key, lane trace, controlled BOM, tests, approvals, and change log. If procurement first needs to distinguish trunks, patch cords, harnesses, and cassettes, use the separate MPO cable types guide.
Common 400G MPO cable interface mistakes
- Ordering only "a 400G MPO cable" leaves the optical standard, row format, polish, lane map, and breakout mode unresolved.
- Assuming multimode means UPC can produce the wrong polish for a named SR8 interface.
- Treating FR4 and 4x100G-FR as synonyms confuses duplex WDM with independent parallel lanes.
- Treating a harness drawing as proof of switch support ignores the platform and port mode.
- Copying a channel-loss value from a neighboring SKU assigns an operating limit without evidence.
FAQ
Does every 400G transceiver use an MPO cable?
No. Named SR8, SR4.2, DR4, and parallel 4x100G-FR examples use MPO interfaces, while a named 400GBASE-FR4 example uses duplex LC. The exact module document controls.
What is the difference between MPO-12 and MPO-16 for 400G?
They are different MPO row formats. A named DR4 or SR4.2 module can use MPO-12, while a named SR8 module can use MPO-16. Shell size alone does not define active lanes, polish, or compatibility.
Does a QSFP-DD or OSFP form factor determine the 400G cable interface?
No. QSFP-DD and OSFP describe module packaging. The module specification, not the form factor, determines whether the external interface is MPO-16, MPO-12, or duplex LC, along with the fiber medium and polish.
What must match at both endpoints before selecting a 400G cable?
Verify the exact module part numbers, host platforms, external optical architecture, interface, fiber medium, polish, reach conditions, and channel-loss limits. For breakout links, also verify port mode, remote optics, wavelength, and FEC requirements.
Does 400G SR8 use APC or UPC?
Do not infer polish from "SR8" or "multimode." Cisco specifies MPO-16 APC for QDD-400G-SR8-S. Check the exact part number at both ends before ordering.
How many active fibers does 400G DR4 use?
DR4 uses four transmit/receive pairs, so a named implementation has eight active fibers within an MPO-12 interface. The approved lane map should show the active positions.
Which 400G MPO optics can break out to four 100G single-lane links?
There is no connector-only answer. Cisco documents conditional DR4 and 4x100G-FR cases for named 100G endpoints. For a longer named example, HPE documents its S3N94A 400G PLR4 over an MPO-12 APC single-mode interface to four single-lane 100G LR endpoints at up to 10 km; HPE explicitly distinguishes those endpoints from 100G LR4. Verify the exact modules, platforms, port mode, FEC, reach, and lane map before selecting the harness. (Cisco datasheet; HPE PLR4 specifications; HPE breakout guidance)
Is 400GBASE-FR4 the same as 4x100G-FR?
No. FR4 wavelength-multiplexes four lanes onto a duplex fiber pair. A 4x100G-FR implementation exposes four independent FR1 paths for breakout.
Can SR8 always break out to four 100G ports?
No. Published examples differ: one vendor's named SR8 supports other breakout patterns, while another vendor documents a specific SR8-to-SR2 solution. Validate the exact module, remote optics, and platform.
Can a supplier substitute another 400G optic with the same connector?
Not from the connector match alone. The replacement can differ in lane architecture, polish, reach, channel-loss limit, or supported breakout. Reopen the interface record and verify the new part number against both endpoints and platforms.
Why can an MPO harness fit while the 400G breakout still stays down?
The connector and passive lane map can be physically correct while the host platform, port mode, remote optics, wavelength, reach, or FEC is incompatible. Mechanical fit proves only that the connectors mate.
What if the module document says only "MPO"?
Hold the interface record. Ask the module vendor for the row format, fiber medium, polish, active positions, reach, breakout modes, and channel-loss allowance. Do not fill the gaps from connector color or a related SKU.
Submit a 400G optic pair before specifying the cable
Send BWNFiber:
- the endpoint A module part number and host platform;
- the endpoint B module, or every breakout module, and each host platform;
- the requested port and breakout mode;
- the current vendor datasheets or compatibility tables.
Ask BWNFiber to flag missing or contradictory interface fields before any 400G MPO cable or duplex-LC assembly enters construction and quotation. Submit the 400G optic pair.
Procurement handoff after interface validation
| Procurement gate | Buyer action | Evidence needed before advancing |
|---|---|---|
| The interface record is open | Hold cable selection and obtain the current endpoint documents. | All five interface fields are source-controlled and approved. |
| The interface record is closed | Transfer it to the polarity worksheet and request the exact assembly drawing and quotation scope. | Route, lane map, construction, test scope, quantity, and document revision are explicit. |
| Offers are ready to compare | Compare price and lead time only when suppliers are quoting the same approved scope. If a sample is required, define its part number, revision, purpose, inspection or test criteria, approver, and relationship to the bulk-order baseline. | The quotation revision, any sample disposition, and the documents controlling the purchase order are approved. |
For an international RFQ, also state the destination country, indoor or outdoor route, applicable project and fire-safety documents, required label and document language, packaging instructions, named delivery location, and agreed trade term. These inputs do not alter the five-field optical interface record, but they can change construction approval, compliance review, logistics, and schedule.
The BWNFiber workflow defined on this page has a deliberately narrow role: surfacing unresolved interface fields before a cable configuration is quoted. A specification sheet, sample, test report, price, MOQ, lead time, availability statement, or delivery commitment should be treated as available only when it appears for the exact configuration in a current controlled document or quotation.
Technical references
- Cisco 400G QSFP-DD transceiver specifications
- HPE 400G PLR4 specifications and compatibility
- HPE 400G PLR4 breakout guidance
- IEEE 802.3cm public scope for 400GBASE-SR8
- IEEE overview of 400GBASE-FR4 development
- IEC 61754-7-1 MPO interface standard page
- IEC 61300-3-35 connector-inspection standard page
- IEC 61280-4-5 MPO installed-cabling test standard page
- IEC 61280-4-2 single-mode installed-cabling test standard page
- IEC 61280-4-1 multimode installed-cabling test standard page
- ISO/IEC 11801-5 data-center generic cabling standard page
- Fluke Networks OTDR and end-to-end loss testing guide
- ANSI/TIA-568.3-E announcement
Technical scope disclaimer: The cited reach and loss figures apply only to the named module or public standard scope. They are for reference only, not a guarantee of BWNFiber product performance, interoperability, or project results. Recheck source revisions and part numbers before design release.
