Test plan for LAG on Distributed VOQ System #3033
Merged
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
|
retest vs image please |
oxygen980
force-pushed
the
lag_testplan
branch
from
15262a2
to
1121448
Compare
oxygen980
changed the title
|
@eswaranb - please add Arista reviewers |
|
retest vs image please |
2 tasks
|
retest vs image please |
2 similar comments
|
retest vs image please |
|
retest vs image please |
|
@yxieca, Could you help merge this test plan? The failures in the test case are unrelated to this commit. And this was presented in the test community last week. Thanks. |
added 2 commits
March 29, 2021 16:37
|
@yxieca @wangxin , @saravanansv - could you please take a look, thanks. |
wangxin
reviewed
Apr 9, 2021
|
|
||
| Verify that when a LAG is dynamically deleted via CLI on an ASIC, it is removed in remote ASIC_DB. | ||
| ### Test Steps | ||
| * Delete an existing LAG from any ASIC in the OC topology |
There was a problem hiding this comment.
OC topology was to refer Open community topology, I have removed 'OC topology'.
wangxin
approved these changes
Apr 12, 2021
saravanansv
pushed a commit
to saravanansv/sonic-mgmt
that referenced
this pull request
May 6, 2021
What is the motivation for this PR? This is the test plan for LAG on SONIC Distributed VOQ System, as described in the VOQ LAG HLD (https://github.com/Azure/SONiC/blob/2e05c6b8ac570fd237484a18e732a58eec004b9c/doc/voq/lag_hld.md) The PR covered in this test plan is Distributed VOQ LAG HLD PR 697 (https://github.com/Azure/SONiC/pull/697/files#diff-77ea0c16b4ae9885fa0e388e81f6343c6bda0f24b999f93e64fcee8467df63fc) The scope of this test plan is as follows: * Check for unique SYSTEM_LAG_ID per LAG in a chassis with multiple line cards * Check if LAG is learned by local and remote ASIC This test plan does not cover functioning of LAG as an IP/Layer3 endpoint as that is outside the scope of the code PR. How did you do it? Based on the code changes based on the associated PR Any platform specific information? This is valid only on VOQ systems. Co-authored-by: falodiya <renu.falodiy@nokia.com>
vmittal-msft
pushed a commit
to vmittal-msft/sonic-mgmt
that referenced
this pull request
Sep 28, 2021
What is the motivation for this PR? This is the test plan for LAG on SONIC Distributed VOQ System, as described in the VOQ LAG HLD (https://github.com/Azure/SONiC/blob/2e05c6b8ac570fd237484a18e732a58eec004b9c/doc/voq/lag_hld.md) The PR covered in this test plan is Distributed VOQ LAG HLD PR 697 (https://github.com/Azure/SONiC/pull/697/files#diff-77ea0c16b4ae9885fa0e388e81f6343c6bda0f24b999f93e64fcee8467df63fc) The scope of this test plan is as follows: * Check for unique SYSTEM_LAG_ID per LAG in a chassis with multiple line cards * Check if LAG is learned by local and remote ASIC This test plan does not cover functioning of LAG as an IP/Layer3 endpoint as that is outside the scope of the code PR. How did you do it? Based on the code changes based on the associated PR Any platform specific information? This is valid only on VOQ systems. Co-authored-by: falodiya <renu.falodiy@nokia.com>
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
The PR is to introduced LAG on VOQ
Summary:
Fixes # (issue)
Type of change
Approach
What is the motivation for this PR?
This is the test plan for LAG on SONIC Distributed VOQ System, as described in the VOQ LAG HLD
The PR covered in this test plan is Distributed VOQ LAG HLD PR 697
The scope of this test plan is as follows:
This test plan does not cover functioning of LAG as an IP/Layer3 endpoint as that is outside the scope of the code PR.
How did you do it?
Based on the code changes based on the associated PR
How did you verify/test it?
Any platform specific information?
This is valid only on VOQ systems.
Supported testbed topology if it's a new test case?
Documentation