Phenomenon Description

On a certain day, a bureau OSN2500 suddenly reports NODE_ID_CONFLICT exception alarm, which has no effect on the services in the existing network.

Cause Analysis

NODEID conflict in the intelligent domain.

Other reasons.

Procedure

Check that the intelligent network elements have no abnormal alarms, normal protocols, normal operation of the intelligent network, and no impact on services.

Check that no newly added intelligent network elements exist in the network, and check that no abnormal operation records exist for the network elements.

Check that there is no conflict in the NODEID of the intelligent network elements in the network intelligent network.

Check that no abnormal reset records exist for network elements reporting alarms. use :ospf-get-onetopo to check that all network elements in the intelligent domain show consistency.

Use :ospf-get-nodeid-alm to check that the value of Remain Time keeps changing, which indicates that the conflicting data of the network element is transmitted back.

By analyzing the black box logs of the network element, it is found that the nodeid address of port 18-3 is the same for sending and receiving data, and it is verified that port 18-3 is not connected to an intelligent network element (the counterpart of which is Risecommunication MSAP equipment).

The main control board of Risecommunication MSAP device is found to be faulty, which leads to abnormal return message. The problem is solved after replacing the main control board of the MSAP device.

Recommendation Summary

Make sure to disable the LMP and OSPF protocols when connecting a smart network element to a non-smart network element.