Aggregate L3 errors with L2 discards for interfaces with RIF#325
Aggregate L3 errors with L2 discards for interfaces with RIF#325bingwang-ms merged 1 commit intosonic-net:masterfrom
Conversation
|
@bingwang-ms @SuvarnaMeenakshi Please review |
|
@stepanblyschak thank you for fixing this. |
|
@SuvarnaMeenakshi ifInDiscard is port buffer drops. Do we know that no monitor app is treating ifInDiscard as port buffer drops? As we are talking about breaking change for established release, a simple revert is less destructive than remap. |
967f311 to
7d43fbf
Compare
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
7d43fbf to
ceb770a
Compare
|
@SuvarnaMeenakshi Discussed offline, your comment is addressed, please review |
…et#325) Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
|
Cherry-pick PR to 202405: #326 |
|
@yxieca Can you please approve the cherry-pick to 202311 branch? Thanks |
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
…et#325) Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
|
Cherry-pick PR to 202311: #327 |
Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
…et#325) Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>
Fixes sonic-net/sonic-buildimage#19715
- What I did
Today we sum L2 and L3 errors on RX/TX in ifInErrors/ifOutErrors counters that are part of RFC1213 MIB.
It appears that the monitoring system is using ifInErrors as a way to detect CRC errors on physical interfaces.
The RFC vaguely defines ifInErrors as:
instead, aggregate errors on L3 as part of ifInDiscard and ifOutDiscard.
- How I did it
Removed aggregation logic and updated UT.
- How to verify it
Manual snmpwalk on interfaces - trigger L3 error - e.g. packet with dst map != router mac, check counter by snmpwalk.
Generate RIF RX errors:
Before this change (14 - error, 13 - discard):
After this change:
- Description for the changelog