forked from FRRouting/frr
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
sharpd, lib: add nexthop-group child group support
The hierarchical nexthop groups need to be tested at protocol level: the SHARP daemon must be adapted to configure nexthop groups in ZEBRA. Each modified nexthop group must be notified to the parent nexthop groups that use that nexthop group. The installation of parent nexthop groups must follow its child groups. The removal of child groups must follow the removal of its parent nexthop-group. - A callback registration mechanism is added in the nexthop-group library to notify parent nexthop groups which own a given child group. - The configuration order is managed by SHARP - SHARP uses the NHG_GROUP_ADD ZAPI message. There are no checks on the number of ECMP nexthops in a child group, knowing that from SHARP perspective, one child group equals one nexthop. Signed-off-by: Philippe Guibert <[email protected]>
- Loading branch information
1 parent
2f2f8f7
commit 95e25d7
Showing
6 changed files
with
292 additions
and
24 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.