Details
-
Type:
Bug
-
Status:
Rejected
(View Workflow)
-
Priority:
Normal
-
Resolution: Cancelled
-
Component/s: NEP
-
Labels:
-
Customer:Ooreedo Tunisia
Description
Dear @Khaled Khalil,
Could you please assign a NEP DEV resource to investigate the issue described below?
Details:
• XML Files: 2025-10-03-10.37.53_Ooredoo (attached on JIRA)
• Import Date: 24-Oct-2025
• Platform: .102
• Server Logs: I will attach on JIRA, once received from Integration as they are facing some issue on BO machine.
Issue Summary:
During XML import, 10 IP addresses from 2 BSCs were not imported into NEP, even though the parent nodes were successfully imported. The system generated an error (refer to the Error Report section), but upon reviewing the XML, I did not find any issue in the file.
Attachments:
Error Report
SS attached
XML Snippet
SS attached
Kindly review this case and assign a developer to check and resolve the issue.
Thank you
Indrasan
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Gantt Options | Milestone (set to milestone: having a due date but zero effort) | |
| Planned Start | 2025-10-31 24:00 (milestone: set planned start date to due date) | |
| Planned End | 2025-10-31 24:00 (milestone: set planned end date to due date) |
-
- Time Spent:
- 1 hour
-
During data validation of Nokia RAN, found the gap in IP & troubleshoot the same and raised the JIRA for this.
| Component/s | NEP [ 16200 ] |
| Assignee | Khaled Khalil [ kkhalil ] | Marwan Kanaan [ mkanaan ] |
| Description |
Dear @Khaled Khalil,
Could you please assign a NEP DEV resource to investigate the issue described below? Details: • XML Files: 2025-10-03-10.37.53_Ooredoo (attached on JIRA) • Import Date: 24-Oct-2025 • Platform: .102 • Server Logs: I will attach on JIRA, once received from Integration as they are facing some issue on BO machine. Issue Summary: During XML import, 10 IP addresses from 2 BSCs were not imported into NEP, even though the parent nodes were successfully imported. The system generated an error (refer to the Error Report section), but upon reviewing the XML, I did not find any issue in the file. Attachments: Error Report SS attached XML Snippet SS attached Kindly review this case and assign a developer to check and resolve the issue. Thank you Indrasan |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 1 hour [ 3600 ] | |
| Worklog Id | 281929 [ 281929 ] |
| Baseline Start | 2025-10-31 24:00 (set baseline based of initial work logging) | |
| Baseline End | 2025-10-31 24:00 (set baseline based of initial work logging) |
-
- Time Spent:
- 4 hours
-
Imported the same XML file to reproduce the reported issue. Analyzed the code logic and identified that the loopback nodeId is referencing the node name instead of the BSC object ID, which leads to a null node exception during processing.
| Status | Open Bug [ 10108 ] | Rejected [ 10100 ] |
| Assignee | Marwan Kanaan [ mkanaan ] | Indrasan Yadav [ iyadav ] |
| Resolution | Cancelled [ 10100 ] |
| Attachment | Screenshot 2025-10-29 150023.png [ 120816 ] | |
| Attachment | Screenshot 2025-10-29 150220.png [ 120817 ] |
| Time Spent | 1 hour [ 3600 ] | 5 hours [ 18000 ] |
| Worklog Id | 282068 [ 282068 ] |
-
- Time Spent:
- 30 minutes
-
Review the email feedback which received from @Marwan & raised to #Sandya to fix the same with in JIRA
OT-84after discussion done with her to explain the same.
| Time Spent | 5 hours [ 18000 ] | 6 hours [ 21600 ] |
| Worklog Id | 282559 [ 282559 ] |
| Worklog Id | 282559 [ 282559 ] |
| Remaining Estimate | 0 minutes [ 0 ] | 30 minutes [ 1800 ] |
| Time Spent | 6 hours [ 21600 ] | 5 hours, 30 minutes [ 19800 ] |
| Worklog Id | 282559 [ 282559 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
1d 22h 21m | 1 | Marwan Kanaan | 29/Oct/25 1:16 PM |
|
Links Hierarchy |
 Documentation
|
Dear @Indrasan Yadav,
Kindly note that while debugging the code logic and reviewing the XML, I found the following:
The BSC node names are listed as BSCMNB06, and their corresponding object IDs are BSC-415338.
ss
However, in the loopback interfaces, the nodeId is referring to the node name instead of the object ID, which should not be the case. This incorrect reference will be avoided in the code, as it can lead to a null node issue during processing.
ss
The same behavior is also observed in the other BSC nodes.
Best Regards,
Marwan Kanaan I Software Developer