Skip to content

[action] [PR:9587] [Nvidia] Fix qos sai test for supporting LAG port #9996

Merged
mssonicbld merged 1 commit intosonic-net:202305from
mssonicbld:cherry/202305/9587
Sep 15, 2023
Merged

[action] [PR:9587] [Nvidia] Fix qos sai test for supporting LAG port #9996
mssonicbld merged 1 commit intosonic-net:202305from
mssonicbld:cherry/202305/9587

Conversation

@mssonicbld
Copy link
Collaborator

Description of PR

Previously, on Nvidia devices, to make port congestion, we disable the port. So, if a LAG port is used as the tx port in the test, the LAG port will go down in 90s because the lacp pdus are also blocked, which will fail the tests. Therefore, we skip the test on the LAG port for QoS tests. Currently, to make the LAG port also support QoS test, we block the data plane queue instead of disabling the port. This change will work for all topo on Nvidia devices.

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 201911
  • 202012
  • 202205

Approach

What is the motivation for this PR?

Make Qos sai test support LAG port

How did you do it?

we block the data plane queue instead of disabling the port. So the control plane still work normally.

How did you verify/test it?

Run qos sai test on t1-lag-64 topo

Any platform specific information?

Any

Supported testbed topology if it's a new test case?

Any

Documentation

Description of PR
Previously, on Nvidia devices, to make port congestion, we disable the port. So, if a LAG port is used as the tx port in the test, the LAG port will go down in 90s because the lacp pdus are also blocked, which will fail the tests. Therefore, we skip the test on the LAG port for QoS tests. Currently, to make the LAG port also support QoS test, we block the data plane queue instead of disabling the port. This change will work for all topo on Nvidia devices.
@mssonicbld
Copy link
Collaborator Author

Original PR: #9587

@mssonicbld mssonicbld merged commit 9141cea into sonic-net:202305 Sep 15, 2023
@mssonicbld mssonicbld deleted the cherry/202305/9587 branch February 4, 2024 09:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants