You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
On R5:
On R1:
On R2:
The text was updated successfully, but these errors were encountered:
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
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:
On R5:
On R1:
On R2:
The text was updated successfully, but these errors were encountered: