-
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
[9.2-dev] staticd/mgmtd doesn't load static routes on OS booting in a special case with more than 11 VRFs in system and wrong networking config #15267
Comments
To solve the booting issue I've created a service like this: /etc/systemd/system/frr-static-routes-fix.service:
|
Hi. Would be great if you could get and test the branch from this PR: #15286. I think it should fix your problem. |
Hi @idryzhov I will try to patch FRR with that PR and I will give a try. Thanks! |
@idryzhov I compiled today's git FRR with your patch. I had to change a little bit the patch to be able to applied on the latest dev. Looks like is working now. |
Perfect. Thanks for the testing! |
I will test on all devices tomorrow |
Describe the bug
When the system is booting up and you have 12 or more VRFs defined in system and in system networking you have a wrong configuration, FRRouting doesn't load static routes and are missing from the running configuration!
I've notice this behavior from December on 4 PC and 1 VM running Debian 12 or 13 with latest development FRR. All of them have the same behavior.
To Reproduce
Networking configuration:
red10 and blue10 VRFs are not existing in system.
Test with 12 VRFs:
Output of networking.service and frr.service:
FRR running config:
Test with 11 VRFs:
Output of networking.service and frr.service:
FRR running config:
Saved config that should be loaded at boot:
Expected behavior
All static routes should be installed on boot.
To fix the issue I have to run
vtysh -d mgmtd -f /etc/frr/frr.conf
after booting.Screenshots
Versions
Additional context
The text was updated successfully, but these errors were encountered: