Duplicate node IDs for MW nodes have been observed, specifically for UBR nodes (i.e., Cambium). As discussed with the customer, for operational reasons they do not want any changes in the existing ID/Object ID column. After analysis with the product team, we finalized that a new column, referred to as Object ID, needs to be created with unique values for NEP functioning.

sharing one sample id from delhi circle for working..2401:4900:0:134:0:877:0:341, 2401:4900:0:134:0:877:0:342
In this cases, same IPV6 IP are used for Cambium, Aviat & Ceragon nodes, & IP addresses are used as ID in XML in network element report
so, links are available for both cambium & Aviat/Ceragon in XML due different link ID because interfaces are also used in link ID with concatenation.

That is why this issue is coming, multiple links are available for different OEM with duplicate IP, whereas only one node is imported in network element report.