[LS-561] OT | SubInterface available in IP Data missing in Subinterface report in NEP. Created: 07/Aug/25  Updated: 15/Oct/25  Due: 13/Aug/25  Resolved: 09/Oct/25

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

Type: Bug Priority: Normal
Reporter: Aurobinda Panda Assignee: Aurobinda Panda
Resolution: Fixed Votes: 0
Labels: MS_OT, Service_routing
Remaining Estimate: 0 minutes
Time Spent: 2 weeks, 4 days, 6 hours, 15 minutes
Original Estimate: Not Specified

Attachments: GZip Archive 2025-08-03-03.40.33_OmanTel.xml.tar.gz     JPEG File BB02401_new IP report.jpg     JPEG File BB02401_new Subinterface report.jpg     JPEG File IP Data_NEP_BBK2401.jpg     JPEG File IP Data_XML_BBK2401.jpg     JPEG File Interface report_NEP_BBK2401.jpg     JPEG File Subinteface_BB02401.JPG     JPEG File Subinteface_BB02401.JPG     JPEG File Subinterface_NEP_BBK2401.jpg    
Customer:
OMAN-Tel
Planned Start:
Planned End:
Complexity: High
Severity: Major
Product: NEP
REQUESTER: INTERNAL
Actual Start:
Date of Baselining:

 Description   

Dear Khaled Khalil,
It is found that, the Subinterfaces available in NEP IP data report is missing in NEP Subinterface report.

Due to which RAN Port information is missing in RAN logical Interface for the RAN nodes.

Please find sample Node below.
BB02401

As per IP data
10.132.70.33 255.255.254.0 10.132.70.1 BB02401 BB02401 SRanBs GETH 0/0/7/0/1.4

10.132.70.33 is assigned for Interface GETH 0/0/7/0/1.4
But as checked in Subinterface report it missing.

BB02401 SRanBs GETH 0/0/7/0/1 3 10.222.79.51 255.255.255.0
BB02401 SRanBs GETH 0/0/7/0/1 4

I have checked the XML and it is available.

SS details are shared in attachment.

 Comments   
Comment by Abir Messaikeh [ 07/Aug/25 ]

https://mobinets-my.sharepoint.com/:u:/p/mohan_rathor/EZsIqyGhw-5Fj6bAag22bikBqlqe4DvREWmasYi8nEVrFw?e=v4XJyH

Comment by Marwan Kanaan [ 13/Aug/25 ]

Dear @Aurobinda Panda,
After importing the XML locally for the first time, the problem was reproducible. We then decided to empty the version and reimport to observe the impacts. Following this, all subinterfaces received their IP addresses without any issues.
In conclusion, we implemented fixes related to saving the physical configuration. The next step is to test these changes after cleaning up the corrupted and duplicated data. Please ensure that the patch 3.7.0.1334 is applied following the cleanup process.

Best Regards,
Marwan Kanaan I Software Developer

Comment by Aurobinda Panda [ 20/Aug/25 ]

As checked for the subinterfaces on 180 the Ips are available under Subinterface now. Please check latest SS attached.

Comment by Marwan Kanaan [ 22/Aug/25 ]

Dear @Aurobinda Panda,

Regarding the issue of "SubInterface available in IP Data missing in Subinterface report in NEP", as mentioned earlier, we agreed to perform a clean-up since all data had been imported normally using a clean version.
Now, after applying the latest patch which includes multiple fixes please proceed with the import again and verify that all your changes are reflected correctly.

Best Regards,
Marwan Kanaan I Software Developer
Email: marwan.kanaan@nuiva.com I www.nuiva.c

Comment by Aurobinda Panda [ 28/Aug/25 ]

Issue will be checked post XML import on PROD.

Comment by Aurobinda Panda [ 17/Sep/25 ]

As checked, Still issue is not fixed post XML import. Check new SS

Comment by Abir Messaikeh [ 17/Sep/25 ]

Please share the last xml and server logs related to last xml import related to this topic

Comment by Marwan Kanaan [ 01/Oct/25 ]

Dears @Abir Messaikeh  and @Aurobinda Panda,

Please be informed that the identified bug has been resolved. A cleanup script is required to address the existing corrupted data entries.

@Abir, kindly coordinate with the OT team to confirm the schedule for deploying the patch, so that we can ensure the script is executed before it.

Patch NB: 3.7.0.1355

Best Regards,

Marwan Kanaan I Software Developer

Comment by Aurobinda Panda [ 09/Oct/25 ]

Issue has been resolved for sample case. But as agreed with L3, the solution of multiple import is not feasible. So L3 need to check a new solution for one time XML import.

Generated at Fri Apr 17 08:11:43 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.