1811 intermittent connection problems 1

[keebe418]

We recently up'd our bandwidth to a 3 meg ethernet fiber line. I set up this 1811 and for the most part it has worked great.

Lately though the internet drops out through this router. I am able to do a quick fix by power cycling the device during normal hours. Otherwise, I am not sure if this has anything to do with it, but it constantly spits out late collision errors like the following:

00:12:34: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
00:12:38: %GT96K_FE-5-LATECOLL: Late Collision on int FastEthernet0/0
00:12:39: %GT96K_FE-5-LATECOLL: Late Collision on int FastEthernet0/0
00:12:40: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up
00:12:49: %GT96K_FE-5-LATECOLL: Late Collision on int FastEthernet0/0
00:12:51: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up

Here is the sh conf and sh int f0/0:

Using 1619 out of 196600 bytes
!
version 12.4
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname Bergquist_TOL
!
boot-start-marker
boot-end-marker
!
logging buffered 51200 warnings
enable password 7 094E4B1B1E414316065D0A
!
no aaa new-model
!
resource policy
!
clock timezone PCTime -5
clock summer-time PCTime date Apr 6 2003 2:00 Oct 26 2003 2:00
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
ip subnet-zero
ip cef
!
!
no ip dhcp use vrf connected
!
!
no ip domain lookup
!
!
!
!
interface FastEthernet0/0
 description Buckeye Ethernet
 ip address x.x.x.x 255.255.255.252
 no ip mroute-cache
 speed 100
 half-duplex
 fair-queue
!
interface FastEthernet0/1
 description connected to EthernetLAN$ES_LAN$
 ip address x.x.x.x 255.255.255.248
 duplex auto
 speed auto
!
interface Serial0/0/0
 no ip address
 no ip mroute-cache
 shutdown
 half-duplex
 fair-queue
 service-module t1 timeslots 1-24
 service-module t1 remote-alarm-enable
!
ip classless
ip route 0.0.0.0 0.0.0.0 x.x.x.x
ip route x.x.x.x 255.255.255.248 FastEthernet0/1
!
ip http server
ip http authentication local
ip http timeout-policy idle 60 life 86400 requests 10000
!
!
control-plane
!
banner login ^CBergquist authorized access only!
  Disconnect IMMEDIATELY if you are not an authorized user for this equipment!^C
!
line con 0
 login local
line aux 0
line vty 0 4
 privilege level 15
 login local
 transport input telnet
line vty 5 15
 privilege level 15
 login local
 transport input telnet
!
end

Bergquist_TOL#sh int f0/0
FastEthernet0/0 is up, line protocol is up
  Hardware is Gt96k FE
  Description: Buckeye Ethernet
  Internet address is x.x.x.x/30
  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)
  Half-duplex, 100Mb/s, 100BaseTX/FX
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:11, 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: weighted fair
  Output queue: 0/1000/64/0 (size/max total/threshold/drops)
     Conversations  0/2/256 (active/max active/max total)
     Reserved Conversations 0/0 (allocated/max allocated)
     Available Bandwidth 75000 kilobits/sec
  5 minute input rate 222000 bits/sec, 76 packets/sec
  5 minute output rate 138000 bits/sec, 81 packets/sec
     42925 packets input, 18712244 bytes
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog
     0 input packets with dribble condition detected
     43049 packets output, 12267502 bytes, 0 underruns
     56 output errors, 224 collisions, 60 interface resets
     0 babbles, 56 late collision, 0 deferred
     0 lost carrier, 0 no carrier
     0 output buffer failures, 0 output buffers swapped out

Any suggestions??

 

[brianinms]

May want to try setting the interface to auto speed and duplex

 

[keebe418]

I changed the speed and duplex and I am still receiving the late collision errors. I am assuming because this eth line transmits always in half-duplex is part of the reason for the collisions, since it should not happen in full-duplex, correct?

I could understand if it was just a few collisions. That is at least expected, but this is a constant stream of one late collision after the other and I wonder if this is what is cutting off our internet access through this router.

There are no extreme lengths of cabling, number of hubs, etc. So I am guessing I have a bad NIC somewhere.

Know of any helpful tools for monitoring where it may be coming from?

Thanks-
Shawn

 

[burtsbees]

56 output errors, 224 collisions, 60 interface resets

I would say the telco side...can you change it to 10/half and see? Have you called the telco/provider? Where are you located? The ice here has caused much havoc...

Burt

 

[keebe418]

Hi Burt-

Just for curiosity sake...What does changing it to 10/half do? We are in northwest OH. I have called the telco(Buckeye) and they have stated no issues on their end. I got a hold of a 2651 router last night to try so I can see if it is just a bad NIC on this 1841(not 1811 like I stated in the thread title).

I had heard of the ice causing some problems though so it may be worth looking into again if this 2651 router does not work.

-Shawn

 

[burtsbees]

You usually don't see 100MBps at half duplex---usually I thought it was 10...that's why I suggested it.
I would just connect the 1841 to the 2651 fastethernet ports (fa0/0 on the 1841) with a crossover and test it with different speed and duplex settings to eliminate the 1841 as a cause...what happens when you do an extended ping through the router? You can usually tell if it's flapping---all the resets indicate this. Late collisions usually mean a duplex mismatch.

Burt

 

[keebe418]

I agree that's why I questioned the original telco tech I spoke with when activating this line, but they stuck to the 100 half.

I called again this afternoon and spoke to their head NOC engineer. He found it was set incorrectly and should be 100 @ full. He mentioned it has issues with auto-duplex and speed so I manually set it to 100 full on our router and I have not received any errors for the past nearly 2 hours. (Whereas before I was receiving the collisions ever 10 seconds)

Thanks for the help!