No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ: The meaning of common error packets under the port

Publication Date:  2012-09-26 Views:  2 Downloads:  0
Issue Description
Q:
The meaning of common error packets under the port
Alarm Information
none
Handling Process
Input error:
Runts: short frame errors. MAC chips received packet length is less than 60 bytes (including padding bytes).
Giants: long frame errors. E200 management Ethernet port can support a maximum frame 1536 bytes, and 2FE network port can support a maximum frame is 1700 bytes.
CRC: CRC checked wrong. This error is generally caused by the line quality. However, if peer end worked in half-duplex mode and the local interface worked in full duplex mode, and flow is large, the interface will receive both the Runts and CRC error packet.
This behavior can deduce the problem that the peer end network interface do not match the working mode in turn.
Collisions: collisions errors, this error usually the MAC works in half-duplex mode causes the wrong package.
Overruns: MAC chip input queue overflow. Firstly, MAC chips packet stores to the chip FIFO queue cache, when you reach a certain byte, the MAC chip output the packet saved in the FIFO to the system memory. If chip processing ability is relatively weak and the flow is large, appears before a packet has not been completely removed, the next packet will be written to the FIFO. That is overrun. High performance networks generally do not have this type of error.
Input no buffers: software memory application errors. Software can’t apply enough memory to accommodate the MAC chip packets received. This error does not occur under normal situation. If this error Statistics grew all the time means the software might have a memory leak problem.
Resource errors: receiving resource error.MAC chip is not available to receive descriptors to receive packets, lead to packet loss. This description the interface traffic is too large, more than capable of withstanding capacity. However, this error is normal, and it can mean that the intranet interface flow is large for some time.

Output:
Late collisions: late collisions, the error associated with half-duplex working mode.
Underruns: MAC chip output queue overflow. With similar input overrun error. When you send a packet, Firstly, MAC chip packet stores to the chip FIFO queue cache, when you reach a certain byte, the MAC chip output the packet saved in the FIFO to the system memory. If chip processing ability is relatively weak and the flow is large, appears before a packet has not been completely removed, the next packet will be written to the FIFO. That is overrun. High performance networks generally do not have this type of error.
Retransmit limits: the output exceed retransmission count limit. The error associated with the half-duplex working mode-related.
Root Cause
none
Suggestions
none

END