-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[BGP] support BGP pending FIB suppression #12853
[BGP] support BGP pending FIB suppression #12853
Conversation
As part of these changes: - Switch to dplane_fpm_nl zebra plugin from old fpm plugin which is not supported anymore - Remove stale patches for old fpm plugin and add similar patches for dplane_fpm_nl - FRR patch backport from 8.4 to add support for fpm dataplane feedback - Templates are updated to read new feature configuration and configure FRR accordingly - YANG models updates to reflect new configuration Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
This reverts commit 735ab84.
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
FRR PR - FRRouting/frr#13086 |
/azp run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stepanblyschak could you add the testcase link or test plan for sonic-mgmt of this feature?
src/sonic-frr/patch/0016-zebra-Add-zrouter.asic_notification_nexthop_control.patch
Show resolved
Hide resolved
@StormLiangMS Test Plan sonic-net/sonic-mgmt#7475 |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
/azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
This reverts commit 79a21ce. DEPENDS ON: sonic-net/sonic-buildimage#12853 What I did Reverted changes back How I did it Reverted changes back How to verify it UT
…eboot Due to sonic-net/sonic-buildimage#12853, IPv6 BGP is partially broken, where some IPv6 BGP prefixes aren't advertised up to T1 neighbors. In an effort to get the warm reboot PR checker re-enabled, disable checking the IPv6 BGP routing for now. Once that PR is either fixed or reverted, revert this PR. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
…eboot (#8735) * Temporarily disable checking IPv6 BGP routing on neighbors for warm-reboot Due to sonic-net/sonic-buildimage#12853, IPv6 BGP is partially broken, where some IPv6 BGP prefixes aren't advertised up to T1 neighbors. In an effort to get the warm reboot PR checker re-enabled, disable checking the IPv6 BGP routing for now. Once that PR is either fixed or reverted, revert this PR. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Add todo comment Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> --------- Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
This reverts commit 79a21ce. DEPENDS ON: sonic-net/sonic-buildimage#12853 What I did Reverted changes back How I did it Reverted changes back How to verify it UT
…eboot (sonic-net#8735) * Temporarily disable checking IPv6 BGP routing on neighbors for warm-reboot Due to sonic-net/sonic-buildimage#12853, IPv6 BGP is partially broken, where some IPv6 BGP prefixes aren't advertised up to T1 neighbors. In an effort to get the warm reboot PR checker re-enabled, disable checking the IPv6 BGP routing for now. Once that PR is either fixed or reverted, revert this PR. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Add todo comment Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> --------- Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
…eboot (sonic-net#8735) * Temporarily disable checking IPv6 BGP routing on neighbors for warm-reboot Due to sonic-net/sonic-buildimage#12853, IPv6 BGP is partially broken, where some IPv6 BGP prefixes aren't advertised up to T1 neighbors. In an effort to get the warm reboot PR checker re-enabled, disable checking the IPv6 BGP routing for now. Once that PR is either fixed or reverted, revert this PR. Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> * Add todo comment Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com> --------- Signed-off-by: Saikrishna Arcot <sarcot@microsoft.com>
Why I did it BGP pending FIB suppression is introduced in #12853, hence updating the YANG model. Work item tracking Microsoft ADO (number only): 28398135 How I did it Added a new field 'suppress-fib-pending' in the DEVICE_METADATA YANG model table. Added UT for YANG model changes. How to verify it Run PR tests. Apply empty.json file to verify: admin@str2-7050cx3-acs-02:~$ sudo config apply-patch empty.json Patch Applier: Patch application starting. Patch Applier: Patch: [] Patch Applier: Getting current config db. Patch Applier: Simulating the target full config after applying the patch. Patch Applier: Validating all JsonPatch operations are permitted on the specified fields Patch Applier: Validating target config does not have empty tables, since they do not show up in ConfigDb. Patch Applier: Sorting patch updates. Patch Applier: The patch was converted into 0 changes. Patch Applier: Applying 0 changes in order. Patch Applier: Verifying patch updates are reflected on ConfigDB. Patch Applier: Patch application completed. Patch applied successfully. admin@str2-7050cx3-acs-02:~$ Signed-off-by: zitingguo-ms zitingguo@microsoft.com
Signed-off-by: Stepan Blyschak stepanb@nvidia.com
DEPENDS: #12852
Why I did it
To support BGP pending FIB suppression.
How I did it
I backported patches from FRR 8.4 feature that allows communicating ASIC route status back to FRR.
Also, added a new field in DEVICE_METADATA YANG model table. Added UT for YANG model changes.
How to verify it
Run on the switch.
Which release branch to backport (provide reason below if selected)
Description for the changelog
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)