Certain ETH RMON counting is different from the definitions of the standard.
The standard is imperfect and this problem need not be solved.
The standard defines the ETH RMON counting at an early time and fails to consider that the MTU can be set. As a result, the current logic defines certain ETH RMON counting differently, but covers the definitions of the standard. As agreed, the current logic still processes the following RMON counting. The main points are as follows:
1. When the received ETH packets have Pause+FCS errors, the ETH RMON counts the rxbad item and rxpause item.
2. The definition of the ethover (the oversized packets): Only the packets of a length exceeding the MTU set by the logic are considered as oversized packets, instead of the packets whose length exceeds a specified value. For example, if the MTU is set to 2000, then packets containing more than 2000 bytes are considered as oversized packets.
3. The definition of the ethjab (the errored oversized packets): The received packets whose length exceeds the MTU and that contain FCS or alignment errors are considered as errored oversized packets.
4. The definition of the rxbad (the errored packet): The received packets that are of an illegal length and contain CRC errors are considered as rxbad packets. Currently, MTU setting is supported. Therefore, the rxbad packets can be defined as the packets that contain less than 64 packets or more than MTU packets and CRC errors.
5. The definition of the rxbox (the good packet): The received packets that contain more than 64 bytes but less than MTU bytes without errors are considered as rxbox packets..
PS: MTU is the maximum packet length in the Ethernet.