In the T2000, the routing information of an SDH trail is inconsistent with the displayed information of the ASON trail. In the SDH circuit, the ASON attribute is displayed as NO, but a corresponding diamond-level ASON trail can be seen. In the SDH trail management, the engineers right-click the SDH circuit and query related ASON trails, but the failure information is returned. The engineers also right-click in the ASON trail management to query related SDH trails, but the failure information is still returned. The engineers doubt that the SDH trail information is inconsistent with the ASON trail information.
1. The engineers synchronize the configuration of the ASON trail and cross-connection of a single station.
2. The engineers perform the trail searching and delete the conflicted trails. Then, the correct end-to-end circuit information is restored.
The engineers confirm with the O&M personnel of the customer and perform the preceding steps. Then, the T2000 data of the current network is restored.
After analysis, the engineers conclude that the problem is caused by the conflict between the SDH end-to-end information and the ASON trail information. Hence, the primary task of the engineers is to solve the inconsistency between the information displayed in the T2000.
Based on the symptoms and the analysis on the log, the possible causes of the problem are as follows:
(1) The data of the T2000 and NE is consistent due to network faults.
The end-to-end trail “TNS00972007_I29P3J1-TNS09127003_I11P1J7_Diamond” is created on “2007-12-10 16:49:41”. The ASON trail with inconsistent data “TNS00972007_I29P3J1-TNS09127003_I11P1J7-VC4 Server Trail” is created on “2008-02-06 20:40:39.0”. It can be seen that a classic VC-4 path is created on 2007-12-10. The source of the path is TNS09127003 and sink is TNS00972007. In the period from 2007-12-10 to 2008-02-06, an upgrade operation is performed for the trail. The trail at the NE side is successfully upgraded to the ASON trail; however, due to network faults (for example, the DNS network that connects the T2000 and NEs is faulty) or other reasons, the T2000 does not receive a response from the NE. As a result, the T2000 determines that the upgrade fails and does not refresh the information in the SDH end-to-end trail management interface. On 2008-02-06 20:40, the ASON trails in the entire network are synchronized and the T2000 detects the ASON trail That is upgraded successfully before. Hence, a diamond-level trail with the source TNS09013004 and sink TNS00972005 is displayed in the ASON trail interface. However, in the SDH end-to-end ASON trail management interface, due to the timeout caused by network faults as mentioned above, the T2000 regards that the upgrade fails and does not refresh the end-to-end trail information. Instead, the routing is displayed as the static common service in the interface.
(2) Multiple sets of T2000s are used to manage one network.
If multiple sets of T2000s are used to manage the equipment in the current network, the data consistency as mentioned above may also occur. For example, suppose the end-to-end classic trail is created in T2000 A and the upgrade to the ASON trail is performed in T2000 B successfully. When the synchronization of ASON trails in the entire network is performed in T2000 A, the newly upgraded ASON trails are also synchronized. However, the end-to-end trail in T2000 A does not receive the ASON trail upgrade success information. As a result, the end-to-end information and the ASON trail information are inconsistent.
(3) Trail-related configuration operations are performed in the current network by using the command line or LCT.
The reason is the same as reason 2.
When the network is faulty or multiple sets of T2000s are used to manage one network, the inconsistency between the end-to-end trail information and ASON trail information mentioned in this case will occur. When this symptom is found in the T2000, the engineers should re-perform the SDH trail searching and upgrade the end-to-end trail information in sync.