Showing results for 
Search instead for 
Did you mean: 

input errors

Hello all 

i have 1 cisco 6500 and 2 nexus 5k(vpc) in my topology

cisco 6500 connected nexus  by 2 fiber cables each nexus (channel-group)

i give a "input errors" one of the interface on cisco nexus

what is the reason 


Ethernet1/1 is up
admin state is up, Dedicated Interface
Belongs to Po3
Hardware: 1000/10000 Ethernet, address: 00c8.8bcc.37aa (bia 00c8.8bcc.37aa)
Description: ****to cisco 6500****
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadcast
Port mode is trunk
full-duplex, 10 Gb/s, media type is 10G
Beacon is turned off
Auto-Negotiation is turned on
Input flow-control is off, output flow-control is off
Auto-mdix is turned off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
EEE (efficient-ethernet) : n/a
Last link flapped 19:26:31
Last clearing of "show interface" counters 19:29:55
3 interface resets
30 seconds input rate 1910056 bits/sec, 199 packets/sec
30 seconds output rate 200 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 384.33 Kbps, 48 pps; output rate 248 bps, 0 pps
1794008 unicast packets 2427246 multicast packets 447912 broadcast packets
4669166 input packets 2709425652 bytes
1563979 jumbo packets 0 storm suppression packets
0 runts 459 giants 0 CRC 0 no buffer
459 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
10 unicast packets 13588 multicast packets 153 broadcast packets
13751 output packets 2246280 bytes
0 jumbo packets
0 output error 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause

Everyone's tags (2)

You need to understand what

You need to understand what is input errors the input errors is includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Here in your case input errors are exactly same as giants i.e. 459. So these input errors is because of giants.

Giants are because of  Frames received that exceed the maximum IEEE 802.3 frame size (1518 bytes for non-jumbo Ethernet) and have a bad Frame Check Sequence (FCS). So you you need to find out why Jumbo Frame grater than 1518 is coming on that interface.

Please rate if you find this post useful


Pawan (CCIE 52104)

VIP Expert



Since the devices are connected via fiber, try replacing the fiber patch on interface e1/1. If you don't have extra fiber cable in hand, you can simply clean the connectors with alcohol.  If that does not help try replacing the optic as well. Clear the counters and test again.


CreatePlease to create content
Content for Community-Ad