08-19-2008 06:54 AM - edited 03-03-2019 11:11 PM
Good morning,
Our company is using Gigabit Ethernet interface to connect to our ISP, which rate limit 155 Mbps.
Although we're able to connect to them, but we have high input errors and input overrun, but zero output errors and overrun.
Attached documents consist of:
show version
show interface gigabitEthernet 0/3
show controllers gigabitEthernet 0/3
Any advices for above case?
-zamri-
meow#show interface gigabitEthernet 0/3
GigabitEthernet0/3 is up, line protocol is up
Hardware is BCM1250 Internal MAC, address is X (bia X)
Description: * PNC *
Internet address is A.B.C.D/30
MTU 1500 bytes, BW 1550000 Kbit, DLY 10 usec,
reliability 255/255, txload 21/255, rxload 15/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is RJ45
output flow-control is XON, input flow-control is XON
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 4d04h
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 93616000 bits/sec, 16967 packets/sec
5 minute output rate 127934000 bits/sec, 20304 packets/sec
3722461450 packets input, 346372024 bytes, 0 no buffer
Received 18 broadcasts, 0 runts, 0 giants, 0 throttles
4294967287 input errors, 0 CRC, 0 frame, 694331 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
679357412 packets output, 2554237425 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 pause output
0 output buffer failures, 0 output buffers swapped out
08-19-2008 09:36 AM
Hello Zamri,
first of all verify the following:
if IP CEF is enabled on gi0/3 or post a filtered version of sh run gi0/3
Are you using gi0/1 and gi0/2 because they are all managed by the NPE-G1 ?
Are you using all the 9 serial interfaces ?
here are the meaning of the errors:
input error Includes runts, giants, no buffer, CRC, frame, overrun, and
ignored counts. Other input-related errors can also cause the
input error count to be increased, and some datagrams may
have more than one error; therefore, this sum may not balance
with the sum of enumerated input error counts.
overrun Shows the number of times that the receiver hardware was
incapable of handing received data to a hardware buffer
because the input rate exceeded the receiver's capability to
handle the data.
Hope to help
Giuseppe
08-20-2008 10:56 AM
I had a similar issue with the NPE-G1 interface, although my input error to overrun ratio was 1-1, whereas you have a lot more input errors. There is a bug where if you have an input service-policy then the processing that takes causes the overruns. Take off the input service-policy and the overruns drop dramatically.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide