Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: NEP
-
Labels:
-
Customer:OMAN-Tel
-
Complexity:High
-
Severity:Critical
-
Product:NEP
-
REQUESTER:INTERNAL
Description
Dear Khaled Khlil,
Please assign a resource to check for below issue.
It is found that, hsrp IPs are not getting imported to NEP. though it is showing as imported in NEP Import network Report.
SS are attached for your reference
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 15 minutes
-
Data checked for HSRP
-
- Time Spent:
- 1 hour
-
Data checked and reverted to L3 as redundancy report is available. HSRP data checking.
-
- Time Spent:
- 1 hour
-
Latest NEP patch 3.7.0.1366 has been successfully deployed on .102 platform
-
- Time Spent:
- 3 hours
-
Debugged and identified the root cause of the issue in the redundancy table, then implemented and verified the fix
-
- Time Spent:
- 4 hours
-
querying data from the production, old, and new .180 schemas for comparison and validation purposes
-
- Time Spent:
- 30 minutes
-
Issue checked and discussed with L3.
-
- Time Spent:
- 1 hour
-
XML and IP data checked. Comment updated.
-
- Time Spent:
- 4 hours
-
I performed the initial import with debug enabled to identify the issue and noticed some routers were not imported because their router types did not exist. I connected to the production NEP to create the missing types locally, then re-imported using a clean version. Both imports completed successfully, so the issue appears to be related to the cleanup process.
-
- Time Spent:
- 2 hours
-
HSRP IP missing. Issue raised to L3.
