Internet slow performance

Answered Question
Apr 4th, 2008
User Badges:

492905 packets output, 178423745 bytes, 0 underruns

9107 output errors, 22454 collisions, 0 interface resets

Correct Answer by thotsaphon about 8 years 12 months ago

Hi thiru,

As paolo said, You should use full-duplex. I still see Half-duplex in your show interface command so I'm not surprised at all why collision errors keep increasing.

CRC should be a layer1-problem to me. If it keep increasing then you should replace the cable for testing. If the problem still occur I'd request ISP to get involved in.


Hopes this helps

Thot

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Loading.
paolo bevilacqua Fri, 04/04/2008 - 08:55
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

The connected device is set for full-duplex and this one to half. Change setting into or another so that they match.


Hope this helps, please rate post if it does!

thiru.vel10 Fri, 04/04/2008 - 10:45
User Badges:

Duplex settings changed but no luck . Still same status.

paolo bevilacqua Fri, 04/04/2008 - 10:56
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Seem strange, for example once full duplex on cisco, it would never show any collision.

thiru.vel10 Fri, 04/04/2008 - 11:25
User Badges:

F0/1 is directly connected to internet modem. In modem they are setting half duplex. So we have configured the same in our f0/1 interface. I am trying to ping the ISP gate way form r1 is success rate is 100 percent (5/5), round-trip min/avg/max = 4/4/4 ms. My users are facing slow performance issue while accessing the internet application.




MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,

reliability 253/255, txload 8/255, rxload 14/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 10Mb/s, 100BaseTX/FX

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 00:59:45

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 569000 bits/sec, 115 packets/sec

5 minute output rate 349000 bits/sec, 125 packets/sec

263398 packets input, 151321672 bytes

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

88 input errors, 84 CRC, 0 frame, 0 overrun, 1 ignored

0 watchdog

0 input packets with dribble condition detected

259264 packets output, 83943118 bytes, 0 underruns

3587 output errors, 14189 collisions, 3 interface resets

0 babbles, 3587 late collision, 0 deferred

0 lost carrier, 0 no carrier

0 output buffer failures, 0 output buffers swapped out

paolo bevilacqua Fri, 04/04/2008 - 16:37
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Slow performance ? You're doing 570 kbos download and 350 upload, that is not little for broadband access. Check if you have concurrent P2P or video downloads users.


Admittedly the output errors ratio is a bit high, and some input errors. Check cabling and possibly replace it. A better choice, put a DSL interface directly into the router to solve any issue.

thiru.vel10 Sun, 04/06/2008 - 00:53
User Badges:



I have checked the Bandwidth in and out Utilization but it seems not that much. There is no user now but still I am getting the same error in internet interface.


Correct Answer
thotsaphon Sun, 04/06/2008 - 03:22
User Badges:
  • Gold, 750 points or more

Hi thiru,

As paolo said, You should use full-duplex. I still see Half-duplex in your show interface command so I'm not surprised at all why collision errors keep increasing.

CRC should be a layer1-problem to me. If it keep increasing then you should replace the cable for testing. If the problem still occur I'd request ISP to get involved in.


Hopes this helps

Thot

thiru.vel10 Mon, 04/07/2008 - 03:47
User Badges:

Thanks I have reported this issue with ISP. There are working on this issue. For your information I have replace the cable also. I am suspecting problem with ISP.

Actions

This Discussion