-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 PIC HLD #1493
base: master
Are you sure you want to change the base?
BGP PIC HLD #1493
Conversation
eddieruan-alibaba
commented
Oct 9, 2023
•
edited
Loading
edited
PR | Status | Submitters |
---|---|---|
[preview]Add PIC support in the srv6 VPN scenario. #16879 | Zice, Alibaba | |
zebra: add an approach to keep the NHG ID unchanged for recursive rou… #16693 | xingrenwai , Accton |
doc/bgp_pic/bgp_pic.md
Outdated
1. In the 'zebra' component: | ||
- Introduce a new Next Hop Group (PIC-NHG) specifically for the FORWARDING function. This NHG will serve as the shareable NHG in hardware. | ||
- When a BGP next hop becomes unavailable, zebra will first update the new FORWARDING-ONLY NHG before BGP convergence takes place. | ||
- If changes occur in the IGP NHG and these changes do not affect the reachability of individual members within the BGP NHG, there is no need to update the BGP NHG. |
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.
I think you should specify what you mean by "these changes do not affect the reachability ...".
I have 2 use cases in mind:
- UCMP - weighted extended community",
- route-map configured that look for the IGP metric, will be ignored.
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.
Let me update the wording. I mean the case BGP NH reachability would not be changed when IGP NHG updates. zebra needs to check BGP NH's reachability and skip BGP NHG update if all members's reachability is not changed.
Currently, the update is reported back to BGP and trigger BGP update even BGP NH's reachability is unchanged.
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.
thanks Eddie
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.
Some questions (to clarify)
more will come before next Tuesday (for frr meeting).
thanks.
Can you clarify the use case: is it for ebgp single hop and multi hop ?
we use eBGP for underlay peering and MP-BGP for overlay peering with remote PE. |
Suggested by FRR folks, I raised FRRouting/frr#14703 for tracking the discussions in FRR community. |
HLD's direct link is https://github.com/eddieruan-alibaba/SONiC/blob/eruan-pic/doc/bgp_pic/bgp_pic.md |
7e34079
to
9162952
Compare
5f3f821
to
2dbff75
Compare
The new location is moved to doc/pic/ https://github.com/eddieruan-alibaba/SONiC/blob/eruan-pic/doc/pic/bgp_pic_edge.md |
d839010
to
2c6d5ac
Compare
This PR contains two HLD now
|
@eddieruan-alibaba can you please add the code PRs to this HLD PR? Thanks. |