Hello, everyone!
Today, I will continue to write about troubleshooting optical networks. This is the second article about this topic. Let’s get started.
In the aerial installation, the optical cables must be at the correct height in order to be damaged. Especially on busy roads. For underground installations, the cables must be at a depth of 1 or 1.2 m, marked with a warning tape and use markers where possible.
Installations in data centers or headends should be in special channels or pipes. It all ends in rack cabinets, which are usually closed. In this way, damaged by unqualified persons is prevented. In situations where there is a risk of rodents or damage due to pressure or sharp objects, an armored optical cable should be installed.
Figure 1. Troubleshooting optical networks
Documentation is very important. Documentation is prepared during the design and during the installation. It should be very detailed, containing many data such as:
types of optical cables, fibers, optical connectors, optical splitters, patch panels, etc.,
capacities of optical cables, active and backup optical fibers,
location of service loops,
routes for optical cables, with GPS locations,
method installations,
information about optical powers,
OLTS and OTDR test results, etc.
In addition, all active and passive equipment must be marked. To make that marking simple and clear. To enable quick navigation.
I want to repeat, we must have a procedure in case of an accident. First, we need to have detailed documentation. Second, we need to have trained staff for troubleshooting with accidents, spare active and passive components and optical cables. And of course, the tools and instruments to solve the problem. The following instruments are required to resolve accidents:
optical microscope,
tools, wipes, and cleaning fluids for fibers and optical connectors,
broadband optical power meter,
PON power meter,
VFL,
fiber identifier, and
OTDR.
This is the end of this article. I will continue to write about this topic in the next article >> Troubleshooting optical networks (3).
Thank you!
