staticd: Install known nexthops upon connection with zebra#18367
Merged
Jafaral merged 1 commit intoFRRouting:masterfrom Mar 12, 2025
Merged
staticd: Install known nexthops upon connection with zebra#18367Jafaral merged 1 commit intoFRRouting:masterfrom
Jafaral merged 1 commit intoFRRouting:masterfrom
Conversation
CI tests are showing cases where staticd is connecting to zebra after config is read in and the nexthops are never being registered w/ zebra: 2025/03/11 15:39:44 STATIC: [T83RR-8SM5G] staticd 10.4-dev starting: vty@2616 2025/03/11 15:39:45 STATIC: [GH3PB-C7X4Y] Static Route to 13.13.13.13/32 not installed currently because dependent config not fully available 2025/03/11 15:39:45 STATIC: [RHJK1-M5FAR] static_zebra_nht_register: Failure to send nexthop 1.1.1.2/32 for 11.11.11.11/32 to zebra 2025/03/11 15:39:45 STATIC: [M7Q4P-46WDR] vty[14]@> enable Zebra shows connection time as: 2025/03/11 15:39:45.933343 ZEBRA: [V98V0-MTWPF] client 5 says hello and bids fair to announce only static routes vrf=0 As a result staticd never installs the route because it has no nexthop tracking to say that the route could be installed. Modify staticd on startup to go through it's nexthops and dump them to zebra to allow the staticd state machine to get to work. Signed-off-by: Donald Sharp <[email protected]>
Jafaral
approved these changes
Mar 12, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CI tests are showing cases where staticd is connecting to zebra after config is read in and the nexthops are never being registered w/ zebra:
2025/03/11 15:39:44 STATIC: [T83RR-8SM5G] staticd 10.4-dev starting: vty@2616
2025/03/11 15:39:45 STATIC: [GH3PB-C7X4Y] Static Route to 13.13.13.13/32 not installed currently because dependent config not fully available
2025/03/11 15:39:45 STATIC: [RHJK1-M5FAR] static_zebra_nht_register: Failure to send nexthop 1.1.1.2/32 for 11.11.11.11/32 to zebra
2025/03/11 15:39:45 STATIC: [M7Q4P-46WDR] vty[14]@> enable
Zebra shows connection time as:
2025/03/11 15:39:45.933343 ZEBRA: [V98V0-MTWPF] client 5 says hello and bids fair to announce only static routes vrf=0
As a result staticd never installs the route because it has no nexthop tracking to say that the route could be installed.
Modify staticd on startup to go through it's nexthops and dump them to zebra to allow the staticd state machine to get to work.