You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ifInErrors for Ethernet interfaces are expected to have L2 CRC errors. With a change that went into SNMP, the RIF counters are being aggregated into ifInErrors/ifOutErrors, this is misleading while monitoring the link for CRC errors.
This is becuase there was a change added in SONiC SNMP to support VLAN and RIF counters.
As a part of this change, the ifInErrors(1.3.6.1.2.1.2.2.1.14) and ifOutErrors(1.3.6.1.2.1.2.2.1.20) OIDs will start seeing sum of L2 and L3 (RIF) counters for each interface.
Issue seen in 202205 image onwards.
Boot up image on platform with RIF counter support with Ethernet RIF interface.
From CLI below, can see that there are are no L2 errors on Ethernet112 but there are RIF errors:
(paste your output here or download and attach the file here )
#### Additional information you deem important (e.g. issue happens only occasionally):
<!--
Also attach debug file produced by `sudo generate_dump`
-->
The text was updated successfully, but these errors were encountered:
Description
ifInErrors for Ethernet interfaces are expected to have L2 CRC errors. With a change that went into SNMP, the RIF counters are being aggregated into ifInErrors/ifOutErrors, this is misleading while monitoring the link for CRC errors.
This is becuase there was a change added in SONiC SNMP to support VLAN and RIF counters.
As a part of this change, the ifInErrors(1.3.6.1.2.1.2.2.1.14) and ifOutErrors(1.3.6.1.2.1.2.2.1.20) OIDs will start seeing sum of L2 and L3 (RIF) counters for each interface.
Restored snmp vlan support per RFC1213 and added the missing support for RFC2863 by raphaelt-nvidia · Pull Request #218 · sonic-net/sonic-snmpagent (github.com)
https://github.com/sonic-net/sonic-snmpagent/blame/a281f9ab771adaa438f01fd5394d7a73ed6bc1d6/src/sonic_ax_impl/mibs/ietf/rfc1213.py#L361
Steps to reproduce the issue:
Issue seen in 202205 image onwards.
Boot up image on platform with RIF counter support with Ethernet RIF interface.
From CLI below, can see that there are are no L2 errors on Ethernet112 but there are RIF errors:
(paste your output here)
(paste your output here or download and attach the file here )
The text was updated successfully, but these errors were encountered: