[action] [PR:19879] Ignore log analyzer error message related to source port GID mapping …#19936
Merged
mssonicbld merged 1 commit intosonic-net:202411from Jul 31, 2025
Merged
Conversation
11 tasks
Collaborator
Author
|
Original PR: #19879 |
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
prabhataravind
approved these changes
Jul 31, 2025
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
3 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.
…in kernel
Description of PR
Summary:
Below Error message is seen occasionally during BFD scale test run
"
ERR kernel: [16615.430155] leaba_module_device 0000:0d:00.0: NPU2: leaba_hostif_get_by_port: Port gid out of range port_gid=384
"
It is transient and stops when trap action for BFD is programmed to send to SAI instead of NETDEV.
All BFD packets are sent to NPU host, it reinjects them if it does not have matching session so that CPU receives it. Once Session is estlabished, NPU host absorbs the message. since packet is recieved from NPUH , source system port is not correct in PUNT header and SDK logs error when packet is destined to NETDEV.
If packet is destined to SAI, kernel does not do the check. once the trap action is changed to SAI, error message is not seen.
This error message is seen in other scenarios and they have rate limited on the number of times this message is displayed
Fixes # (issue)
This error message does not have any functionality impact. Fix is to move the log message to ignore list.
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation