[topo][routes] Add support to announces different route set for t0 topo in announce_routes#19041
Merged
Blueve merged 7 commits intosonic-net:masterfrom Jun 19, 2025
Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
yaqiangz
changed the title
yaqiangz
changed the title
w1nda
reviewed
Jun 17, 2025
w1nda
approved these changes
Jun 17, 2025
Janetxxx
approved these changes
Jun 17, 2025
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
w1nda
approved these changes
Jun 17, 2025
11 tasks
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Blueve
approved these changes
Jun 18, 2025
Blueve
pushed a commit
that referenced
this pull request
Jun 19, 2025
…ts (#19058) What is the motivation for this PR? After adding announce different routes set by #19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests
mssonicbld
pushed a commit
that referenced
this pull request
Jul 3, 2025
What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. #19117 #19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests
nissampa
pushed a commit
to nissampa/sonic-mgmt_dpu_test
that referenced
this pull request
Aug 7, 2025
…ts (sonic-net#19058) What is the motivation for this PR? After adding announce different routes set by sonic-net#19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests
nissampa
pushed a commit
to nissampa/sonic-mgmt_dpu_test
that referenced
this pull request
Aug 7, 2025
…po in announce_routes (sonic-net#19041) What is the motivation for this PR? In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors How did you do it? Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2 How did you verify/test it? Announce routes
nissampa
pushed a commit
to nissampa/sonic-mgmt_dpu_test
that referenced
this pull request
Aug 7, 2025
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests
ashutosh-agrawal
pushed a commit
to ashutosh-agrawal/sonic-mgmt
that referenced
this pull request
Aug 14, 2025
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests
vidyac86
pushed a commit
to vidyac86/sonic-mgmt
that referenced
this pull request
Oct 23, 2025
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
…ts (sonic-net#19058) What is the motivation for this PR? After adding announce different routes set by sonic-net#19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
…po in announce_routes (sonic-net#19041) What is the motivation for this PR? In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors How did you do it? Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2 How did you verify/test it? Announce routes Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…ts (sonic-net#19058) What is the motivation for this PR? After adding announce different routes set by sonic-net#19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…po in announce_routes (sonic-net#19041) What is the motivation for this PR? In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors How did you do it? Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2 How did you verify/test it? Announce routes Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…ts (sonic-net#19058) What is the motivation for this PR? After adding announce different routes set by sonic-net#19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…po in announce_routes (sonic-net#19041) What is the motivation for this PR? In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors How did you do it? Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2 How did you verify/test it? Announce routes Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…ts (sonic-net#19058) What is the motivation for this PR? After adding announce different routes set by sonic-net#19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…po in announce_routes (sonic-net#19041) What is the motivation for this PR? In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors How did you do it? Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2 How did you verify/test it? Announce routes Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
…ts (sonic-net#19058) What is the motivation for this PR? After adding announce different routes set by sonic-net#19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
…po in announce_routes (sonic-net#19041) What is the motivation for this PR? In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors How did you do it? Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2 How did you verify/test it? Announce routes
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…ts (sonic-net#19058) What is the motivation for this PR? After adding announce different routes set by sonic-net#19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…po in announce_routes (sonic-net#19041) What is the motivation for this PR? In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors How did you do it? Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2 How did you verify/test it? Announce routes Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
…ts (sonic-net#19058) What is the motivation for this PR? After adding announce different routes set by sonic-net#19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests Signed-off-by: Yael Tzur <ytzur@nvidia.com>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
…po in announce_routes (sonic-net#19041) What is the motivation for this PR? In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors How did you do it? Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2 How did you verify/test it? Announce routes Signed-off-by: Yael Tzur <ytzur@nvidia.com>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests Signed-off-by: Yael Tzur <ytzur@nvidia.com>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
…ts (sonic-net#19058) What is the motivation for this PR? After adding announce different routes set by sonic-net#19041, test_ipv6_bgp_scale need to be updated to support it How did you do it? For test_sessions_flapping and test_device_unisolation, modify the function to get ecmp routes For test_nexthop_group_member_scale: 2.1 Modify the function to get ecmp routes 2.2 Add support to specify flap neighbor count 2.3 Sample: To be noticed that the parameter is to specify neighbors' number to withdraw one route in test_nexthop_group_member_scale. In this test, we would withdraw 1 route from number of neighbors, the nexthop group member would be increased with the increasing with neighbors' number withdraw routes. Due to hw limitaion in some platform, the blast of nexthop group members would cause swss crash. Hence we add such parameter to limit the number of neighbors who withdraw routes ./run_tests.sh -i ../ansible/st,../ansible/veos -n testbed -u -m individual -e --disable_loganalyzer -e --skip_sanity -c bgp/test_ipv6_bgp_scale.py -e --max_flap_neighbor_number=190 How did you verify/test it? Run tests
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
…po in announce_routes (sonic-net#19041) What is the motivation for this PR? In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors How did you do it? Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2 How did you verify/test it? Announce routes
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
…19340) What is the motivation for this PR? Below PRs added support to advertise different route sets from BGP neighbors for T0 / T1, it's based on vm index. But loading dict from yml cannot guarantee the sort always be the same. If we re-announce routes or withdraw routes after order changing, the result would be incorrect. sonic-net#19117 sonic-net#19041 How did you do it? Add sorted in vm index to make sure order of vm dict would always be the same How did you verify/test it? Run tests
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
5 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:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
In t0-isolated-d2u510s2 topo, we need announce different route set to bgp neighbors
How did you do it?
Add support in announce_routes.py and modify topo file of t0-isolated-d2u510s2
How did you verify/test it?
Announce routes
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation