http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/LS-615 L3 Support <p>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.</p> <p>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<br/> In this cases, same IPV6 IP are used for Cambium, Aviat &amp; Ceragon nodes, &amp; IP addresses are used as ID in XML in network element report<br/> so, links are available for both cambium &amp; Aviat/Ceragon in XML due different link ID because interfaces are also used in link ID with concatenation.</p> <p>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.</p> LS-615

Duplicate object ID for UBR nodes

CR Urgent Closed Fixed Srishti Kashyap Priyasha Tiwari nep_dev Mon, 1 Sep 2025 15:18:25 +0300 Fri, 27 Feb 2026 08:30:42 +0200 Fri, 27 Feb 2026 08:30:42 +0200 NEP Wed, 3 Sep 2025 00:00:00 +0300 0 3 0 minutes 2 days, 1 hour, 30 minutes 0 minutes 2 days, 1 hour, 30 minutes <p>As agreed we need to implement the below mentioned points.</p> <p>1- in the UBR report change the NEID column name to object ID, and the Object ID name it to NEP Object id ( NEP Part) –<br/> More Clarification<br/> New NEID column need to be added in UBR report name it as object id and data will be of ne id and node id column rename this as NEP object id and put in the last column.</p> <p>2- Ensure if any DB view is using this Object ID , to point to NE ID field as in DB the column remain the same ( NEP part)</p> <p>column name changed facing below problem please suggest:<br/> During the XML import process, it has been observed that the NEID format is being validated against the expected format, which should contain a hyphen (“-”) as the separator.157-461007_10.19.137.46_RJ</p> <p>However, in the current XML input, the NEID format for UBR is appearing as 10.186.4.90_DL, which does not follow the expected convention and therefore fails validation, preventing the data from being imported.</p> <p>Could you please suggest how we should handle this case? Should the XML be corrected at source to match the expected NEID format, or do we need to relax/update the validation logic on our side?</p> <p>Hi Dear,<br/> Build 3.7.71.496 has been released with the following changes:<br/> 1. In the UBR report, the column name NEID has been changed to Object ID, and the previous Object ID has been renamed to NEP Object ID.<br/> 2. Removed the validation for NEID format.<br/> 3. Updated references from Object ID to NEID in the TOPOLOGY_SITECOMPONENT DB view for UBR.</p> <p>some object id in ubr report for cambium is showing blank please check , snapshot attached for your reference .</p> <p>Dear<br/> A separate ticket <a href="http://jira.mobinets.com/jira/browse/LS-683" title="Airtel_object id blank_UBR _cambium_prod" class="issue-link" data-issue-key="LS-683"><del>LS-683</del></a> is created for the last mentioned issue</p> <p>board report the object id is not correct , should be same as the object id for UBR node report. refer the screenshot attached .</p> LS-670 LS-649 Actual Start Mon, 1 Sep 2025 00:00:00 +0300 Baseline End Wed, 3 Sep 2025 00:00:00 +0300 Baseline Start Wed, 3 Sep 2025 00:00:00 +0300 Customer Date of Baselining Tue, 2 Sep 2025 08:21:20 +0300 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Wed, 3 Sep 2025 00:00:00 +0300 Planned Start Wed, 3 Sep 2025 00:00:00 +0300 Rank 0|xtipvd: Rank (Obsolete) 9223372036854775807 VTDirections