Link to home
Start Free TrialLog in
Avatar of Evolutionzz
Evolutionzz

asked on

Cisco Interface Input Errors and Giants

How do I resolve interface errors?

r6bu200_cat4506a.r6bu.200#sho int tenGigabitEthernet 2/2
TenGigabitEthernet2/2 is up, line protocol is up (connected)
  Hardware is Ten Gigabit Ethernet Port, address is e8b7.48cd.216c (bia e8b7.48cd.216c)
  Description: cat6509a.x7y3.200
  MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 10Gb/s, link type is auto, media type is 10GBase-SR
  input flow-control is on, output flow-control is on
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:02, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 11538000 bits/sec, 6464 packets/sec
  5 minute output rate 7654000 bits/sec, 4696 packets/sec
     199689853 packets input, 51594226394 bytes, 0 no buffer
     Received 26195241 broadcasts (21721329 multicasts)
     0 runts, 502 giants, 0 throttles
     502 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     141512592 packets output, 30945681421 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out


r6bu200_cat4506a.r6bu.200#sho int tenGigabitEthernet 2/3
TenGigabitEthernet2/3 is up, line protocol is up (connected)
  Hardware is Ten Gigabit Ethernet Port, address is e8b7.48cd.216d (bia e8b7.48cd.216d)
  Description: cat6509a.x8y3.200
  MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 10Gb/s, link type is auto, media type is 10GBase-SR
  input flow-control is on, output flow-control is on
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:05, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 14130000 bits/sec, 6987 packets/sec
  5 minute output rate 11616000 bits/sec, 5999 packets/sec
     1744442977 packets input, 2398579286032 bytes, 0 no buffer
     Received 26036040 broadcasts (21860444 multicasts)
     0 runts, 62641 giants, 0 throttles
     62641 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     288186653 packets output, 59060817765 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out
SOLUTION
Avatar of Zephyr ICT
Zephyr ICT
Flag of Belgium image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Evolutionzz
Evolutionzz

ASKER

I did.  These interfaces  are trunks and mtu is 1500.
Avatar of Don Johnston
What is connected to these ports?

It would appear that the connected devices either have their MTU's set to greater than 1,500, or they have jabbering interfaces (which seems unlikely).
Yes, still convinced something in the chain isn't happy with the MTU being used. Check everything that is connected to the switches, also possible virtual systems ...
There's  a lot a VM's on the network using those interfaces and associated port channels.  So I need to verify  every device  and VM using those interfaces and port channels?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
How would I determine  what to increase the mtu to? I would still need to determine  what the mtu for the VM's are, correct?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Ok.  Thanks for the tips.
Last question,  how do I determine the error rate and what rate is above the acceptable rate for input errors and CRC errors?
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
for TenGigabitEthernet2/3 the input error rate would be 62641 divided by 14130000 which is   4.433 %??????


Hardware is Ten Gigabit Ethernet Port, address is e8b7.48cd.216d (bia e8b7.48cd.216d)
  Description: cat6509a.x8y3.200
  MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 10Gb/s, link type is auto, media type is 10GBase-SR
  input flow-control is on, output flow-control is on
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:05, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 14130000 bits/sec, 6987 packets/sec
  5 minute output rate 11616000 bits/sec, 5999 packets/sec
     1744442977 packets input, 2398579286032 bytes, 0 no buffer
     Received 26036040 broadcasts (21860444 multicasts)
     0 runts, 62641 giants, 0 throttles
     62641 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 input packets with dribble condition detected
     288186653 packets output, 59060817765 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out