chore: update announce routes script to match T2#18719
Merged
bingwang-ms merged 1 commit intosonic-net:masterfrom Jun 3, 2025
Merged
chore: update announce routes script to match T2#18719bingwang-ms merged 1 commit intosonic-net:masterfrom
bingwang-ms merged 1 commit intosonic-net:masterfrom
Conversation
Signed-off-by: Austin Pham <[email protected]>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
bingwang-ms
approved these changes
Jun 3, 2025
mssonicbld
pushed a commit
to mssonicbld/sonic-mgmt
that referenced
this pull request
Jun 4, 2025
Signed-off-by: Austin Pham <[email protected]>
Collaborator
|
Cherry-pick PR to 202505: #18784 |
11 tasks
mssonicbld
pushed a commit
that referenced
this pull request
Jun 4, 2025
Signed-off-by: Austin Pham <[email protected]>
mssonicbld
added
Included in 202505 branch
and removed
Created PR to 202505 branch
labels
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
Signed-off-by: Austin Pham <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Guy Shemesh <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
Signed-off-by: Austin Pham <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Guy Shemesh <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
Signed-off-by: Austin Pham <[email protected]> Signed-off-by: Yael Tzur <[email protected]>
12 tasks
12 tasks
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
Signed-off-by: Austin Pham <[email protected]>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Currently T2 announce route script are publishing 32 routes x 3 for 3 groups of VM to T1. I.e:
Since LT1 have 110 T1, we will use another 192.171.x.x (32 routes) to satisfy the requirement
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Add more routing to match with current T2 setup
How did you do it?
Broadcast the following sequentially in 4 groups of 110 VM:
The last group of 110 will broadcast 14 routes of 192.171.x.x
How did you verify/test it?
Verify on LT2 device
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation