T2: Snappi Based Route Convergence Test Changes #16337
Open
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:
T2 Snappi based automation testcases, currently didnt have Different types of upstream neighbors support.
As part of this PR,
Type of change
Back port request
Approach
What is the motivation for this PR?
T2 Snappi based automation testcases, currently didnt have Different types of upstream neighbors support.
How did you do it?
Different upstream neighbors support is added. This also covers different route policies on different types of upstream neighbors
How did you verify/test it?
Ran the testcases locally and captured the results.
Any platform specific information?
NA
Supported testbed topology if it's a new test case?
Documentation