[LS-272] NEP not checking the sub interface for IP route/ route builder Created: 10/Mar/25  Updated: 28/May/25  Due: 30/Apr/25  Resolved: 05/May/25

Status: Closed
Project: L3 Support
Component/s: NEP
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Eyob Tatek Assignee: Abir Messaikeh
Resolution: Cannot Reproduce Votes: 0
Labels: NEP, Service_routing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File 62.231.255.242.txt     Text File 62.231.255.93.txt     PNG File IP route output.png     PNG File IP route output_LB00010.png     JPEG File Source inteface in NEP.jpg     PNG File Source interface configuration.png     PNG File Source interface configuration_LB00010.png     PNG File Source interface configuration_dump_file_LB00010 .png    
Customer:
OMAN-Tel
Planned Start:
Planned End:

 Description   

While performing IP route on failed route builder cases, the IP route algorithm doesn't check the exact source interface which is the sub interface but instead it takes the interface as the source interface. Due to this it is not able to check the correct routing table and hence failing to build the route.

Attached screen shots for node BD02870 with source GW: 10.116.10.1 and destination GW: 10.238.250.2, " with main failure reason of Destination IP unreachable in route builder ".
Also attached screen shots for node LB00010 with source GW: 10.238.143.1 and destination GW: 10.238.250.54. " with main failure reason of Next Hop IP missing for Router in route builder"

 Comments   
Comment by Bessem Manita [ 09/Apr/25 ]

As discussed the issue is not reproducible on prod and .180 platforms, it seems it was a data issue.
Dear Eyob please check and confirm.

Comment by Eyob Tatek [ 05/May/25 ]

Error is not able to be reproduced, ticket can be closed

Comment by Abir Messaikeh [ 28/May/25 ]

closed - data issue

Generated at Fri Apr 17 08:11:53 EEST 2026 using JIRA 6.1.4#6159-sha1:44eaedef2e4a625c6c7183698b2468d4719c20dc.