Keywords

Link merging

Case Information

U2000	OS	Database	NE
--	--	--	--

 

Symptom

After adding a GNE, a user imports link planning data and performs synchronization. When the synchronization is complete, the planned and actual links are all displayed in the DCN topology without being automatically merged. Planned links are displayed in orange, and actual links in green, as shown in the following figure.

Problem Identification

The names of NE interfaces at both ends of a planned link are different from those of an actual link, which causes the merging failure.

Problem Locating and Cause Analysis

The planned and actual links can be automatically merged only when the following requirements are met:

l   The planned and actual links have been merged at one end.

 

l   The planned and actual links have the same NE interface name configured at the other end. As shown in the following figure, the planned and actual links between RSG98 and ASG2 have different interface names on the ASG2 side. Therefore, the two links cannot be automatically merged.

 

NOTE

   In initial status, if the sysname of the GNE on the planned link is the same as that on the actual link, the two GNEs on the links are   automatically merged first.

Solutions

l   Solution 1: Modify the link planning table and import it to the plug-and-play management system again.

l   Solution 2: Merge links manually, as shown in the following figure.

 

Suggestion and Summary

To achieve the automatic merging of planned and actual links, check that the names of NE interfaces at both ends of the planned link are the same as those of the actual link and select the involved NE in the DCN view to perform synchronization. Alternatively, merge the planned and actual links manually. During manual merging, you must change the value of NE Interface for the planned link in the Manually Merge Link dialog box to be the same as that of the actual link.