Cisco interface's statistics : explained

• Overruns : number of times that the device was incapable of handing received data to a hardware buffer because the input rate exceeded the device capability to handle the data
• underruns : number of times that the transmitter ran faster than the device could handle
• CRC : number of cyclical redundancy check errors. When a station sends a frame, it appends a CRC to the end of the frame. This is generated from an algorithm based on the data in the frame. If the frame is altered between the source and the destination, the device notes that the CRC does not match. A high number of CRC is usually the result of collision or a station transmitting bad data
• frame : number of frame errors. Bad frames include packets with an incorrect length or bad frame checksums. This error is usually the result of collisions or malfunctioning Ethernet device
• runts: number of packets that are discarded because they are smaller than the minimum packet size, which is 64 bytes. Runts are usually caused by collisions. They might also be caused by poor wiring and electrical interference
• giants : number of packets that are discarded because they exceed the maximum packet size. For example, any Ethernet packet that is greater than 1518 bytes is considered a giant
• Deferred (for fastethernet interfaces only) : number of frames that were deferred before transmission due to activity on the link
• output errors : number of frames not transmitted because the configured maximum number of collisions was exceeded. This counter should only increment during heavy network traffic
• collisions : number of message retransmitted due to an Ethernet collision (single and multiple collisions). This usually occurs on an overextended LAN (Ethernet or transceiver cable too long, more than 2 repeaters between stations, or too many cascaded multi-port transceivers)
• late collisions : number of frames that were not transmitted because a collision occurred outside the normal window. A late collision is a collision that is detected late in the transmission of the packet. Normally, these should never happen. When 2 Ethernet hosts try to talk at once, they should collide early in the packet and both back off, or the second host should see that the first one is talking and wait. This is not a real problem because networking protocols are designed to cope with collisions by resending packets
• input queue : shows the number of packets in the input queue (hardware and software input queue )
• output queue : shows the number of packets in the output queue (hardware and software input queue )

------------------------------------------------------------------------------------------------------
I will be honored to read your comment about this post. Please feel free to leave one ☺ And if you have a Cisco IOS, Firewall ASA Or Mircrosoft server infrastructure topic you would like me to add in this blog, i will be more than happy to know which one ☺
-------------------------------------------------------------------------------------------------------