Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ipv6 /64 route not getting advertised to Peer #17638

Closed
abdosi opened this issue Dec 30, 2023 · 3 comments · Fixed by sonic-net/sonic-swss#3013
Closed

Ipv6 /64 route not getting advertised to Peer #17638

abdosi opened this issue Dec 30, 2023 · 3 comments · Fixed by sonic-net/sonic-swss#3013
Assignees
Labels
Issue for 202305 MSFT P0 Priority of the issue Triaged this issue has been triaged

Comments

@abdosi
Copy link
Contributor

abdosi commented Dec 30, 2023

on master and 202305

For 202205 behavior is fine where Static Route is not marked as queued by FRR .

On 202305 and master route is maeked as queued. This is because of fib suppression feature enable from 202305 onwards.

str3-xxxx-lc3-1# show ipv6 route fc00:12::/64
Routing entry for fc00:12::/64
Known via "static", distance 1, metric 0, best
Last update 01w1d19h ago

  • directly connected, Loopback0, weight 1

str3-xxxx-lc3-1# show ipv6 route static
S>* fc00:12::/64 [1/0] is directly connected, Loopback0, weight 1, 01w1d19h

@abdosi abdosi added Issue for 202305 P0 Priority of the issue labels Dec 30, 2023
@abdosi
Copy link
Contributor Author

abdosi commented Dec 30, 2023

Solution for 202305: Fib suppression feature is going to disable so we should not see this isse. PR will be open by @stepanblyschak / @dgsudharsan for viz.

Solution for master is being looked into by @prsunny

@stepanblyschak
Copy link
Collaborator

@abdosi Isn't it the same as #15709?

@judyjoseph judyjoseph added Triaged this issue has been triaged MSFT labels Jan 3, 2024
@rlhui
Copy link
Contributor

rlhui commented Jan 9, 2024

@abdosi Isn't it the same as #15709?

@stepanblyschak don't think it's the same issue as #15709 was closed in July. nonetheless, can we use this new one to track the current issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue for 202305 MSFT P0 Priority of the issue Triaged this issue has been triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants