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
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
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