Skip to content
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

[multi-asic] BBR support on internal-peers for multi-asic platfroms. #6848

Merged
merged 2 commits into from
Feb 26, 2021

Conversation

abdosi
Copy link
Contributor

@abdosi abdosi commented Feb 23, 2021

What I did:
Enable BBR config allowas-in 1 for internal peers

Why I did:
To advertise BBR routes learnt via e-BGP peer in one asic/namespace to another iBGP asic/namespace via Route Reflector.

How I Verify:

Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
@abdosi abdosi requested a review from lguohan as a code owner February 23, 2021 00:39
Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
@abdosi abdosi merged commit a520cec into sonic-net:master Feb 26, 2021
@abdosi abdosi deleted the bbr branch February 26, 2021 07:15
abdosi added a commit that referenced this pull request Mar 2, 2021
…6848)

Enable BBR config allowas-in 1 for internal peers

Why I did:
To advertise BBR routes learnt via e-BGP peer in one asic/namespace to another iBGP asic/namespace via Route Reflector.
qiluo-msft pushed a commit that referenced this pull request May 24, 2021
…6848)

Enable BBR config allowas-in 1 for internal peers

Why I did:
To advertise BBR routes learnt via e-BGP peer in one asic/namespace to another iBGP asic/namespace via Route Reflector.
carl-nokia pushed a commit to carl-nokia/sonic-buildimage that referenced this pull request Aug 7, 2021
…onic-net#6848)

Enable BBR config allowas-in 1 for internal peers

Why I did:
To advertise BBR routes learnt via e-BGP peer in one asic/namespace to another iBGP asic/namespace via Route Reflector.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants