WDM ports on certain boards (LOG, LSX, and NS2) report new OCH_OCI alarms after an internal fiber connection is created on the OSN 6800. The NE version of the OSN 6800 is 188.8.131.52.
1. Verify that the fiber connection on the network management board is consistent with the fiber connection of the equipment and that the fiber connection from each OTU board to the demultiplexer board has been created.
2. Perform fiber synchronization in the NE Explorer. The number of uncreated fibers of the NE and the number of uncreated fibers of the network management system are zero. You can exclude the possibility that the fiber connections on the network management system are inconsistent with the actual fiber connections of the NE.
3. On the entire network, no optical cross-connect board is configured and only electrical cross-connect boards are configured. You can exclude a configuration problem of optical cross-connections.
4. Check the network design and you can find that the transmitters of the multiplexer part are configured with no optical amplifier board (output signals of the M40 are directly transmitted to the line board) and only the receivers are configured with the OBU and D40 boards. As confirmed, OCH_OCI alarms are generated in such networking mode. Such alarms are a feature of the equipment version and do not affect services. You can suppress the alarms directly.
1. No optical cross-connection is configured for the upstream service link.
2. No fiber connection is configured from the OTU board to the demultiplexer board.
3. The networking configuration is improper. For example, no optical amplifier board is configured for the upstream station.
1. There are two possible causes of an OCH_OCI alarm. One is that the physical fiber connections are inconsistent with the logical ones. In this case, services are not affected. The other is that the optical cross-connections that are transmitted to this station are not configured at the upstream station.
2. The OCH_OCI alarm is defined imperfectly in the current V1R3 version. Factors (for example, unconventional networking design) other than the preceding two causes are also likely to trigger this alarm. This aspect will be improved in V1R4 and later versions.