-
Notifications
You must be signed in to change notification settings - Fork 778
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Cherry-pick 202405] New TC for PC Test on higher lag ids #16142
Merged
bingwang-ms
merged 2 commits into
sonic-net:202405
from
vikshaw-Nokia:2405_po_update_higher_lagids
Jan 15, 2025
Merged
[Cherry-pick 202405] New TC for PC Test on higher lag ids #16142
bingwang-ms
merged 2 commits into
sonic-net:202405
from
vikshaw-Nokia:2405_po_update_higher_lagids
Jan 15, 2025
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
8 tasks
arlakshm
approved these changes
Jan 3, 2025
/Azp run Azure.sonic-mgmt |
Azure Pipelines successfully started running 1 pipeline(s). |
arista-nwolfe
added a commit
to arista-nwolfe/sonic-mgmt
that referenced
this pull request
Jan 21, 2025
This test was added recently by sonic-net#16142 And does config reloads and reboots causing loganalyzer to fail
11 tasks
mssonicbld
added a commit
to mssonicbld/sonic-mgmt.msft
that referenced
this pull request
Jan 29, 2025
`test_po_update_with_higher_lagids` was added recently by sonic-net/sonic-mgmt#16142 And does config reloads and reboots causing loganalyzer to fail. ### Type of change - [x] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [x] 202405 - [x] 202411
11 tasks
mssonicbld
added a commit
to Azure/sonic-mgmt.msft
that referenced
this pull request
Feb 5, 2025
`test_po_update_with_higher_lagids` was added recently by sonic-net/sonic-mgmt#16142 And does config reloads and reboots causing loganalyzer to fail. ### Type of change - [x] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202012 - [ ] 202205 - [ ] 202305 - [ ] 202311 - [x] 202405 - [x] 202411
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:
Master PR #14842
The Test Cases focuses on the below PR Changes of lagid allocation to portchannel and new SYSTEM_LAG_IDS_FREE_LIST
sonic-net/sonic-platform-daemons#542
sonic-net/sonic-swss#3303
sonic-net/sonic-buildimage#20369
This PR is dependent on the above mentioned PR.
Type of change
Back port request
Approach
What is the motivation for this PR?
Verification of the new feature of LAG ID allocation to PortChannel and new list of SYSTEM_LAG_IDS_FREE_LIST
How did you do it?
The test case verifies traffic flow between all port channels in a full mesh topology. It begins with a system reboot to allocate the lower series of LAG IDs and validate the SYSTEM_LAG_IDS_FREE_LIST. Next, the LAG IDs are incremented through temporary port channel additions and deletions. A configuration reload is then performed to allocate higher LAG IDs to the port channels, followed by a final validation of mesh traffic.
How did you verify/test it?
Verified on T2 VOQ Chassis
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation