From dark fiber to lit, managed optical transport
How a pair of dark fibers becomes a set of managed, high-capacity services on Ekinops360 equipment — the physics, the platform, and the operations. No prior optical background assumed; no marketing, just the working model you need to design, turn up, and troubleshoot links.
Start here
Pick the entry point that matches where you are — then use the sidebar to move around. Nothing is locked, and your progress checkboxes save in this browser.
Start from the fiber
Begin at the physical layer — strands and pairs, dB/dBm, insertion loss, loss budgets — then build up through WDM and transport. This is the intended path if optics is new to you.
Go deeper — engineering
Comfortable with fiber and WDM? Jump into the engineering track: loss and OSNR budgets, dispersion, coherent optics, amplification and safety, ROADMs, OTN and timing.
Practice by doing
Interactive labs that build a real design: close a link budget, plan a channel grid, engineer physically diverse protection, and work a graded fault — with live pass/fail checks.
Prefer the whole picture first? The roadmap shows how every topic fits together, or jump straight to the Ekinops360 platform or the Celestis NMS.
The end-to-end picture
Every optical transport link you will ever build is a variation of this stack. Read it top-to-bottom as the journey of one customer's traffic across a dark fiber pair and back into a router on the far side.
Dark fiber = the empty road. It carries no traffic by itself — it is just glass between two points. Ekinops = the transport system that puts controlled traffic lanes on that road. WDM = different colored lanes of light sharing one fiber.
- Client side faces your routers, switches, servers and SAN.
- Line side faces the optical/fiber network.
- A transponder converts one client signal into one transport wavelength.
- A muxponder aggregates several lower-speed clients into one higher-speed transport signal.
- A mux/demux combines many wavelengths onto one fiber and separates them at the far end.
- Amplifiers boost optical power for distance.
- OADM/ROADM add, drop, or route individual wavelengths at a site.
- Celestis NMS manages the gear and gives you service visibility.
How to use this site
This is a self-paced path, not a reference manual to skim. It works best if you turn each topic into something you could hand to a colleague. Follow the same three-beat rhythm the roadmap suggests for each topic:
Read the theory
Work the matching lesson page and take notes in your own words. If you can't restate it plainly, you don't have it yet.
Draw the design
Sketch the topic as a diagram — client side, line side, fiber. Drawing is where the gaps in your mental model surface.
Build the runbook
Turn it into a one-page checklist, budget, or port map you'd actually use in the field. That artifact is the real deliverable.
Tick the progress checkboxes on the roadmap and resources pages — they save in this browser so you can see how far you've come. And do the labs: they build on each other from a two-site 100G link up to a protected, NMS-managed multi-site network, and they are where the theory turns into judgment.
The path at a glance
The course is organized so each layer stands on the one before it. Skipping ahead usually means you turn up a link that "should work on paper" but fails on a loss budget or a dirty connector. Each layer below names what you'll be able to do once you own it — and maps to a group in the sidebar.
Fiber basics
Strands, pairs, single-mode vs multimode, connectors, polarity, dBm, insertion and return loss. The physical medium.
You'll be able to: read a fiber path end to end and spot a polarity or connector problem before it becomes an outage.
Testing & loss budget
Power meter, light source, OTDR, and the loss-budget math that tells you if a span will actually carry light.
You'll be able to: build a loss budget for a span and say whether it closes against a system budget, with margin.
WDM & optical transport
CWDM vs DWDM, the ITU grid, mux/demux, add/drop, and the components that light the fiber.
You'll be able to: lay out a valid channel plan and choose CWDM vs DWDM for a given capacity and reach.
Ekinops360 platform
How Ekinops packages transponders, muxponders, line systems and OTN into a managed platform.
You'll be able to: map any Ekinops design onto the physics and ask the right BOM questions (rate, wavelength, OTN, protection).
Operations & troubleshooting
Celestis NMS, turn-up workflow, fault isolation, protection and OTN. Running it in production.
You'll be able to: turn up a link to a documented baseline and isolate a fault by layer instead of guessing.
Practice
Labs, a glossary for fast lookups, and a resources page to keep going after the course.
You'll be able to: defend a full design end to end — topology, budget, protection, and baselines.
What you will be able to do by the end
Hand this course a dark fiber pair and by the end you can answer, with numbers: Can I light this path, at what speed, with which optics, what loss budget, what protection — and how do I troubleshoot it when it breaks? Everything below is a piece of that single answer.
- Can I light it? Read an optical transport design and explain client side vs line side, every component, and why it is there.
- At what speed / which optics? Tell CWDM from DWDM, pick the right one, and explain what a transponder, muxponder, mux/demux, amplifier, OADM and ROADM each do.
- What loss budget? Calculate a loss budget for a dark-fiber span and decide whether it needs amplification or regeneration.
- What protection? Choose a protection scheme, verify path diversity, and reason about the ~50 ms switch target.
- How do I turn it up? Walk a fiber turn-up from clean-and-inspect through power levels to a passing, baselined service.
- How do I troubleshoot it? Use Celestis NMS to see service state, read pre-/post-FEC and power trends, and start fault isolation.
- How do I sanity-check someone else's work? Ask the right questions when handed an Ekinops design or BOM.
Do not treat "dark fiber" as a service by itself. Dark fiber is the passive fiber path — glass with no light on it. It must be lit with optical equipment before it carries anything. And Ekinops is not dark fiber: Ekinops equipment is what you attach to the fiber to turn it into managed optical transport services. When someone says "we bought dark fiber," the correct next question is "what are we lighting it with, and what's the loss budget?"
You are learning a layer, not a product. The physics (fiber, light, loss) is vendor-neutral and permanent. Ekinops360 is one very good way to implement that physics. Learn the physics first and the platform becomes easy.