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
-
- 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.
-
- Time Spent:
- 2 hours
-
fixed the validation for the virtual interface name
