NE Sysname Conflict Is Reported When a Replacement NE Is Configured to Go Online in Planning-free Mode

 Keywords

NE go-online after replacement

Symptom

After an NE is replaced and the replacement NE is configured to go online in planning-free mode, a message is displayed indicating a sysname conflict. Actually, the NE used before the replacement has already been deleted from the Main Topology, and the associated NE and link information has already been deleted from the plug-and-play management system.

Problem Identification

After the NE is replaced, the pre-replacement NE that has went offline is not removed from the DCN view. As a result, its information still exists in the database table.

Solution

Search for the associated GNE based on the name of the pre-replacement NE or its upstream NE.

Then remove the GNE from the DCN view and add it to the view again.