Optical Transport
The building blocks that turn lit fiber into real services. Once you can name each component, say what it does, and say where it sits on the path, any Ekinops design becomes readable — and any fault becomes a place to look rather than a mystery.
Every component below does exactly one of four jobs: convert a signal (transponder/muxponder/regen), combine or split wavelengths (mux/demux, OADM/ROADM), add power (EDFA/Raman), or carry management (OSC). Keep sorting each part into one of those four buckets and the whole system stays legible.
Client side vs line side
Every transport device has two faces. The client side faces your world — routers, switches, servers, SAN — usually with familiar grey short-reach optics (SR/LR pluggables at a standard nominal wavelength like 1310 nm, all the same colour, cheap, interchangeable). The line side faces the optical network — a specific coloured DWDM wavelength on a precise ITU-grid channel, often generated by a tunable laser so one card can be set to any channel. The device's whole job is to bridge those two worlds.
Why grey on the client
Client optics are commodity. The router doesn't know or care that a transport box is downstream — it just lights a standard short/long-reach pluggable. That keeps the client world cheap, swappable, and vendor-neutral.
Why coloured on the line
The line side must land on an exact ITU channel so dozens of wavelengths can share one fiber without colliding. Tunable lasers mean you stock one card type and provision its channel, instead of stocking 96 fixed-colour cards.
Transponder vs muxponder
Both are O-E-O (optical → electrical → optical) converters that adapt a grey client to a coloured line wavelength. The difference is purely how many clients ride one wavelength.
Transponder — 1 client → 1 line λ
Takes one client and converts it to one line wavelength. Simplest possible client-to-λ adapter. Use it when a service already fills the wavelength (e.g. a 100G client onto a 100G line) or when you deliberately want one customer alone on a lambda.
Muxponder — N clients → 1 line λ
Aggregates several lower-rate clients into one higher-rate line wavelength (commonly with OTN mapping underneath). Fewer wavelengths burned for the same traffic — critical when fiber or channel count is the scarce resource.
Assuming a muxponder is "free" aggregation. Every client you add shares the fate of that one wavelength — cut the line λ and all N clients drop together. Aggregation trades wavelength efficiency for a larger blast radius. If two of those clients need independent survivability, they may belong on separate wavelengths (or separate protected paths), not stacked in the same muxponder.
1R / 2R / 3R — amplify vs regenerate
Signals degrade two different ways over distance: they lose power, and they lose quality (noise accumulates — OSNR drops — and chromatic dispersion smears the pulses). These need different fixes. The "R" count tells you how much rebuilding a device does.
| Class | What it does | Domain | Fixes power? | Fixes OSNR / dispersion? |
|---|---|---|---|---|
| 1R — re-amplify | Boosts power only (an amplifier, e.g. EDFA) | Analog / optical | Yes | No — amplifies the noise along with the signal, adds its own ASE noise |
| 2R — + re-shape | Boosts and squares up the pulse shape | Partly electrical | Yes | Partly — cleans shape but not timing jitter; rare on its own in modern DWDM |
| 3R — + re-time (regen) | Re-amplify + re-shape + re-time: a full O-E-O rebuild | Electrical (O-E-O) | Yes | Yes — resets OSNR and dispersion to like-new; the signal is regenerated from decoded bits |
An alien wavelength is a wavelength generated by a third-party transponder (not the line-system vendor's) that the DWDM line system carries transparently end to end — the line system amplifies and switches the light without terminating it. Powerful (mix vendors, put coherent pluggables straight in routers) but it means the line system can't see inside that signal, so OSNR and reach planning for the alien λ are on you, not the line vendor's turnkey tool.
EDFA vs Raman amplification
Both add optical power to all channels at once without O-E-O. They differ in where the gain happens and what it buys you.
EDFA (erbium-doped fiber amplifier)
- C-band, roughly 1530–1565 nm.
- Typical gain ~15–25 dB; amplifies the whole band in one shot.
- Adds ASE noise (noise figure ~4–6 dB) — so it lifts power but slowly erodes OSNR each hop.
- Needs gain-flattening / tilt control so channels at the band edges aren't left high or low.
- Gain is lumped in a box at the site.
Raman amplification
- A high-power pump laser injects into the transmission fiber itself.
- Gain is distributed along the fiber, not lumped — it effectively amplifies before the signal has fully decayed, so it improves OSNR and extends reach.
- More complex and has real laser-safety implications (high pump power on the live fiber).
- Often paired with EDFAs on the longest spans, not instead of them.
Believing amplifiers "fix" a marginal link. They do not touch the OSNR floor or dispersion — only power. Stacking EDFAs on a link that's already noise-limited just makes a louder bad signal and can drive receivers into overload. When reach (not power) is the wall, the answer is a 3R regenerator or a more capable coherent transponder, not more gain.
OSC — the optical supervisory channel
The OSC is a dedicated out-of-band management wavelength (often around 1510 nm or 1625 nm, outside the amplified C-band traffic) that carries management, comms, and telemetry between optical nodes. Crucially it is dropped, terminated, and regenerated at every node — because it must be readable at each site — while the amplified traffic band passes straight through the amplifiers untouched.
The OSC is how you reach a remote shelf whose traffic path is broken. If a span's traffic is down but the OSC is up, you can still log into the far node, read alarms, and drive a switch. If the OSC itself is down between two sites, you are managing blind past that point — that's often your first clue to which span failed.
OADM vs ROADM
OADM — fixed add/drop
Optical Add/Drop Multiplexer. Passive filters drop and add a specific, hard-wired set of channels at a site; everything else expresses through. Cheap, simple, no power — but the channel plan is set in the glass. Changing which λ drops here means a truck roll and new filters.
ROADM — reconfigurable add/drop
Reconfigurable OADM. A WSS (wavelength-selective switch) steers any channel to any direction/port under software control. You provision add/drop/express remotely — no re-cabling. This is what makes mesh optical networks and remote wavelength turn-up possible.
- Colorless — any wavelength can go to any add/drop port (the port isn't wired to one fixed colour).
- Directionless — an added/dropped wavelength can be sent to any line direction, not one pre-cabled way.
- Contentionless — no internal blocking; the same wavelength can be added/dropped in multiple directions at once without colliding inside the node.
A node's degree = the number of line directions it connects. A degree-2 node sits on a line (east/west); a degree ≥3 node is a mesh branch point where a ROADM chooses which direction each wavelength takes.
Topologies
Point-to-point
Two sites, one span. Simplest and most common — DCI, back-to-back offices, a single leased-lambda service. Protection here means a whole second diverse span.
Linear w/ add-drop
A chain of sites; intermediate nodes drop/add some channels and express the rest. OADM or ROADM at the middle sites.
Ring
Sites on a loop (2-fiber or 4-fiber). Survives a single cut by sending traffic the other way around. Efficient shared protection.
Mesh (ROADM degree ≥3)
Mesh needs ROADMs of degree ≥3 at the branch points. It's the optical equivalent of a routed core with multiple paths: expensive, but a cut becomes a reroute rather than an outage.
Component reference table
The one table to keep handy when reading a design. "Where it sits" tells you which part of the path it lives on; "what to check" is your first operational move when something's wrong.
| Component | What it does | Where it sits | What to check |
|---|---|---|---|
| Transponder | Converts one client signal to one line wavelength (O-E-O) | Between client gear and the line system | Client + line Tx/Rx power, correct channel, client service up |
| Muxponder | Aggregates several clients into one higher-rate wavelength | Between multiple client ports and one line port | Each client's status, aggregate line rate, OTN mapping/tributary config |
| Mux / demux | Combines (mux) / separates (demux) wavelengths on one fiber | At the fiber junction of the line system | Per-channel port assignment, insertion loss, clean connectors |
| EDFA (amplifier) | Optically boosts power of all C-band channels at once (1R) | Booster (post-Tx), inline (mid-span), pre-amp (pre-Rx) | Input/output power, gain, tilt/flatness, not driving Rx into overload |
| Raman | Distributed gain via pump laser into the span fiber; lifts OSNR | Into the transmission fiber, usually longest spans | Pump power, OSNR gain, laser-safety interlocks, fiber cleanliness |
| Regenerator (3R) | Rebuilds a degraded signal (re-amplify + re-shape + re-time) | Mid-path where optical reach/OSNR runs out | Whether the problem is power (amp) or quality (regen), pre/post-FEC errors |
| OADM | Fixed add/drop of specific channels; rest express through | Intermediate/terminal site on the line | Which channels drop vs express, port mapping, insertion loss |
| ROADM (WSS) | Software-reconfigurable add/drop and per-λ routing; CDC/degree | Flexible / mesh branch sites (degree ≥3) | Wavelength routing config, per-channel power balancing, blocked/contended paths |
| OSC | Out-of-band management λ, dropped + regenerated at each node | A dedicated wavelength (~1510/1625 nm) alongside traffic | OSC link up between adjacent sites, reachability of remote shelves |
Common use cases
DCI — data-center interconnect
Very high capacity per fiber, low latency, short-to-metro reach. Increasingly done with 400G ZR / ZR+ coherent pluggables placed straight into the routers (the router is the transponder, an alien-wavelength model) or with dedicated transponders/muxponders.
Watch: per-fiber capacity ceiling, latency budget, and whether router pluggables or the line system own OSNR/reach planning.
SAN extension
Fibre Channel (storage/replication) over WDM between sites. Distance drives buffer-to-buffer credits (too few and FC throughput collapses over distance) and the choice of sync vs async replication. Rule of thumb: ~5 µs/km one-way, so ~1 ms round trip per 100 km (approximate).
Watch: latency vs the array's sync-replication limit; BB-credit sizing; timing preservation.
Carrier wavelength service
Hand a customer a transparent lambda — a point-to-point pipe they light with their own optics. Often an alien wavelength to your line system.
Watch: the demarc and who owns OSNR/reach; what client rates the λ must transparently carry; monitoring you can offer when you can't see inside the customer's signal.
Reaching for an amplifier when you actually need a regenerator. An EDFA raises power and its own noise — if signal quality (OSNR) is already poor, more amplification won't fix errors. Degraded power → amplify. Degraded quality / reach exceeded → regenerate (or go coherent).
1. A design shows one line wavelength carrying ten 10G clients. Transponder or muxponder — and what's the operational catch?
2. A span's traffic is degraded. The optical power is fine but the pre-FEC error rate is climbing. Add an amplifier or a regenerator?
3. Why is the OSC dropped and regenerated at every node while the traffic band just passes through the amplifiers?
4. What does a node's "degree" tell you, and what's the minimum degree for a mesh branch point?