Details
-
Type:
CR
-
Status:
Closed
(View Workflow)
-
Priority:
Urgent
-
Resolution: Fixed
-
Component/s: NEP
-
Customer:Airtel India
Description
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.
Attachments
Open Bug
Activity
| Field | Original Value | New Value |
|---|---|---|
| Gantt Options | Milestone (set to milestone: having a due date but zero effort) | |
| Planned Start | 2025-09-03 24:00 (milestone: set planned start date to due date) | |
| Planned End | 2025-09-03 24:00 (milestone: set planned end date to due date) |
| Summary | Duplicate Node ID MW nodes | Duplicate object ID for MW nodes |
| Summary | Duplicate object ID for MW nodes | Duplicate object ID for UBR nodes |
| Assignee | Khaled Khalil [ kkhalil ] | Hassan Abdine [ habdine ] |
| Priority | Normal [ 10002 ] | Urgent [ 10001 ] |
| Labels | nep_dev |
| Description | 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. |
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 these 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. |
| Description |
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 these 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. |
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. |
| Issue Type | Bug [ 1 ] | CR [ 10900 ] |
| Workflow | Mobinets_Dev_BugWF_J4.4 [ 192709 ] | Mobinets_Dev_WF_J4.4 [ 192710 ] |
| Status | Open Bug [ 10108 ] | Opened [ 1 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 2 hours [ 7200 ] | |
| Worklog Id | 276228 [ 276228 ] |
| Baseline Start | 2025-09-03 24:00 (set baseline based of initial work logging) | |
| Baseline End | 2025-09-03 24:00 (set baseline based of initial work logging) |
| Component/s | NEP [ 16200 ] |
-
- Time Spent:
- 30 minutes
-
timeline discussion
| Assignee | Hassan Abdine [ habdine ] | Srishti Kashyap [ skashyap ] |
| Status | Opened [ 1 ] | Pending Requirements [ 10300 ] |
| Status | Pending Requirements [ 10300 ] | Pending Design Session [ 10112 ] |
| Assignee | Srishti Kashyap [ skashyap ] | Khaled Khalil [ kkhalil ] |
| Status | Pending Design Session [ 10112 ] | Dev Scheduled [ 10014 ] |
| Assignee | Khaled Khalil [ kkhalil ] | Srishti Kashyap [ skashyap ] |
-
- Time Spent:
- 30 minutes
-
timeline discussion
| Time Spent | 2 hours [ 7200 ] | 2 hours, 30 minutes [ 9000 ] |
| Worklog Id | 277815 [ 277815 ] |
| Time Spent | 2 hours, 30 minutes [ 9000 ] | 3 hours [ 10800 ] |
| Worklog Id | 277816 [ 277816 ] |
-
- Time Spent:
- 1 hour, 30 minutes
-
Checking jira confirming details with the telco of changes.
-
- Time Spent:
- 6 hours, 30 minutes
-
worked on changing columns and refrence in the three UBR report,changed getting neid blank need to check ...neid validation during xml import ..mailing for it..need to remove the neid format validation,done same testing for it done checking the dbview didnt found any specifc asking integration to share the names of related dbview
column name changed facing below problem please suggest:
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
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.
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?
| Status | Dev Scheduled [ 10014 ] | Implementation in progress [ 10016 ] |
| Status | Implementation in progress [ 10016 ] | Dev Paused [ 10017 ] |
| Time Spent | 3 hours [ 10800 ] | 4 hours, 30 minutes [ 16200 ] |
| Worklog Id | 278141 [ 278141 ] |
-
- Time Spent:
- 2 hours
-
checked the topology_sitecomponenet dbview at RJDBCLONE checked the value checked the creation and its related dbview made the changes with respect to objectid and neid only with refrence to UBR committed the code for
LS-615
-
- Time Spent:
- 2 hours
-
The patch has been deployed on .45 test server for duplicate UBR nodes
Hi Dear,
Build 3.7.71.496 has been released with the following changes:
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.
2. Removed the validation for NEID format.
3. Updated references from Object ID to NEID in the TOPOLOGY_SITECOMPONENT DB view for UBR.
| Status | Dev Paused [ 10017 ] | Implementation in progress [ 10016 ] |
| Status | Implementation in progress [ 10016 ] | To Be Released [ 10400 ] |
| Status | To Be Released [ 10400 ] | Ready for QA [ 10023 ] |
| Assignee | Srishti Kashyap [ skashyap ] | Priyasha Tiwari [ ptiwari ] |
| Time Spent | 4 hours, 30 minutes [ 16200 ] | 1 day, 3 hours [ 39600 ] |
| Worklog Id | 278336 [ 278336 ] |
| Time Spent | 1 day, 3 hours [ 39600 ] | 1 day, 5 hours [ 46800 ] |
| Worklog Id | 278340 [ 278340 ] |
-
- Time Spent:
- 2 hours
-
Raised the columns values not appearing correct in test checking the properties files and jar at server..checking the .14 server reports have correct name value..reverting same on mail
| Time Spent | 1 day, 5 hours [ 46800 ] | 1 day, 5 hours, 30 minutes [ 48600 ] |
| Worklog Id | 278521 [ 278521 ] |
| Time Spent | 1 day, 5 hours, 30 minutes [ 48600 ] | 1 day, 7 hours, 30 minutes [ 55800 ] |
| Worklog Id | 278549 [ 278549 ] |
| Time Spent | 1 day, 7 hours, 30 minutes [ 55800 ] | 2 days, 1 hour, 30 minutes [ 63000 ] |
| Worklog Id | 278707 [ 278707 ] |
some object id in ubr report for cambium is showing blank please check , snapshot attached for your reference .
| Attachment | ubr nep report.png [ 118818 ] | |
| Attachment | ubr object id issue.png [ 118819 ] | |
| Attachment | object id blank ubr.png [ 118820 ] |
| Assignee | Priyasha Tiwari [ ptiwari ] | Srishti Kashyap [ skashyap ] |
Dear
A separate ticket LS-683 is created for the last mentioned issue
| Assignee | Srishti Kashyap [ skashyap ] | Priyasha Tiwari [ ptiwari ] |
board report the object id is not correct , should be same as the object id for UBR node report. refer the screenshot attached .
| Attachment | board report ubr.png [ 119301 ] |
| Assignee | Priyasha Tiwari [ ptiwari ] | Srishti Kashyap [ skashyap ] |
| Status | Ready for QA [ 10023 ] | QA In Progress [ 10015 ] |
| Assignee | Srishti Kashyap [ skashyap ] | Abir Messaikeh [ amessaikeh ] |
| Status | QA In Progress [ 10015 ] | Bug/s Found [ 10208 ] |
| Assignee | Abir Messaikeh [ amessaikeh ] | Srishti Kashyap [ skashyap ] |
| Status | Bug/s Found [ 10208 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
21m 9s | 1 | Abir Messaikeh | 01/Sep/25 3:39 PM | |||||
|
14d 19h 36m | 1 | Khaled Khalil | 16/Sep/25 11:15 AM | |||||
|
10s | 1 | Khaled Khalil | 16/Sep/25 11:16 AM | |||||
|
10s | 1 | Khaled Khalil | 16/Sep/25 11:16 AM | |||||
|
5d 21h 45m | 1 | Srishti Kashyap | 22/Sep/25 9:01 AM | |||||
|
20s | 1 | Srishti Kashyap | 22/Sep/25 9:01 AM | |||||
|
1d 43m | 1 | Khaled Khalil | 23/Sep/25 9:45 AM | |||||
|
2h 15m | 1 | Khaled Khalil | 23/Sep/25 12:00 PM | |||||
|
15s | 1 | Khaled Khalil | 23/Sep/25 12:00 PM | |||||
|
98d 2h 59m | 1 | Abir Messaikeh | 30/Dec/25 2:00 PM | |||||
|
42s | 1 | Abir Messaikeh | 30/Dec/25 2:00 PM | |||||
|
58d 18h 29m | 1 | Priyasha Tiwari | 27/Feb/26 8:30 AM |
|
Links Hierarchy |
 Documentation
|
As agreed we need to implement the below mentioned points.
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) –
More Clarification
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.
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)