Showing results for 
Search instead for 
Did you mean: 

Should I be concerned?

Paul Smith
Level 1
Level 1

Hey folks,

Uptime is 5 days. Does anybody see anything in this config I should be concerned about?

WAN-RTR-VPN01#sh int gig 0/1
GigabitEthernet0/1 is up, line protocol is up
  Hardware is CN Gigabit Ethernet, address is 2c33.115a.a7e9 (bia 2c33.115a.a7e9)
  Description: Telstra_Fibre
  Internet address is
  MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full Duplex, 1Gbps, media type is RJ45
  output flow-control is unsupported, input flow-control is unsupported
  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 never
  Input queue: 48/75/59/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 1755000 bits/sec, 199 packets/sec
  5 minute output rate 279000 bits/sec, 140 packets/sec
     278556002 packets input, 4068943737 bytes, 0 no buffer
     Received 0 broadcasts (0 IP multicasts)
     0 runts, 0 giants, 14 throttles
     119926 input errors, 0 CRC, 0 frame, 119926 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     195992190 packets output, 774120162 bytes, 0 underruns
     0 output errors, 0 collisions, 2 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     1 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

2 Replies 2


input errors and overruns...are you actually experiencing performance problems ? The input errors and overruns usually mean that the router cannot handle incoming packets fast enough.

A simple shaping policy like the one below could remedy this. I don't know what the subscribed bandwidth is you have with Telstra, but let's assume it is 250MB.

policy-map Shape_Out
 class class-default
  shape average 250000000

and apply it to the interface:

interface GigabitEthernet0/1
 service-policy Shape_Out out

Hi Paul,

Input errors could be generated by a bad cable or duplex mismatch, also I see 1 lost carrier error. Clear the counters and see if the counting stops otherwise contact to your ISP to open a case and certify the cabling. The overrun can be mitigated applying a policy map as provided by Georg. 

>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<
Review Cisco Networking for a $25 gift card