-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
FRR 10.2 upgrade - lost static routes and bgp graceful-restart #17537
Comments
Could you show the configs before/after? |
Hi Here is the diff, from backup the day before. diff -w /root/host-cpt-ter-rs1-frr.conf frr.conf ⏎1c1
|
I upgraded two other routers, which kept their static routes, but also had the 'neighbor NNN graceful-restart' lines removed. I looked through the log files, did not find anything useful. By the time I saved this I already went and pasted back the static routes - had customers complaining. So 28x 'ip route' and 'ipv6 route' statements not in the diff above. I can't be sure all 28 went missing - but sure about at least 4. I did the 'write mem' command to create the new config file a few seconds after it started up, so I'm also not sure if that caused the problem, or if it started up without the static routes. |
Please give us not the diff, but real configs to load them and see a real case. |
Hi, can't really publish customer routing info on a public forum. Can I share the config just with you? |
Yes, you can send it to me by email or in Slack. |
Thanks. The graceful-restart issue (with peer-groups) is a known regression and it's fixed in stable/10.2, but gonna be released with 10.2.1... Checking yet regarding static routes if this is an issue from the FRR side or not. |
@SwimGeek how about static routes? Can it be somehow reproduced? |
Hi, we upgraded a 2nd switch with the same hardware to 10.2, but did not encounter the same issue. Still not sure what caused it. I guess I'll just always do a diff after upgrade going forward to see if I can spot the issue again. |
Description
In the process of upgrading from FRR 10.1.1 to 10.2 I noticed frr.conf had lost all the static routes in the config (v4 and v6). I did a diff on the old and new config files and found a few other missing items.
- ipv6 nd adv-interval-option
- ipv6 nd managed-config-flag
Version
How to reproduce
I upgraded a router, restarted FRR, then ran vtysh - then write mem - with the idea to update the config file with new FRR version number. Somewhere in this process I ended up without static routes in the newly written config file.
Expected behavior
Keep the configured static routes after an upgrade.
Actual behavior
frr.conf changed, losing static routes
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: