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.

Sign up for GitHub

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

Jump to bottom

Verify TSA/TSB works across iBGP for chasiss for both IPv4 and Ipv6 #8170

Closed
abdosi opened this issue Apr 27, 2023 · 1 comment
Closed

Verify TSA/TSB works across iBGP for chasiss for both IPv4 and Ipv6 #8170

abdosi opened this issue Apr 27, 2023 · 1 comment
Assignees
@tjchadaga
Labels
Test gap Triaged

Comments

@abdosi
Copy link
Contributor

abdosi commented Apr 27, 2023

Description:

Verify TSA/TSB works across iBGP for chasiss for both IPv4 and Ipv6
@abdosi abdosi mentioned this issue Apr 27, 2023
Merged
@yxieca yxieca added the Triaged label May 3, 2023
lguohan pushed a commit to sonic-net/sonic-buildimage that referenced this issue May 5, 2023
@abdosi
[bgp/TSA]: Fixed the internal peer route-map policy (#14804)
9b8b4e6 
What I did:
In FRR command update source <interface-name> is not at address-family level. Because of this
internal peer route-map for ipv6 were getting applied to ipv4 address family. As a result
TSA over iBGP for Ipv6 was not getting applied.

How I verify:

Manual Verification of TSA over both ipv4 and ipv6 after fix works fine.
Updated UT for this.

Added sonic-mgmt test gap: sonic-net/sonic-mgmt#8170

Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
@mssonicbld mssonicbld mentioned this issue May 17, 2023
Merged
mssonicbld pushed a commit to mssonicbld/sonic-buildimage that referenced this issue May 17, 2023
@abdosi @mssonicbld
[bgp/TSA]: Fixed the internal peer route-map policy (sonic-net#14804)
b313108 
What I did:
In FRR command update source <interface-name> is not at address-family level. Because of this
internal peer route-map for ipv6 were getting applied to ipv4 address family. As a result
TSA over iBGP for Ipv6 was not getting applied.

How I verify:

Manual Verification of TSA over both ipv4 and ipv6 after fix works fine.
Updated UT for this.

Added sonic-mgmt test gap: sonic-net/sonic-mgmt#8170

Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
mssonicbld pushed a commit to sonic-net/sonic-buildimage that referenced this issue May 18, 2023
@abdosi @mssonicbld
[bgp/TSA]: Fixed the internal peer route-map policy (#14804)
4f0f0e0 
What I did:
In FRR command update source <interface-name> is not at address-family level. Because of this
internal peer route-map for ipv6 were getting applied to ipv4 address family. As a result
TSA over iBGP for Ipv6 was not getting applied.

How I verify:

Manual Verification of TSA over both ipv4 and ipv6 after fix works fine.
Updated UT for this.

Added sonic-mgmt test gap: sonic-net/sonic-mgmt#8170

Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>
@abdosi
Copy link
Contributor Author

abdosi commented Dec 5, 2024

Done via #10239

@abdosi abdosi closed this as completed Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tjchadaga tjchadaga

Labels
Test gap Triaged
Projects
SONiC Chassis
Status: Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@yxieca @abdosi @tjchadaga