Interface statistics: Difference between revisions

Interface statistics (view source)

Revision as of 10:31, 24 March 2020

12 bytes removed , 24 March 2020

no edit summary

Soumar

1,775

edits

@@ Line 43: / Line 43: @@
 RX errors apply to received packets. Following errors are counted:
-- Malformed packets: The packet was corrupt. This is a general receive
+- Malformed packets: The packet was corrupt. This is a general receive error counter and more detailed counters will be reported below.
-  error counter and more detailed counters will be reported below.
+- Hardware miss: The packet couldn't be received by the network interface card.
-- Hardware miss: The packet couldn't be received by the network
+- Out of packet buffer: There have been problems with allocating memory for the packet.
-  interface card.
+- Undersized: The packet was shorter than the minimum size of 64 Bytes and had a valid CRC.
-- Out of packet buffer: There have been problems with allocating memory
-  for the packet.
-- Undersized: The packet was shorter than the minimum size of 64 Bytes
-  and had a valid CRC.
 - Oversized: The packet exceeded the defined MTU.
 - Under or oversized: The packet was either too small or it exceeded MTU.
 - Bad CRC: Frame check sequence of layer 2 was broken.
-- Bad fragmentation: The packet was was shorter than the minimum size of 64 Bytes
+- Bad fragmentation: The packet was was shorter than the minimum size of 64 Bytes and had a bad CRC.
-  and had a bad CRC.
 - Jabber: The packet was longer than the MTU and had a bad CRC.
@@ Line 61: / Line 56: @@
 - Unable to forward: This is a generic error counter.
-- Dropped due to missing capacity: The packet could not be sent as the link
+- Dropped due to missing capacity: The packet could not be sent as the link capacity was too small.
-  capacity was too small.
 Not processed packets were dropped due to overloaded software send queues.