Details
-
Type:
Bug
-
Status:
QA In Progress
(View Workflow)
-
Priority:
Normal
-
Resolution: Unresolved
-
Component/s: NEP
-
Labels:
-
Customer:Ooreedo Tunisia
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.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | 2025-07-30-05.57.49_Omantel.xml [ 115140 ] |
| Attachment | network importer report.jpg [ 115141 ] | |
| Attachment | IP data report.jpg [ 115142 ] | |
| Attachment | IP data csv.jpg [ 115143 ] |
| 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. |
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. |
| Status | Open Bug [ 10108 ] | Dev Scheduled [ 10014 ] |
| Assignee | Khaled Khalil [ kkhalil ] | Marwan Kanaan [ mkanaan ] |
-
- Time Spent:
- 4 hours
-
During debugging, I identified that certain virtual interface IPs failed to import because the interface name in the new XML did not follow the required rules that it must be either MANAGEMENT1 or MANAGEMENT2. Comparing it with a previously working XML confirmed this discrepancy. To prevent such issues, validation is added to reject corrupted XML data,and error logging is clearly indicate the reason whenever an invalid interface name is detected,ensuring the system no longer incorrectly marks invalid virtual interfaces as successfully added.
| Status | Dev Scheduled [ 10014 ] | Implementation in progress [ 10016 ] |
| Attachment | Screenshot 2025-08-21 125807.png [ 115907 ] | |
| Attachment | Screenshot 2025-08-21 130203.png [ 115908 ] |
| Status | Implementation in progress [ 10016 ] | To Be Released [ 10400 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 4 hours [ 14400 ] | |
| Worklog Id | 275123 [ 275123 ] |
| Worklog Id | 275123 [ 275123 ] |
| Status | To Be Released [ 10400 ] | Ready for QA [ 10023 ] |
| Assignee | Marwan Kanaan [ mkanaan ] | divya kaushik [ dkaushik ] |
-
- Time Spent:
- 2 hours
-
fixed the validation for the virtual interface name
| Time Spent | 4 hours [ 14400 ] | 6 hours [ 21600 ] |
| Worklog Id | 276508 [ 276508 ] |
| Status | Ready for QA [ 10023 ] | QA In Progress [ 10015 ] |
| Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
|---|---|---|---|---|---|---|---|---|---|
|
8d 16h 20m | 1 | Hassan Abdine | 20/Aug/25 5:01 AM | |||||
|
1d 2h 24m | 1 | Marwan Kanaan | 21/Aug/25 7:25 AM | |||||
|
2h 8m | 1 | Marwan Kanaan | 21/Aug/25 9:34 AM | |||||
|
21m 28s | 1 | Khaled Khalil | 21/Aug/25 9:55 AM | |||||
|
32d 19h 24m | 1 | divya kaushik | 23/Sep/25 5:19 AM |
|
Links Hierarchy |
 Documentation
|
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