DATACENTER TWIN LAB

Infrastructure Engineering · Lesson 21 of 24 · 25 minutes

Separate physical routes, optical budgets and fabric capacity

Two fibres are not automatically two independent services, and a low optical loss is not automatically an application pass. Separate the physical administration route from the logical fabric, then calculate a narrow loss budget and post-uplink-loss capacity. The lesson adds communications reasoning without pretending that the existing electrical simulator already models packets.

Run this lesson interactively

Learning objectives

Source statement

Draw two different maps

Entrance arrangements, MDA, IDA/HDA, optional ZDA and EDA identify physical distribution and administration spaces. Leaf, spine, core and access identify logical connectivity or function. A top-of-rack switch can exist within a structured-cabling hierarchy. Two logical paths can still share a tray, patch panel, room, fire boundary, maintenance zone or transceiver supply. Preserve those physical dependencies rather than using a complete-looking mesh as proof.

Illustrative assumption

Add the channel losses

The teaching channel is 100 m at 3.5 dB/km, four connector events at 0.35 dB, two splices at 0.1 dB and 0.5 dB engineering margin. The total budget allocation is 2.45 dB. Against an explicitly illustrative 2.6 dB interface budget, only 0.15 dB remains. Engineering margin is budget allocation, not a literal extra connector or measured attenuation. Dispersion, bandwidth, wavelength, polarity, reflectance and interface compatibility remain separate.

Unresolved

Recalculate after a link loss

Forty-eight 25 Gb/s downlinks total 1,200 Gb/s. Six 100 Gb/s uplinks total 600 Gb/s, giving 2:1 nominal oversubscription. One lost uplink leaves 500 Gb/s and a ratio of 2.4:1. This is a line-rate capacity ratio, not predicted application throughput. The underlying cabling guide is historical and the manuscript’s 2024 standards excerpt is front matter only; no missing normative clauses or current transceiver limits are supplied.

Predict → run → explain

  1. Read the declared boundary and units. Predict the selected result before calculating.
  2. Run the starting case and inspect the ledger, assumptions and model limits.
  3. Apply the challenge, run again, and explain the difference. Export only the last completed inputs and results.

Physical dB = length m/1,000 × dB/km + connectors × connector dB + splices × splice dB; allocation dB = physical dB + engineering margin; remaining dB = budget − allocation; ratio = downlink Gb/s / active uplink Gb/s. With zero active uplinks, the model is disconnected and ratio is unavailable.

Declared starting inputs

{
  "lengthM": 100,
  "dbPerKm": 3.5,
  "connectors": 4,
  "connectorDB": 0.35,
  "splices": 2,
  "spliceDB": 0.1,
  "engineeringMarginDB": 0.5,
  "budgetDB": 2.6,
  "downlinks": 48,
  "downlinkGbps": 25,
  "uplinks": 6,
  "uplinkGbps": 100,
  "lostUplinks": 0
}
Worked default — unrounded educational outputs
QuantityValueUnit
physicalLossDB1.95dB
budgetUseDB2.45dB
remainingMarginDB0.1499999999999999dB
activeUplinkGbps600Gb/s
oversubscription2ratio or null when disconnected
connectivityconnectedconnectivity state
statusscreen-satisfiedscreen state

Challenge

Does one uplink failure change the optical budget of the remaining channel?

{
  "lostUplinks": 1
}

The line-rate ratio becomes 2.4:1. The separately declared optical channel stays at 2.45 dB allocation and 0.15 dB remaining margin.

Worked challenge
QuantityValueUnit
physicalLossDB1.95dB
budgetUseDB2.45dB
remainingMarginDB0.1499999999999999dB
activeUplinkGbps500Gb/s
oversubscription2.4ratio or null when disconnected
connectivityconnectedconnectivity state
statusscreen-satisfiedscreen state

A physical route beneath the logical fabric — static equivalent

  1. Reveal entrance → distribution spaces → racks on a physical floor plane.
  2. Lift the logical leaf–spine fabric above it without merging the identities.
  3. Inspect each optical loss event and a separate margin reservation.
  4. Remove one uplink and recalculate the capacity ratio; expose shared trays separately.

Separate physical-route and logical-link tables plus optical-loss and line-rate ledgers.

Toggle physical/logical layers, remove uplinks with keyboard controls and inspect each loss term.

Narrative steps are not physical seconds. Essential states and quantities remain available without animation.

Assessment and answer criteria

9.1 · Find loss allocation for 200 m at 3 dB/km, two 0.4 dB connectors and 0.5 dB margin.

Read answer and marking criterion

1.9 dB.

Criterion: Convert metres to kilometres and keep margin explicit.

Source: DCIE-R1 Appendix A, PDF pp.59-61

9.2 · Find normal and one-uplink-lost ratios for 32 × 25 Gb/s downlinks and 4 × 100 Gb/s uplinks.

Read answer and marking criterion

2:1 normally; 800/300 ≈ 2.67:1 after one loss.

Criterion: Recalculate only active uplink capacity.

Source: DCIE-R1 Appendix A, PDF pp.59-61

9.3 · Why is attenuation alone insufficient for a high-speed multimode channel?

Read answer and marking criterion

Bandwidth, dispersion, polarity, reflectance and interface compatibility also require evidence.

Criterion: Do not call a loss screen full application conformity.

Source: DCIE-R1 Appendix A, PDF pp.59-61

Source and model boundaries

Data Centre Infrastructure Engineering, reference manuscript revision 1 (DCIE-R1), 11 October 2026, chapter 9, PDF pp.42–45. PDF page 1 includes the cover. manuscript-derived; not independent source verification.

Original educational adaptation. The private PDF and missing archive are not public downloads. Source statement, Editorial derivation, Illustrative assumption and Unresolved remain distinct.

Result schema: infrastructure-screen-1; content 2.0.0; model 1.0.0. Raw inputs, outputs, units, assumptions, source locators and canonical hashes. No supported in-browser Python verification protocol exists for this result family.