NE40E version: V300R002C06B325
Use the display interface Eth-Trunk 0 command to view the count results:
2118045376018 packets input, 1253086769442757 bytes, 31251043 dropsThe number of dropped packets increases greatly.
View the number of member ports on Eth-Trunk 0:
display interface GigabitEthernet 1/0/4
Overrun: 0 , InRangeLength: 929195
display interface GigabitEthernet 1/0/3
Overrun: 0 , InRangeLength: 17858755
The count of InRangeLength on the port increases continuously.
Add all the InRangeLength values. As a result, the total value is equal to the number of dropped packets on Eth-Trunk 0. Therefore, the conclusion is that the dropped packets are the InRangeLength packets over the member port.
The InRangeLength field indicates that the value range of 46�1500 of the length/type field in the received frames does not match the actual value. In this case, the packets are dropped.
The conclusion is that the lengths of dropped frames do not match the actual length. The packets are incorrect or virus attacks occur on the user side.Because the packets are dropped on the PIC instead of on the CPU, the problem cannot be located by capturing packets on the CPU. It is recommended that the layer-2 link be checked or packets be captured on the user side.
In most cases, a count mistake over a port results from a link failure. Check the member port on Eth-Trunk 0 to troubleshoot the problem.
The lengths of dropped frames do not match the actual length. This is probably due to the layer-2 link or virus attacks. The problem does not affect other user services.