[LS-756] IP Not Imported For Nokia BSC Created: 27/Oct/25  Updated: 04/Nov/25  Due: 31/Oct/25  Resolved: 29/Oct/25

Status: Rejected
Project: L3 Support
Component/s: NEP
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Indrasan Yadav Assignee: Indrasan Yadav
Resolution: Cancelled Votes: 0
Labels: AI_All_incidents, Nokia_RAN_OO
Remaining Estimate: 30 minutes
Time Spent: 5 hours, 30 minutes
Original Estimate: Not Specified

Attachments: PNG File Error Snap_Nokia RAN.png     File Nokia RAN_XML.rar     PNG File Screenshot 2025-10-29 150023.png     PNG File Screenshot 2025-10-29 150220.png     PNG File XML Snippet_Nokia RAN.png    
Customer:
Ooreedo Tunisia
Planned Start:
Planned End:
Rejected By: Marwan Kanaan
Actual Start:
Date of Baselining:

 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

 Comments   
Comment by Marwan Kanaan [ 29/Oct/25 ]

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

Generated at Wed Apr 15 14:42:13 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.