Update CoPP configs to handle neighbor_miss trap type#18480
Closed
msherif1234 wants to merge 1 commit intosonic-net:masterfrom
Closed
Update CoPP configs to handle neighbor_miss trap type#18480msherif1234 wants to merge 1 commit intosonic-net:masterfrom
msherif1234 wants to merge 1 commit intosonic-net:masterfrom
Conversation
Signed-off-by: Mohamed S. Mahmoud <[email protected]>
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Author
|
changes already handled in |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Added neighbor_miss trap copp configuration
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
New trap id was added to handle
NEIGHBOR_MISSpackets, punted traffic with this typego to a dedicated queue that has lower policer rate limiting than other control plane traffic.
How did you do it?
Added new config for the queue used
queue1_group3for neigh_miss trap id.How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation
depends on
sonic-net/sonic-swss#3624