Modified FIB testcases to support T2 topology on multi-dut #2891
Conversation
This file contains 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
|
Will create a new PR with the changes made for multi-dut in FIB. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Approach
What is the motivation for this PR?
Needed FIB testcases to support T2 topology for multi-dut
How did you do it?
To run traffic across multiple line cards in case of VOQ, needed access to T3 and T2 line cards so removed 'rand_one_dut_hostname' .
sending traffic from T1 to T3 line cards.
How did you verify/test it?
Ran testcases on VOQ testbed with T2 topology
Any platform specific information?
Supported testbed topology if it's a new test case?
T2
Documentation