Optical transport and troubleshooting
Documented troubleshooting: evidence, changes and handoff
A document-based review can organize a problem and guide the next check without equipment in front of you. A useful handoff shows what evidence exists and how far it supports a conclusion.
Link every fact to its source
Identify equipment, optics, ports, firmware and route. For each capture or log, record who obtained it, date, time, units and system state. Distinguish a manual requirement from a reported observation: a data sheet supporting an optic does not prove that optic is installed.
Separate facts and hypotheses
Record the reported symptom, visible states and contradictions. For each hypothesis, record the supporting evidence and the check that could distinguish it from the alternatives. An abnormal RX reading may point toward several components; do not turn that clue into a definitive diagnosis of damaged fiber.
Hand off a verifiable next step
Retain earlier configuration and diagrams, changes actually reported and their observed effects. Separate proposed changes from executed ones. Identify a specific check, its scope, observation criterion and who can perform it for the system. Without a physical test, describe the conclusion as a document review rather than a verified repair.
Information for a link review
| Item | What to record | Purpose |
|---|---|---|
| Documentation | Models, versions, manuals and requirements | Establish what applies to the assembly |
| Observation | Captures, logs, source and date | Show what was observed or reported |
| Hypothesis and next step | Possible explanation, evidence and proposed check | Let another technician continue without assumed results |
Before approaching an optical connection
Do not look into optical ports or fiber ends, even when no light is visible. Inspection, cleaning and measurement require the manufacturer’s tools and procedures. If the assembly is hybrid and also carries power, identify the complete system and arrange work with qualified personnel.
Technical questions
Does “no signal” alone prove the fiber is broken?
No. Causes may involve endpoints, optics, configuration or the route. Collect evidence from both ends.
Does a picture capture verify stability?
It documents only the captured state. Continuity requires observation under defined conditions with actual duration recorded.
What if two records conflict?
Keep both, verify identity, time and configuration, and identify the information needed to resolve the difference. Do not choose one without evidence.
Further documentation
- Cisco — Troubleshoot Fiber Links on Catalyst 9000 Series Switches — Module and fiber compatibility and TX/RX interpretation on Catalyst 9000.
- Juniper — show interfaces diagnostics optics — DOM diagnostics on EX/QFX; fields and alarms depend on module support.
- Fluke Networks — 5 Vital Safety Rules for Fiber Optic Cables — Optical safety and suitable tools.