[CoPP]: Added neighbor_miss trap verification and cli test#18326
[CoPP]: Added neighbor_miss trap verification and cli test#18326yxieca merged 2 commits intosonic-net:masterfrom
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@prabhataravind @prsunny, please review. |
Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>
28a7098 to
4403df2
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@rminnikanti , can you check the test failure? As I understand, this test should fall back to old behavior if new traps are not installed, hence should not have a dependency on (sonic-net/sonic-buildimage#22406) |
|
@prsunny, tests also verify the new CLI command is not yet part of the master image: PR failures log: _ansible_no_log = None
stdout =
stderr =
Usage: show [OPTIONS] COMMAND [ARGS]...
Try "show -h" for help.
Error: No such command "copp".
FAILEDsonic-utilities submodule in master doesn't yet include the new copp CLI changes. commit c19ece7106b30d941aff8774f1742486eebc1ec3
Author: mssonicbld <79238446+mssonicbld@users.noreply.github.com>
Date: Thu May 22 19:01:49 2025 +0800
[submodule] Update submodule sonic-utilities to the latest HEAD automatically (#22614) |
|
Should it also be part of the 202505 branch, right? I don't see the label for 202505 |
|
@nhe-NV I edited the PR description and added 202505 backport from my side. |
|
/azpw run Azure.sonic-mgmt |
|
/AzurePipelines run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@prsunny @prabhataravind PR checks are passing now. Can you please review |
|
@prabhataravind , would you review and signoff? |
I see the label for 202505 is not added, I will add it in case not missing |
|
@dgsudharsan could you pls review as well, esp from Nvidia platform pov? |
|
@StormLiangMS , would you help with merge? |
|
@yxieca can you please help merge this PR? |
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>
|
Cherry-pick PR to 202505: #20397 |
* Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com> Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com> Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com> Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com> Signed-off-by: Guy Shemesh <gshemesh@nvidia.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com> Signed-off-by: Yael Tzur <ytzur@nvidia.com>
…#18326) * Added neighbor_miss trap and copp cli tests Added test for the following - If the platform supports neighbor_miss trap, verify Vlan subnet traffic is policed under neighbor_miss copp - Verify 'show copp configuration' CLI output - Verify trap installation status of configured traps Signed-off-by: Ravi Minnikanti <rminnikanti@marvell.com>

Description of PR
show copp configurationCLI output -test_verify_copp_configuration_cli.Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
sonic-net/SONiC#1943
How did you do it?
update_copp_config.pyscript to not modify neighbor_miss trap CBS/CIR values if the platform supports this trap type. This way verification will be able to verify neighbor_miss trap is policed under its own copp but not under default trap.How did you verify/test it?
Tested by running copp component tests on T0 topology on marvell-teralynx platform.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation