When we are using fiber optic transceivers, we will inevitably encounter some problems. How do we solve these common problems? The following Fiber Closure manufacturer will introduce you to everyone.
1, Power light is not bright
2, the Link light is not bright
The fault may be as follows:
Check if the fiber line is open.
Check if the fiber line loss is too large and exceed the receiving range of the device.
Check that the fiber interface is properly connected. The local TX is connected to the remote RX, and the remote TX is connected to the local RX.
Check whether the fiber connector is properly inserted into the device interface, whether the jumper type matches the device interface, whether the device type matches the fiber, and whether the device transmission length matches the distance.
3, the circuit Link light is not bright
The fault may be as follows:
Check if the network cable is open.
Check whether the connection type matches: devices such as network cards and routers use cross-wires, switches, hubs, etc., using straight-through lines.
Check if the device transfer rate matches.
4, The network packet loss is serious: The possible faults are as follows:
The electrical port of the transceiver is connected to the network device, or the duplex mode of the interface of the two devices does not match. Twisted pair and RJ-45 head have problems and are tested.
Fiber connection problem, whether the jumper is aligned with the device interface, whether the pigtail matches the jumper and coupler type.
Whether the fiber line loss exceeds the device acceptance sensitivity.
5, the fiber transceiver can not communicate after the two ends are connected
The fiber is reversed, and the fiber connected to TX and RX is reversed.
The RJ45 interface is not properly connected to the external device (note that the straight-through and the spliced) fiber interface (ceramic ferrule) does not match. This fault is mainly reflected in the 100M transceiver with photoelectric mutual control function, such as the APC ferrule The transceiver of the PC ferrule will not be able to communicate normally, but the non-optical mutual control transceiver will not affect. 6, time pass and time phenomenon:
It may be that the optical path attenuation is too large. At this time, the optical power of the receiving end can be measured by the optical power meter. If it is near the receiving sensitivity range, the optical path fault can be judged within the range of 1~2dB.
The switch connected to the transceiver may be faulty. In this case, the switch is replaced by a PC, that is, the two transceivers are directly connected to the PC, and the two ends are connected to PING. If the switch is not present, the switch can be determined to be a fault of the switch.
It may be a transceiver failure. In this case, connect the transceiver to the PC at both ends (not through the switch). After both ends have no problem with PING, transfer a large file (100M) from one end to the other end, and observe its speed. If the speed is very slow (files of less than 200M are transmitted for more than 15 minutes), the transceiver can be judged to be faulty.
6, after a period of communication, the crash, that is, can not communicate, resume normally after restarting
This phenomenon is generally caused by the switch. The switch performs CRC error detection and length check on all received data. It checks that the packet with the error will be discarded and the correct packet will be forwarded. However, some packets with errors in this process are not detected in the CRC error detection and length check. Such packets will not be sent during the forwarding process and will not be discarded. They will be accumulated in the dynamic cache. (buffer), can never be sent out, wait until the buffer is full, it will cause the switch to crash. Because restarting the transceiver or restarting the switch at this time can restore the communication to normal, the user usually thinks it is a problem with the transceiver.