Most 400G and 800G upgrades in a working hall inherit a cable plant pulled for 40G or 100G parallel optics: Base-12 trunks, MPO-12 cassettes and panels laid out around twelve-fiber connectors. The useful question is which of those parts stay. This guide follows the order a system integrator works in: read the transceiver interface, audit the trunk, choose the Base, draw the link hop by hop, then write the purchase list. It complements our AI data center fiber cabling guide, which covers the design of new builds.

Quick answer
- 400GBASE-DR4 uses eight single-mode fibers on an MPO-12 APC interface. An installed OS2 Base-12 trunk may be reusable after its polish, pinning, keying, polarity, lane map and measured channel loss are checked against the selected module. The four center fibers remain unused in that DR4 link.
- 800GBASE-DR8 uses sixteen single-mode fibers. Module variants present one MPO-16 or two MPO-12 connectors. A dual-MPO-12 variant may reuse two compatible Base-12 links; a single MPO-16 variant requires a verified conversion harness or a compatible Base-16 path.
- Multimode Base-12 (OM3/OM4) can carry 400GBASE-SR4 or SR4.2 inside 100 m on OM4, with channel loss of 1.8 dB or less. DR4 and DR8 need single-mode.
- Replace or rework a trunk if its fiber type, end-face polish, connector arrangement, lane mapping or measured loss cannot meet the selected channel requirements. Decide which end components to change only after that audit.
The five steps
- Read the transceiver interface
- Audit the trunk you own
- Choose the Base
- Draw the link
- Write the purchase list
Read the transceiver interface before the trunk
The module decides everything downstream, so its datasheet comes first. Table 1 lists the IEEE 802.3 applications that run over parallel fiber and use MPO connectors. Duplex variants such as 400GBASE-FR4 and LR4 run on one LC pair, so they reuse existing single-mode LC plant and never touch the MPO Base decision.
| Application | Fibers | Fiber type | Module connector | Channel loss limit | Reach |
|---|---|---|---|---|---|
| 400GBASE-DR4 | 8 | OS2, 1310 nm | MPO-12 APC | 3.0 dB | 500 m |
| 800GBASE-DR8 | 16 | OS2, 1310 nm | MPO-16 APC, or dual MPO-12 APC (module variant) | 3.0 dB | 500 m |
| 400GBASE-SR4 | 8 | OM3 / OM4 / OM5, 850 nm | MPO-12 | 1.7 / 1.8 dB (OM3 / OM4) | 60 / 100 m |
| 400GBASE-SR4.2 | 8 | OM3 / OM4 / OM5, 850 + 910 nm | MPO-12 | 1.7 / 1.8 / 2.0 dB | 70 / 100 / 150 m |
| 400GBASE-SR8 | 16 | OM3 / OM4, 850 nm | MPO-16 | 1.8 / 1.9 dB (OM3 / OM4) | 70 / 100 m |
Sources: Fiber Optics Tech Consortium application overviews (linked in the first column) and vendor datasheets. Cisco lists MPO-12 APC on its QSFP-400G-DR4 module. Multimode modules differ in polish, so read the module datasheet.
One 800G port, two connector presentations
Cisco lists the same 800GBASE-DR8 function in two OSFP variants: OSFP-800G-DR8 with dual MPO-12 APC, and OSFP-800G-DR8P with one MPO-16 APC. Both also support 2x 400GBASE-DR4, 4x 200GBASE-DR2 and 8x 100GBASE-DR1 breakouts to 500 m. Panduit describes the same split across the market as three module interface formats: 16-fiber MPO, 8/12-fiber MPO and dual 8/12-fiber MPO (Panduit, DCD).
The consequence is practical. A dual-MPO-12 module plugs into two existing Base-12 links. A single-MPO-16 module needs a new Base-16 link or a harness. Ask the switch vendor for the exact module part number before the trunk BOM is fixed, because that one field decides which branch of this guide applies.
Why an MPO-12 port uses eight of its twelve positions
On four-lane parallel optics the transmit lanes take positions 1 to 4 and the receive lanes take positions 12 to 9. The Fiber Optic Association MPO reference shows this arrangement for 40GBASE-SR4; DR4 and SR4 modules follow the same outer-eight pattern, and the module datasheet confirms the lane map. Corning's application note on Base-8 structured cabling states the choice for a Base-12 plant directly: leave the four middle fibers dark, or add a conversion device. On a trunk that is already installed, leaving them dark costs nothing further.
Figure 1. The four-lane pattern on a 12-position ferrule. Positions 5 to 8 carry no signal.
Audit the trunk you own before choosing a Base
Six checks decide reuse. Each one is answerable from the label, the installation test report or a fiber scope.
The six-check trunk passport
1. Fiber type
DR4 and DR8 need single-mode, so OS2 (ITU-T G.652.D) is the relevant trunk fiber type; fiber type alone does not establish that a complete installed link can be reused. An OM3 or OM4 trunk belongs to the multimode 400G family: SR4 at 60 m on OM3 or 100 m on OM4, or SR4.2 at 70, 100 or 150 m by grade. Their channel-loss ceilings of 1.7 to 2.0 dB leave little room. Two connections planned at 0.75 dB each would already use 1.5 dB of a 1.8 dB OM4 budget.
2. End-face polish
Vendor datasheets list APC (8-degree angled) MPO on DR4 and DR8 module ports. An APC end-face cannot mate with a flat UPC end-face, so a UPC-terminated trunk cannot serve an APC port without re-termination. Connector housing color varies by manufacturer and gives a hint only. Confirm the polish with a scope and the test report.
3. Connector count and key
MPO-12 carries a center key. MPO-16 carries an offset key defined in TIA-604-18 and IEC 61754-7-3/-7-4, designed so a 16-fiber connector cannot mate with standard MPO hardware (US Conec MTP-16 handout). Existing MPO-12 adapters, cassettes and panels therefore cannot take an MPO-16 port directly.
4. Polarity method
TIA-568.3-E, published in September 2022, defines array methods A, B, C, U1 and U2 (Siemon summary, CommScope summary). Read the method from the drawing or label. Mixed components require a documented end-to-end map; a method name on one cord alone cannot establish channel polarity.
5. Gender and pinning
Siemon's TIA-568.3-E guidance recommends pinned trunks at both ends, unpinned connectors inside MPO-to-LC modules, and unpinned patch cords facing pinned active-equipment ports for systems designed to support future array links. Confirm the actual module and component pinning; each mated pair needs one pinned side and one unpinned side. The FOA discusses the reference-cable method for plug-and-jack MPO testing (FOA reference cables).
6. Measured loss and end-face condition
Ask for the installation test report and read the per-fiber dB values. Then inspect every end-face to IEC 61300-3-35 practice and clean before any re-test; our connector cleaning guide lists MPO-specific tools.
Engineer's note
A report that shows only pass or fail per fiber says nothing about a 3.0 dB budget. Treat that plant as untested for DR4 and DR8 and re-measure a representative sample of links with an MPO-native test set before the purchase order goes out. The measured dB values also feed the loss ledger below.
A loss ledger for reused plant
The cited DR4 and DR8 application overviews specify 3.0 dB maximum channel insertion loss. Table 2 is an illustrative sensitivity check for 200 m of OS2 at an assumed 0.4 dB/km (0.08 dB of fiber loss). It applies the same assumed loss to every mated pair solely to show how connection count changes the result; it is not a design acceptance table or a claim that every component in a Glory assembly has that rating. The 0.75 dB scenario reflects a historical multifiber allowance discussed by the FOA; actual component values and the selected module's reference planes must govern the final budget.
| Example topology (assumed mated pairs) | 0.75 dB per pair | 0.60 dB per pair | 0.35 dB per pair |
|---|---|---|---|
| Adapter panel at each end (2) | 1.58 | 1.28 | 0.78 |
| Conversion module at each end (4) | 3.08 | 2.48 | 1.48 |
| Modules at both ends plus a cross-connect (6) | 4.58 | 3.68 | 2.18 |
These are hypothetical topologies, not measured links. The count assumes that transceiver-to-cord interfaces are outside the cited channel reference planes; verify that convention with the exact module datasheet. A conversion module, cassette, splice or cross-connect may have a component-specific loss that cannot be represented by one uniform per-pair figure. Check reflectance separately.
Under these assumptions, four 0.75 dB connections exceed the 3.0 dB limit before any margin is reserved. A real reuse decision needs the measured trunk loss, the specified maximum for every added component, the module's reference planes and a project margin. The values on Glory's data center cabling page require confirmation in the relevant product datasheets before they are used as per-connection limits.
Choose the Base by the condition it fits
Table 3 summarizes where each Base earns its place in an existing hall. Base-8 is a cabling system organized in eight-fiber increments, as described in Corning's Base-8 application note; the DR4 example uses eight active positions on an MPO-12 module interface. Mechanical mating with MPO-12 hardware alone does not establish compatible fiber mapping, polarity or cassette wiring; verify mixed-system designs component by component.
| Base | Native fit | Choose it when | Watch for |
|---|---|---|---|
| Base-12 | DR4, dual-MPO-12 DR8, SR4, SR4.2 when the fiber and interfaces match | The installed path passes all six checks | Four unused fibers in each DR4 leg; MPO-16 ports need a verified harness |
| Base-8 | Eight-fiber DR4 and SR4 links | New pulls in a DR4-dominant fabric | Check cassette and polarity compatibility with any Base-12 hardware; an MPO-16 port needs a mapped breakout path |
| Base-16 | DR8 and SR8 on one connector | New pulls will serve single-MPO-16 800G ports | Offset key needs its own adapters and panels |
| Base-24 | Aggregation of 3x8 or 2x12 groups | Pathway space limits cable count | Conversion modules add mated pairs and need one mapping drawing |
Keep Base-12 when the trunk passes the audit
An installed OS2 Base-12 trunk is a reuse candidate for DR4 or a dual-MPO-12 DR8 module when its polish, pinning, key orientation, polarity, lane map and measured channel loss all match the selected equipment. That decision differs from specifying Base-12 for a new DR4 plant: our new-build AI data center guide warns against choosing it only because it is familiar. For an installed, compatible trunk, compare the cost and downtime of a new pull with the end components needed for reuse.
Add Base-16 or Base-8 for new pulls
Decide the module presentation first, then the trunk. If the switches you will buy present one MPO-16 per 800G port, a Base-16 trunk gives one connector per port with all sixteen fibers in use, and a harness at the leaf side splits it into two 8-fiber groups for DR4 ports. If the fabric is DR4 only, Base-8 matches the module exactly. Keep one module presentation across the fabric so the Base decision does not repeat at every rack.
Use Base-24 for aggregation only where pathways force it
Base-24 packs two rows of twelve. Corning's application note describes regrouping two separate 12-fiber links into three 8-fiber links; that example does not, by itself, validate a single MPO-24 trunk design. Our MTP/MPO cable types guide describes 24-to-2x12 and 24-to-3x8 conversion assemblies. A single-trunk design requires a matching assembly at each end, a supplier-approved lane map and a component-specific loss budget. Table 2 shows why added connection points deserve scrutiny; its four-pair row is only a planning example.
Three link schemes, drawn hop by hop
These figures are conceptual array-to-array layouts, not released assembly drawings. They mark the intended fiber type, polish, pinning and polarity path. Filled squares are pinned (male) ends; hollow squares are unpinned (female) ends. Confirm end-face orientation, keying, lane assignments and loss against the exact transceiver and supplier assembly before ordering.
Polarity as a parity count
For a parallel channel, Tx must land on Rx. A reversal count is a useful first check for the one-row array examples below, but it does not establish that APC ferrules mate correctly or that a conversion assembly maps each lane as intended. Table 4 lists the assumed contribution of simple components; confirm the completed path with a manufacturer's drawing and polarity test.
| Component | Reversals |
|---|---|
| Type-A cable (straight through) | 0 |
| Type-B cable (positions reversed) | 1 |
| Type-A adapter (key-up to key-down) | 0 |
| Type-B adapter (key-up to key-up) | 1 |
| Conversion harness or module | Per manufacturer drawing; state it on the purchase order |
Duplex breakouts follow the Method A/B/C/U1/U2 rules of TIA-568.3-E; the parity count applies to array-to-array channels. Confirm every build against your manufacturer's polarity drawing.
Engineer's note
A replacement cord with the wrong polarity can make a link fail even when its connectors are clean and its fibers pass continuity checks. Print the cord type on the jacket label, keep the approved map in the rack and test the complete channel after a change.
Scheme A: reuse the Base-12 trunk
Use this example only for an existing Type-B, pinned, APC-terminated OS2 trunk that passes all six checks. It shows Type-A (key-up/key-down) adapters at the panel interfaces, following the single-mode APC mating approach discussed in the Siemon polarity guidance. Confirm the exact end-face orientation, complete lane map and module channel-loss reference planes before treating its two panel connections as the budgeted mated pairs. MPO-12-to-LC modules may serve 4x 100G DR1 breakouts when their internal mapping and the equipment's breakout mode match.
Figure 2. Conceptual Scheme A: 400G-DR4 over a verified Type-B Base-12 OS2 trunk. A compatible dual-MPO-12 800G module can use two mapped legs.
Variant A2: a single MPO-16 port on Base-12 trunks
A vendor-approved MPO-16 to 2x MPO-12 harness may present one 800G port to two compatible Base-12 links. If it replaces an existing cord at the same connection points, it need not add a mated pair; confirm this in the actual topology. Specify each connector's pinning and APC orientation, take the lane assignments from the exact 800G module and harness drawings, and test both mapped legs before declaring the installed trunks reusable.
Scheme B: pull new Base-16 (or Base-8)
Choose Scheme B when the existing trunk fails the audit or when single-MPO-16 ports dominate the switch plan. The MPO-16 offset key requires matching MPO-16 interfaces at its connection points. This example uses a Type-B trunk and Type-A (key-up/key-down) adapters; its APC mating and lane map still require supplier verification. At the far side a compatible harness can split the 16 fibers into two mapped 8-fiber groups for DR4 ports.
Figure 3. Conceptual Scheme B: 800G-DR8 over a new Base-16 OS2 trunk; verify the exact APC assembly and polarity before procurement.
Scheme C: Base-24 aggregation
Choose Scheme C where tray space limits the cable count and both ends can host conversion modules. Work outward from the trunk: the trunk is pinned, so the module rear connector is unpinned; the cords are unpinned, so the module front connectors are pinned. This face-by-face assignment comes from the one-pinned-side rule and needs confirming for each vendor, because conversion modules follow no single gender convention. Compare cassette and cassette-less layouts in our high-density ODF guide.
Figure 4. Conceptual Scheme C: a single MPO-24 trunk regrouped into three DR4 links at each end, subject to a supplier-approved conversion assembly and lane map.
Turn the design into a purchase list
A purchase order that names only "MPO-12 trunk, 30 m" leaves key interface and testing questions open. Table 5 lists the fields to specify and the Glory product or documentation category to confirm in a project quote.
| Field | Write on the order | Glory category or document to confirm |
|---|---|---|
| Fiber type | OS2 (G.652.D) for DR4/DR8; OM4 or OM5 for SR4/SR4.2/SR8 | MPO/MTP trunks in OS2, OM3, OM4 and OM5 |
| Interface | MPO-12, MPO-16 or MPO-24, populated positions, module part number | Elite trunks in 8, 12 and 16 fibers; 24-fiber trunk |
| Polish and gender | APC or UPC per the exact module; pinned or unpinned at each end | Connector polish and pinning at every mating face, subject to the project drawing |
| Polarity | Method, cable type at each segment, adapter type, reversal total | Type A, B, C or custom polarity, per the OEM/ODM page |
| Conversion parts | Lane map drawing for every harness or module pair | Confirm the required harness or conversion configuration and approved drawing through the quote form |
| Link loss | Each component's specified maximum, measured installed loss and reserved margin | Product-specific IL/RL specification and factory test report; confirm the unit and reference method |
| Panels | Adapter panel or cassette, density, depth | MPO patch panels and 12-fiber MPO-to-LC cassette modules; see our MPO patch panel guide |
| End-face inspection | Scope every end-face before mating (IEC 61300-3-35) | Cleaning method in the cleaning guide |
| Test report | Per-fiber IL and RL, polarity result, end-face images where required | Confirm which factory records and installed-link tests are included in the quoted package |
The published data center cabling page lists Elite and standard trunk IL figures and typical dispatch windows of 3–7 business days for stocked products and 7–15 business days for custom projects. These are catalogue statements, not acceptance criteria or a guaranteed project schedule. Confirm the test reference method, exact component values, 16-fiber and 24-fiber module availability, and delivery date in the current quotation.
Acceptance records worth keeping
Test each link with an MPO-native loss set, using the FOA three-cable reference for plug-and-jack MPO ends (FOA MPO testing). Record the polarity result for every channel, store the end-face images, and file the per-fiber report next to the drawing. That folder answers the first question at every later cord swap. For grade differences between MPO and MTP assemblies, see MPO vs MTP pre-terminated fiber, and for the wider connector question including VSFF, see MMC vs MPO/MTP for 400G/800G.
Frequently asked questions
Q: Can an existing MPO-12 trunk carry 400G?
A: Potentially. 400GBASE-DR4 uses eight single-mode fibers on an MPO-12 APC interface (positions 1-4 and 9-12). Reuse an installed OS2 Base-12 trunk only after confirming its end-face polish, connector keying and pinning, end-to-end polarity, lane map, and measured channel loss against the exact transceiver specification. An installed multimode Base-12 trunk may support 400GBASE-SR4 or SR4.2 within the applicable reach and loss limits; it cannot carry DR4.
Q: Do I have to replace Base-12 with Base-8 for 400G-DR4?
A: Not necessarily. The four center fibers of a compatible installed Base-12 trunk remain unused in a DR4 link; keeping the trunk can avoid a new cable pull, although those fibers remain unavailable to that link. Base-8 may suit new DR4-focused runs or a documented conversion that regroups two 12-fiber links into three 8-fiber links. Check component compatibility and polarity before mixing Base-8 and Base-12 parts.
Q: How many fibers and which connector does 800G-DR8 need?
A: 800GBASE-DR8 needs 16 single-mode fibers (eight lanes, two fibers each). Vendors ship the module with either one MPO-16 APC connector or two MPO-12 APC connectors, so the exact module part number decides whether existing Base-12 links can plug in directly.
Q: Can an MPO-16 connector mate with MPO-12 hardware?
A: No. MPO-16 uses an offset key that prevents mating with standard MPO-12 hardware. Reach an MPO-12 panel from an MPO-16 port with an MPO-16 to 2x MPO-12 harness, or use MPO-16 adapters and panels end to end.
Q: When does a Base-24 trunk make sense for 400G or 800G?
A: Base-24 may suit aggregation where pathway space is limited. A 24-fiber trunk can be divided into three 8-fiber groups or two 12-fiber groups only with a compatible, documented conversion assembly at each end. Confirm the lane map, connector presentation, component losses and complete channel budget before ordering.
Q: What insertion loss can a 400G-DR4 or 800G-DR8 channel tolerate?
A: The cited 400GBASE-DR4 and 800GBASE-DR8 application overviews give a 3.0 dB maximum channel insertion loss. Count fiber, mated connections, conversion components and splices according to the selected module's reference-plane definition. Multimode limits depend on the application and fiber grade: consult the relevant SR4, SR4.2 or SR8 specification rather than applying the DR limit.
Q: Why does an MPO link stay dark after an upgrade?
A: The usual causes are polarity parity (an even number of reversals in a parallel channel), a pinned-to-pinned or unpinned-to-unpinned mating, a UPC end-face meeting an APC port, a dirty ferrule, or a wrong lane map on a conversion harness. Inspect and clean every end-face, verify polarity with a tester, then measure loss with an MPO-native test set.
Request a project-specific cabling review
Share the transceiver part numbers, current trunk type, test records, polarity method and rack layout. Ask the team to confirm a component-level drawing, lane map, loss budget and BOM for the proposed reuse path. Start from the data center fiber cabling solution page or use the quote form.
