[LS-565] || virtual interface IP is not importing in NEP|| Created: 11/Aug/25  Updated: 23/Sep/25  Due: 14/Aug/25

Status: QA In Progress
Project: L3 Support
Component/s: NEP
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: divya kaushik Assignee: divya kaushik
Resolution: Unresolved Votes: 0
Labels: AI_All_incidents
Remaining Estimate: 0 minutes
Time Spent: 6 hours
Original Estimate: Not Specified

Attachments: XML File 2025-07-30-05.57.49_Omantel.xml     JPEG File IP data csv.jpg     JPEG File IP data report.jpg     PNG File Screenshot 2025-08-21 125807.png     PNG File Screenshot 2025-08-21 130203.png     JPEG File network importer report.jpg    
Customer:
Ooreedo Tunisia
Actual Start:

 Description   

Hi Team,

We have identified an issue where the virtual interface IP is not being parsed in NEP, even though it is present in the XML. Additionally, there are no related errors shown in NEP. Please investigate and revert back asap.

Note:- xml and related screen shot attached.

 Comments   
Comment by Marwan Kanaan [ 21/Aug/25 ]

Dear @Divya Kaushik,

The issue with the virtual interface IP not being imported was caused by incorrect XML data for the virtual interface.

"ScreenShot attatched"

Specifically, the interface name must be MANAGEMENT1 or MANAGEMENT2.
Please ensure that any incorrect naming in the XML is corrected accordingly.

"ScreenShot attatched"

Additionally, even when this problem exists, the Network Reports Importer currently shows the interface as successfully added to NEP. The upcoming patch 3.7.0.1341 will address this by preventing the saving  and displaying the appropriate error message if the naming is incorrect.

Thank you for your attention to this matter.

Best Regards,
Marwan Kanaan I Software Developer

Generated at Fri Apr 17 10:34:00 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.