[RouteOrch] Publish route state for route to Loopback interface #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Route to loopback interface is not advertised to peers when FIB suppression is enabled.
Route is queued:
```
admin@sonic:~$ show ipv6 route |grep q
> - selected route, * - FIB route, q - queued route, r - rejected route
S>qfc00:1::/64 [1/0] is directly connected, Loopback0, 00:02:00
```
With this change:
```
admin@sonic:~$ show ipv6 route | grep q
> - selected route, * - FIB route, q - queued route, r - rejected route
```
The proper way would be to program route to HW and then publish the
route state, however to keep the existing behaviour this W/A is proposed
until a final solution.
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
volodymyrsamotiy
approved these changes
Jan 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I did
Publish exception route state to APPL_STATE_DB.
Why I did it
Route to loopback interface is not advertised to peers when FIB suppression is enabled.
The proper way would be to program route to HW and then publish the route state, however to keep the existing behaviour this W/A is proposed until a final solution.
How I verified it
Route is queued:
With this change:
Details if related