Ethernet Switching
Highlighted
Ethernet Switching

errors on multiple errors

[ Edited ]
‎09-12-2019 11:56 PM

Hi all,

As you can see that some interfaces have mtu errors hugeee. why don't these interfaces have any Drops or Errors.... If there is no any Drops and Errors, can we understant these interfaces are okay and in normal operating? If you think no....What troucleshooting must be done? And what reason behind this mtu errors?

 

9200ex>show interfaces extensive | match ".........
Carrier transitions: 0, Errors: 0, Drops: 2661, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 4367, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 1819827, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 2346, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 4570, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 83754, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Errors: 2720, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3 incompletes: 2720, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0
Errors: 4, Drops: 0, Framing errors: 4, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0
Errors: 58, Drops: 0, Framing errors: 47, Runts: 11, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0
Carrier transitions: 4, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 116115, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 115723, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 1311, Resource errors: 0
Carrier transitions: 4, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Errors: 1, Drops: 0, Framing errors: 1, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0
Errors: 2, Drops: 0, Framing errors: 2, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0

 

Thx

A

2 REPLIES 2
Highlighted
Ethernet Switching

Re: errors on multiple errors

‎09-13-2019 02:44 AM

Hi,

 

The MTU errors that you are seeing are seen as the Output errors on the respective interfaces.

It simply means that there are some big packets which are exiting the interfaces and it does not necessarily mean that the packet is being dropped at the output of the interface.

You can check the MTU settings on the local interfaces and the remote side MTU.

There will be packet drop only in the situation where  transit packets whose packet size is bigger than the MTU of the outgoing interface, and if the DF (Do-Not-Fragment) bit is set in the packet header, these packets will be dropped at the outgoing interface and output MTU errors will be counted.

For that you need to check if the MTU errors are incrementing.

 

Hope this helps.

 

 

Highlighted
Ethernet Switching

Re: errors on multiple errors

‎09-13-2019 01:40 PM
In case those interfaces are configured as "interface-mode trunk" you may want to increment the MTU manually, as it will not automatically adjust as other EX platforms do. See: