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

Datas residue in OSPF Segment Routing database #15031

Closed
huangyl-git opened this issue Dec 15, 2023 · 2 comments
Closed

Datas residue in OSPF Segment Routing database #15031

huangyl-git opened this issue Dec 15, 2023 · 2 comments
Assignees
Labels

Comments

@huangyl-git
Copy link

huangyl-git commented Dec 15, 2023

image

Operations:
ip set link down eth45 which r4 to r5, then show ip ospf database segment-routing on r1/r2/r4/r5,data residued on them.
After the link is set Up again, the sr db generates duplicate data.

The red box below is the residual data!

On R4:
image

On R5:
image

On R1:
image

On R2:
image

@huangyl-git huangyl-git added the triage Needs further investigation label Dec 15, 2023
@odd22 odd22 added the ospf label Dec 19, 2023
@odd22
Copy link
Member

odd22 commented Dec 19, 2023

Hello,

This is depends greatly from how you interconnect the 2 routers. If you use a switch between them (I'm pretty sure you do it like that), r5 is not seeing its interface eth54 down because it is still connected to the intermediate switch. Thus, it is normal that r5 continues to advertise adjacency sid.

However, I also discover that r5 should detect that the OSPF neighbor r4 is no more reachable through eth45, and thus stop flooding the adjacency SID for eth54. I corrected the problem with #15026 which has been merged in master.

Can you try 2 things:
1/ shutdown also eth54 to verify that SR is behave normally i.e. adjacency SID for eth54 are not more flood by r5
2/ redo the same test with latest master which incorporate the fix mention above

@odd22 odd22 removed the triage Needs further investigation label Dec 19, 2023
@odd22 odd22 self-assigned this Dec 19, 2023
@huangyl-git
Copy link
Author

15026 solves this problem

@odd22 odd22 closed this as completed Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants