Chinese
English
Problem Description
Four OSN2500 devices are connected two by two to form a MESH network, and ASON intelligence is turned on for each network element. After ASON intelligence is successfully turned on, two default intelligent domains are found under the "Intelligent Topology Management" view, and after deleting the original intelligent domains and then creating new intelligent domains, the four network elements still cannot enter the same intelligent domain. After deleting the original smart domain and creating a new smart domain, the four network elements still cannot enter the same smart domain. Because the network elements are in different intelligent domains, many intelligent functions of ASON cannot be realized.
Alarm message
None
Process
First, check the ASON version of each network element, and find that there is no abnormality in the version, which is a unified version;
Check the node ID of each network element, and there is no duplicate node ID number;
Finally, check the DCC of each network element, and find that the D4-D12 of two network elements can't communicate normally, and check the DCC resources, and find that there is only a 3-byte DCC resource allocated in the DCC resources, and there is no 9-byte DCC resource allocated, so you re-allocate 9-byte DCC resources in the "DCC resource allocation". Re-allocate 9 bytes of DCC resources in "DCC Resource Allocation", and check the communication between D4-D12 after completion. Re-upload the network element data, so the smart network elements are in the same smart domain, and the problem is solved.
Root Cause
Multiple network elements are in different intelligent domains probably because the control planes of the intelligent network elements cannot communicate with each other;
There may be several reasons why the control planes of smart network elements cannot communicate with each other:
1, ASON version mismatch;
2, duplicate node IDs of network elements;
3, abnormal D4-D12 communication between network elements.
Recommendations and Summary
When this problem occurs, firstly, check whether the ASON versions of each network element are consistent, and consider upgrading if they are not consistent;
Secondly, check whether the node IDs of each network element are duplicated, and if they are duplicated, modify the duplicated IDs (the network element will be reset softly after modification);
Finally, check whether the communication between D4-D12 of each network element is normal, if not, you need to check whether the optical path is normal and whether the "DCC Resource Allocation" allocates 9 bytes of DCC resources.
The above three steps can solve the problem that OSN2500 intelligent network elements are no longer in the same intelligent domain.
