Details
-
Type:
Bug
-
Status:
Closed
(View Workflow)
-
Priority:
Normal
-
Resolution: Fixed
-
Component/s: None
-
Labels:
-
Customer:OMAN-Tel
-
Complexity:High
-
Severity:Major
Description
Currently there are issues in NEP route builder algorithm when encountering a tunnel path in the route path. To solve this issue the below algorithm is proposed.
1. When encountering a routing table information withe a tunnel path the interpretation of the routing table info should be as follows.
- To reach to the specified destination network - > go to this next hop router - > Via the tunnel specified.
- Attached the routing table info for route of 4G node LM17130 in the router routing table.
2. The tunnel path can be determined from the tunnel path configuration information. By going thorough each next hop step by step using the routing table information. Attached the routing table info for the tunnel configuration information on a router in the path of node LM17130.
3. Corresponding NEP screenshots of the information's also attached.
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
- Transitions
- Trace
-
- Time Spent:
- 30 minutes
-
Data checked in Route builder report as requested by L3.
-
- Time Spent:
- 1 hour, 30 minutes
-
Issue discussed & data checked.
-
- Time Spent:
- 1 hour
-
Routing issue checked post XML import.
-
- Time Spent:
- 1 hour
-
Discussion with l2 & L3 for issue found during import.
-
- Time Spent:
- 1 hour
-
Discussion & follow up for the issue.
-
- Time Spent:
- 3 hours
-
Tunnel issue checked & discussed with team.
-
- Time Spent:
- 1 hour
-
NGN routing issue checked.
-
- Time Spent:
- 1 hour
-
Issue checked related to NGN Routing
-
- Time Spent:
- 1 hour
-
Routing issue checked & discussed with Team.
-
- Time Spent:
- 1 hour, 30 minutes
-
NGN routing checked post XML import.
-
- Time Spent:
- 4 hours
-
Data check & discussion with team.
-
- Time Spent:
- 3 hours
-
testing done & discussion with L3
-
- Time Spent:
- 3 hours
-
Data check & Ip related issues & routing issues checked.
-
- Time Spent:
- 2 hours
-
Discussion with L3 & Phy connectivity checked.
-
- Time Spent:
- 2 hours
-
Data checked & discussions done with Internal team.
-
- Time Spent:
- 4 hours
-
Internal discussion & data check in NEP.
-
- Time Spent:
- 2 hours
-
Data checked & shared with Internal team for Ips missing in NEP.
-
- Time Spent:
- 2 hours
-
validate the missing IP NEs and IP data in NEP side, with the shared sheet
-
- Time Spent:
- 2 hours, 30 minutes
-
analyze the issue from XML side
