[LS-13] NEP route builder algorithm issues when encountering a tunnel interface. Created: 25/Nov/24 Updated: 18/Aug/25 Due: 30/Apr/25 Resolved: 07/Jul/25 |
|
| Status: | Closed |
| Project: | L3 Support |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Normal |
| Reporter: | Eyob Tatek | Assignee: | Aurobinda Panda |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | NEP, Service_routing | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 4 days, 6 hours | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Customer: |
OMAN-Tel
|
| Planned Start: | |
| Planned End: | |
| Complexity: | High |
| Severity: | Major |
| Actual Start: | |
| Date of Baselining: |
| 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.
|
| Comments |
| Comment by Bessem Manita [ 06/May/25 ] |
|
| Comment by Bessem Manita [ 06/May/25 ] |
|
for Tunnel, it's data issue , IP 62.231.253.177 is not configured on the right interface |
| Comment by Anonymous [ 04/Jun/25 ] |
|
LM17130 - is isolated now. Awaiting to close it if we see it is fully fixed |
| Comment by Bessem Manita [ 01/Jul/25 ] |
|
Release 3.7.0.1315 – Additional Fix Core RB: Automatically create a virtual link if the expected link is not found during processing. |
| Comment by Bessem Manita [ 01/Jul/25 ] |
|
Release 3.7.0.1312 – Additional Fix Tunnel Build: set source and destination nodes for virtual links during tunnel creation. |