Dear @Daljeet Singh Virdi
After investigating the issue, it appears to be related to the following warning message:
“Same local ID is associated with two different remote IPs. ”
Best regards,
Nouha

The problem is most likely related to the following scenario:

The IP data of LABS1188 (10.39.15.177) was originally linked to a node called LBBK5061O.

After you imported the data, the IP became associated with the new node (LABS1188), but the interfaces of the old node still exist (as shown in the screenshot), along with their related AdditionalInfo.

In fact, there is still an interface between the old node (LBBK5061O) and the core element with IP 10.74.15.113.

Because of this, the new interface is not being created between 10.39.15.177 and 10.74.15.113—it already exists under the old node.

What we kindly ask you to do:

Manually delete the old interface named LBBK5061O_USN9810BTC02_S1-MME_1.

Re-import the node LABS1188 and its AdditionalInfo.

Verify if the missing interface is created correctly, and update us with the result.

If this resolves the issue, then we can confirm the root cause and proceed to update our code accordingly

Did manual delete of interface, will check tommorw

Issue still remains same. Asked L2 to generate XML for Huawei and NSN RAN nodes.

As checked in XML, both the nodes are having same Local IP. Due to which RAN logical interface is not getting created. Asked L2 to share the dumps.

Dear @Mustapha Al-Hage,

As checked and found Huawei Node (LBBK5061O) is outdated and same has been deleted manually from the NEP.
Will check the error in RB tomorrow.

@MUshtapha, The issue is not reproduceable now and the Logical info for NE LBBK5061O is missing now in dumps as well as NEP. and LABS1188 is now routed in RB report.