[CoPP]: Added neighbor_miss trap verification and cli test #18326
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
show copp configuration
CLI 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.py
script 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