Showing results for 
Search instead for 
Did you mean: 

Jumbo and Output errors at the TX on Nexus 5596


We are observing huge increase in Jumbo and Output errors at the TX on one of ourNexus 5596 switch.

Do we have any specific reason and what will be the soulution to fix this?

Please find the interface output.

Ethernet1/24 is up

Dedicated Interface

  Belongs to Po324

  Hardware: 1000/10000 Ethernet, address: 547f.eefb.ff9f (bia 547f.eefb.ff9f)

  MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec

  reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation ARPA

  Port mode is trunk

  full-duplex, 10 Gb/s, media type is 10G

  Beacon is turned off

  Input flow-control is off, output flow-control is off

  Rate mode is dedicated

  Switchport monitor is off

  EtherType is 0x8100

  Last link flapped 2week(s) 5day(s)

  Last clearing of "show interface" counters 01:02:11

  30 seconds input rate 280 bits/sec, 0 packets/sec

  30 seconds output rate 35339936 bits/sec, 7590 packets/sec

  Load-Interval #2: 5 minute (300 seconds)

    input rate 8.32 Mbps, 633 pps; output rate 33.49 Mbps, 7.35 Kpps


    1577334 unicast packets  186 multicast packets  4280 broadcast packets

    1581800 input packets  990139607 bytes

    540658 jumbo packets  0 storm suppression bytes

    0 runts  0 giants  0 CRC  0 no buffer

    0 input error  0 short frame  0 overrun   0 underrun  0 ignored

    0 watchdog  0 bad etype drop  0 bad proto drop  0 if down drop

    0 input with dribble  0 input discard

    0 Rx pause


    27130970 unicast packets  1166 multicast packets  26407 broadcast packets

    27158543 output packets  15956581601 bytes

    7231723 jumbo packets

    260 output errors  0 collision  0 deferred  0 late collision

    0 lost carrier  0 no carrier  0 babble 0 output discard

    0 Tx pause

  0 interface resets

2 Replies 2

Richard Michael
Cisco Employee
Cisco Employee

Hi Senthil,

What interface is the Ethernet 1/24? Is it a part of the FEX port-channel? If yes, VNTAG header addition might show there as jumbo packets the extra 6 byte.

If not, then understand why you receive a frame more than 1500 bytes. you might also try enabling the jumbo frame,


Ricky Micky

*Rate if its useful

Kanes Ramasamy

Hi Senthil,


Have you managed to solve this issue? I seem to be having the same problem?

Could you share your outcome?


Thanks and most appreciated,



Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: