Skip navigation
Cisco Learning Home > Certifications > Routing & Switching (CCNP) > Discussions

_Communities

30568 Views 4 Replies Latest reply: Nov 3, 2009 7:01 AM by Scott Morris - CCDE/4xCCIE/2xJNCIE RSS

Currently Being Moderated

troubleshoot input errors

Sep 14, 2009 11:57 AM

JoshG 72 posts since
May 20, 2008

Anyone have any ideas what to look for when you have an interface that is receiving a large number of input errors?

 

GigabitEthernet0/51 is up, line protocol is up (connected)
  Hardware is Gigabit Ethernet, address is 0023.ab66.15b3 (bia 0023.ab66.15b3)
  MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec,
     reliability 254/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive not set
  Full-duplex, 1000Mb/s, link type is auto, media type is 1000BaseSX SFP
  input flow-control is off, output flow-control is unsupported
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:12, output 00:00:01, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 242000 bits/sec, 159 packets/sec
  5 minute output rate 666000 bits/sec, 157 packets/sec
     2802578 packets input, 2915628256 bytes, 0 no buffer
     Received 765 broadcasts (0 multicasts)
     0 runts, 0 giants, 0 throttles
     42479 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 765 multicast, 0 pause input
     0 input packets with dribble condition detected
     1493331 packets output, 325973353 bytes, 0 underruns
     0 output errors, 0 collisions, 1 interface resets
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 PAUSE output
     0 output buffer failures, 0 output buffers swapped out

 

The only thing I can think to do is SPAN that port and collect wireshark logs. But then I wouldn't know what to look for. Any help would be appreciated.

  • Kailen Harper 143 posts since
    Jun 24, 2008
    Currently Being Moderated
    1. Sep 14, 2009 12:13 PM (in response to JoshG)
    Re: troubleshoot input errors

    Josh,

     

         The first things I look at are the controller for the interface (show controller , show ip interface) and the logging to make sure I don't have a speed/duplex problem. Then replace the cable or move the device to another port and see if the problem moves or goes away. If all of that checks out then it's time to start digging in deep. Also make sure the NIC on whatever device is connected to the port is configured correctly and has a current driver. Try these first and if you need to go deeper we can burn that bridge when you get there.

     

    Good Luck,

     

    Kailen

  • Darwin R CCNA/CCDA 580 posts since
    Jun 22, 2009
    Currently Being Moderated
    2. Sep 14, 2009 12:19 PM (in response to JoshG)
    Re: troubleshoot input errors

    Hello Josh,

     

    Have you cleared the counters on that interface recently in order to see how fast they increment? Have you just starting noticing this issue or is it reocurring? Is it affecting performance? What's type hardware is connected to the switch port?

     

    I'm wondering if it could be a faulty nic/port on connected device. Normally, you would see more than just input errors with bad cabling...not all the time though.

     

    We're talking technology...anything is liable to be wrong

     

    Regards,

     

    Darwin

  • iDen 5 posts since
    Nov 2, 2009
    Currently Being Moderated
    3. Nov 3, 2009 12:29 AM (in response to JoshG)
    Re: troubleshoot input errors

    i do have same problem.

    it lasts dusring last week, and issue happens only after 7pm with time interval about 1-1.5 hour

    cleared counters here is output taken during last evening

    by the first time i thought that it's broadcast storm, but check other outputs

    Have no idea what to do.

     

    8:33pm

    FastEthernet0/0 is up, line protocol is up

      Description: -=LAN4.0=-
      Internet address is 192.168.4.1/24
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 2/255, rxload 2/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 100Mb/s, 100BaseTX/FX
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:00, output 00:00:00, output hang never
      Last clearing of "show interface" counters 02:27:40
      Input queue: 0/75/149/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      30 second input rate 879000 bits/sec, 743 packets/sec
      30 second output rate 945000 bits/sec, 616 packets/sec
         5003967 packets input, 730977789 bytes
         Received 366 broadcasts, 0 runts, 0 giants, 0 throttles
         24 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 watchdog
         0 input packets with dribble condition detected
         4820207 packets output, 1030556118 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

     

    10.29pm

    FastEthernet0/0 is up, line protocol is up
      Hardware is Gt96k FE, address is 001b.d4ca.e138 (bia 001b.d4ca.e138)
      Description: -=LAN4.0=-
      Internet address is 192.168.4.1/24
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 2/255, rxload 2/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 100Mb/s, 100BaseTX/FX
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:00, output 00:00:00, output hang never
      Last clearing of "show interface" counters 01:23:51
    Input queue: 0/75/726/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      30 second input rate 1044000 bits/sec, 741 packets/sec
      30 second output rate 986000 bits/sec, 704 packets/sec
         3107427 packets input, 478664898 bytes
         Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
         257 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 watchdog
         0 input packets with dribble condition detected
         2979026 packets output, 450471479 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

    10.40

    FastEthernet0/0 is up, line protocol is up
      Hardware is Gt96k FE, address is 001b.d4ca.e138 (bia 001b.d4ca.e138)
      Description: -=LAN4.0=-
      Internet address is 192.168.4.1/24
      MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      Full-duplex, 100Mb/s, 100BaseTX/FX
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:00, output 00:00:00, output hang never
      Last clearing of "show interface" counters 01:26:20
    Input queue: 28/75/726/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: fifo
      Output queue: 0/40 (size/max)
      30 second input rate 734000 bits/sec, 645 packets/sec
      30 second output rate 629000 bits/sec, 577 packets/sec
         3203651 packets input, 493292970 bytes
         Received 2 broadcasts, 0 runts, 0 giants, 0 throttles
        448 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
         0 watchdog
         0 input packets with dribble condition detected
         3069987 packets output, 464035958 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

  • Scott Morris - CCDE/4xCCIE/2xJNCIE 8,395 posts since
    Oct 7, 2008
    Currently Being Moderated
    4. Nov 3, 2009 7:01 AM (in response to iDen)
    Re: troubleshoot input errors

    As I noted i the other place you posted this, I'm more concerned with the input queues growing.  Look at what's eating the CPU of the router and/or look at running a network analyzer (span port) to see the traffic coming in because something flooding the **** out of that router.

     

    Also consider control plane policing.

     

    HTH,

     

    Scott

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)