Verify no tx_drop counter increment on egress DUT port in oper down state #15705
+187
−1
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
alpeshspatel
approved these changes
Nov 22, 2024
|
FYI: @kevinwangsk @wsycqyz for the test |
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
Back port request
Approach
What is the motivation for this PR?
Egress DUT port in oper down state shouldn't increase the tx drop counter of the egress port.
How did you do it?
Used Ixia snappi framework to inject traffic and verify the data path.
Bring down the Ixia port to get the egress DUT port to go to Oper down state.
Check for no tx_drop counter increment after 90 seconds.
How did you verify/test it?
On a Ixia connected DUT
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation