Use display interface to check interface message Statistics, such as:
Input: 207300 packets, 12438000 bytes
1267168 broadcasts, 12 multicasts
6523 errors, 0 runts, 0 giants, 0 CRC,
0 collisions, 0 late collisions, 0 overruns,
0 jabbers, 0 input no buffers, 6523 Resource errors
0 other errors
Output:194571 packets, 11674260 bytes
0 errors, 0 late collisions,
0 underruns, 0 retransmit limits
In this case we can very clearly find the input: received 207300 packets, a total of 12438000 bytes, of which there are 1267168 broadcast packets, 12 multicast packets; The output sent 194571 packets, a total of 11674260 bytes.
All the other instructions are as follows:
『Input』
errors： is the sum total of the all port abnormal Statistics, including：runts、giants、CRC、collisions、late collisions、overruns、jabbers、input no buffers、Resource errors、other errors。
Runts: short frame error, MAC chip received message length less than 60 bytes (including filling bytes).
Giants: long frame error, E200 management network interface can support the longest frame is 1536 bytes, 2FE network interface can support the longest frame is 1700 bytes.
CRC: CRC check error. This error is usually caused by line quality. But, if the peer end work in half-duplex mode and the local interface work in full-duplex mode, and the flow is large, the interface will receive runts and CRC error message at the same time. This phenomenon can, in turn, deduce maybe the peer end Network interface work mode does not match.
Collisions:
Late collisions: collision error, this error is generally caused by MAC work in half-duplex mode.
Overruns: MAC chip input queue overflow. MAC chip first buffer the message to the chip FIFO queue cache, when reach a certain byte, will move the message saved in FIFO to the system main store. If chip processing ability is weak and flow is large, will appear before a message do not finish move, the content of next message write into the FIFO. Namely overrun. Network interface of high performance of usually won't appear this error.
Jabbers: unable to make sure or redundant message.
Input no buffers: software memory application error. Software do not get enough memory to store the message of MAC chip. Usually won't appear this error. If this error statistics increasing all the time means exist software may exist memory leak problem.
Resource errors: receiving resources error. MAC chip cannot get the available receiving descriptor to receive message, will lead to packet loss. This means the interface flow is too large, beyond the processing capability. But this error is normal phenomenon, it can qualitatively describe the internet interface flow is large in a period of time.
The overruns and Resource errors count of interface statistics information is not 0, and find it is sustaining increasing, explain the flow is beyond the processing capability, if the two numbers increase slowly, will not affect the normal service.
『Output』
Late collisions: late collisions, the relevant error as half-duplex work mode.
Underruns: MAC chip output queue overflow. And similar to input overrun error. When send message, MAC chip first move the message from main store to the chip output FIFO queue cache, when reach a certain byte, MAC chip will output the message saved in FIFO. If chip processing ability is weak and flow is large, will appear before a message do not finish move, the content of next message write into the FIFO. Namely underrun. Network interface of high performance of usually won't appear this error.
Retransmit limits: output beyond retransmit limits. And the relevant error as half-duplex work mode.
When check the interface having error, can refer to the above information to find the failure factor.
