Re: buffers, input errors, hardware or traffic issue.

rungemach · ‎01-19-2006

Stumped and no one has an answer!

Errors that stall-out the router!

I am at a loss, we have done everything we can think of at this point, layer 1, cable, doubled DRAM to 512K, updated to latest code. Removed BGP and went to static routing. Below is the sh interface. Netflow show that the traffic going through the router is port 25. A larger than normal burst but no larger than 25mbps whihc is well under the line speed of 100mbps.

I need help fast, this has been going on for > week. TAC is stumped as well as CISCO SE.

inetrouter2#sh int

GigabitEthernet0/0 is up, line protocol is up

Hardware is MV96340 Ethernet, address is 000f.352e.d281 (bia 000f.352e.d281)

Description: Inside Interface$FW_INSIDE$

Internet address is xxx.xxx.xxx.xxx /24

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 24/255, rxload 9/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, media type is T

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 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 3672000 bits/sec, 1276 packets/sec

5 minute output rate 9472000 bits/sec, 1579 packets/sec

91728321 packets input, 3448573575 bytes, 0 no buffer

Received 4399 broadcasts, 0 runts, 0 giants, 0 throttles

152889 input errors, 0 CRC, 0 frame, 0 overrun, 152893 ignored

0 watchdog, 0 multicast, 0 pause input

0 input packets with dribble condition detected

102913439 packets output, 314532730 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 158076 pause output

0 output buffer failures, 0 output buffers swapped out

GigabitEthernet0/1 is up, line protocol is up

Hardware is MV96340 Ethernet, address is 000f.352e.d282 (bia 000f.352e.d282)

Description: $ETH-WAN$Outside Interface$FW_OUTSIDE$

Internet address is xxx.xxx.xxx.xxx /29

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 9/255, rxload 24/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Full-duplex, 100Mb/s, media type is T

output flow-control is XON, input flow-control is XON

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:01, output 00:00:00, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/4/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 9416000 bits/sec, 1571 packets/sec

5 minute output rate 3643000 bits/sec, 1274 packets/sec

103609259 packets input, 94232125 bytes, 0 no buffer

Received 502 broadcasts, 0 runts, 0 giants, 3 throttles

118025 input errors, 0 CRC, 1 frame, 0 overrun, 118025 ignored

0 watchdog, 0 multicast, 0 pause input

0 input packets with dribble condition detected

91797436 packets output, 3136134715 bytes, 0 underruns

0 output errors, 0 collisions, 2 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 132446 pause output

0 output buffer failures, 0 output buffers swapped out

Mikhail.Galiulin · ‎01-20-2006

Hi,

Do you have speed/duplex parameters for both interfaces in autonegotiation mode on both sides?

If so try to change it to statically configured 100 Full-duplex. It should be done not only on router but also on switches (or other equipment) which connected to the ports.

//Mikhail Galiulin

rungemach · ‎01-20-2006

I was hoping it would have been that simple, but alas, all intefaces are set for 100/full. All interfaces are reporting connected at 100/full

Mikhail.Galiulin · ‎01-23-2006

What type of equipment do you use on "the other side". Could you send the similar statistic from it.

It would be good if you can also attach routers config.

//Mikhail Galiulin

rungemach · ‎01-23-2006

This is an internet facing device, there is no other side other than UUNet's equipment. We replaced the router on Friday, since then the errors are gone. This was a 2821 and we did purchase at the very beginning of the release. I noticed that there have been modifications to the board since then. Most importantly, the error has not reappeared for more than 72 hours. Prio to RMA on equipment we were having issues within just a couple of hours.