Optical port loopback operations

2

Loopbacks are used to locate faults. An outloop can be used to test whether the fiber line and connector are normal. An inloop can be used to test whether signals are correctly processed inside a board. Both outloops and inloops are software loopback operations performed on the NMS.

Other related questions:
The state of an optical interface is not Up when it interconnects with the peer device
For the problem that the state of an optical interface is not Up when it interconnects with the peer device, see the troubleshooting guide. For details, access the URL in the right column.

Hardware loopback and software loopback
A hardware loopback is performed on a physical port (an optical port) using a fiber. It must be performed onsite, while a software loopback can be configured on the NMS. A loopback will interrupt services, and therefore it is often used for deployment commissioning or service interruption diagnosis.

Channel loopback
A channel loopback loops back a single ODUk signal rather than signals of an entire board. A channel loopback on one service does not affect other services on the same board. It is used to check whether an ODUk signal sent from a tributary board is normal and whether the line board can properly process this ODUk signal.

Can I use a GE optical module on a 10GE optical port or a 100M optical module on a GE optical port
A high-speed optical port supports low-speed SFP, eSFP, and SPF+ modules. Generally, optical ports on a modular switch support low-speed optical modules. However, on a fixed switch, downlink optical ports support low-speed optical modules, but uplink optical ports do not. You can use a GE optical module on a 10GE optical port or a 100M optical module on a GE optical port. NOTE: Normally, you are not advised to install a low-speed optical module on a high speed optical port.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top