Keywords

fiber does not turn red, fiber coloring, MUT_LOS

Version Mapping

NMS	OS	Database	NE
U2000 V100R009C00SPC200	Windows	Microsoft SQL Server	-

Symptom

The OLP board of an OptiX BWS 1600G reports the MUT_LOS alarm, but the related fiber does not turn red in the topology view.

Problem Identification

1           Quality problems exist in the U2000 V100R009C00SPC200 to V100R009C00SPC201. When a fiber is created between an OptiX BMS 1600G (earlier than 5.8.7.20) and an OSN 1800 (excluded in the range 5.67.2.10-5.67.3.89), the port location information and FDN of the fiber are incorrect.

2           After an upgrade or patch installation is implemented for the U2000, the port location information and FDN of the fiber are still incorrect. Alarms cannot be associated.

3           If an abnormal fiber exists and the U2000 version is upgraded, it is possible that a port is traversed by two fibers.

Cause Analysis

1.         View the InventoryDM logs and find the NE alarm information.

Warn ,[T5577],INVCORE TNAlarmCollectMgr: receive alarm. sn:16821522, id:186, faultflag:1, fdn:ONE=4063344,NE=3146120,FR=0,S=4,CP=-1,PP=3||2|,FB=10|1||, the PortID:196610

2.         The failure to associate the alarm with the fiber is printed in the logs.

Warn ,[T5577],INVCORE the alarminfo event id is 186

Warn ,[T5577],default not find a link by portfdn,and the alarmfdn is :ONE=4063344,NE=3146120,FR=0,S=4,CP=-1,PP=3||2|,FB=10|1||

3.         Check the fiber in the database and find that the subrack cAShelf is -1. The alarm FDN does not match the fiber FDN, and the alarm cannot be located to the fiber.

 

4.         The fiber port FDN stored in the inventory database is obtained from the NE management process when the fiber is created. Check the related code of the NE management process for obtaining the FDN and find that a quality problem exists in the U2000 V100R009C00SPC200. As a result, when a fiber is created between the OptiX BMS 1600G (earlier than 5.8.7.20) and an OSN 1800 (excluded in the range 5.67.2.10-5.67.3.89), an incorrect FDN is obtained from the NE.

5.         The problem has been resolved in the U2000 V100R009C00SPC201. However, for created fibers, the data is not restored and the alarm cannot be associated with the fibers. In this case, the source and sink ports of the abnormal fibers are still available during fiber creation.

Solution

Two solutions are provided for the OptiX BMS 1600G based on its version:

1           For the OptiX BMS 1600G later than 5.08.6.10, resolve the problem by synchronizing fibers.

Filter fibers based on the type of the OptiX BMS 1600G and the fiber creation time (V100R009C00SPC200 to SPC201) and delete the fibers on the U2000. Ensure that the database is backed up before the fibers are deleted. Synchronize WDM fibers and search out fibers/cables that traverse the OptiX BMS 1600G. Check whether the number of fibers/cables that are not created on the U2000 is consistent with the number of fibers that are deleted from the U2000. Then search for WDM trails and protection subnets.

2           The OptiX BMS 1600G earlier than 5.08.6.10 does not support fiber synchronization. Resolve the problem by importing a script.

Restore the database on the live network and run database commands to find the fibers that traverse the OptiX BMS 1600G and that are created when the U2000 is upgraded from V100R009C00SPC200 to V100R009C00SPC201. Change the subrack ID to 0 (based on the actual situation) and export the network-layer information file using the script import and export function. In the fiber/cable management window, delete the abnormal fibers from the network layer, import the network-layer information file, and verify the result. If no exception occurs during the verification, send the script to frontline engineers to resolve the problem.

If a message is displayed indicating that the port resources have been occupied when the script is imported, the reason is as follows: The subrack ID of the abnormal fibers created on the U2000 V100R009C00SPC200 is -1 and fibers can still be created on the same ports. During the script import, the subrack ID has been corrected and fibers cannot be created on the same ports. Therefore, the error message is displayed indicating that the port resources have been occupied. Confirm the situation on the live network and delete redundant fibers.

 

NOTE

In this case, you need to modify the database. Contact Huawei R&D engineers for a solution.

For the OSN 1800, resolve the problem by synchronizing fibers.

Suggestions and Summary

1.         Check whether the U2000 version belongs to the abnormal version range. If yes, find the fibers that are created within this period and install the latest patch or upgrade the U2000.

2.         If an upgrade or patch installation has been implemented for the U2000, find the fibers that are created on the abnormal U2000 based on the fiber creation time. If you forget the patch installation or upgrade time, determine whether the problem occurs by using the script export method. Abnormal fibers cannot be exported.

3.         If you have installed the latest patch and detected that the problem exists, resolve the problem by synchronizing fibers. If the device version is too earlier, contact Huawei R&D engineers for a solution.