I have a Cisco 1600 router on a dsl, in this week, is getting slow browsing in internet, my ISP, say that i get some crs or somethig like that, and some collisions on my side, I really have a litle knowledge of cisco commands,what can i do !
hi, hjm, i can´t copy all the pages that come after type the command show tech-support, in telnet, how come i copy all the pages one after another, sorry, and by the way,
you know how can reset my couters,!
by the way this morning the service is fine and fast, but i cant tell in a hour or some thig. here yoe have the result of that commnad in telnet.
----------------------------------------------------------------
User Access Verification
------------------ show version ------------------
Cisco Internetwork Operating System Software
IOS (tm) 1600 Software (C1600-Y-M), Version 12.1(3)T, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Tue 18-Jul-00 22:56 by ccai
Image text-base: 0x02005000, data-base: 0x025D8BE4
ROM: System Bootstrap, Version 12.0(3)T, RELEASE SOFTWARE (fc1)
ROM: 1600 Software (C1600-RBOOT-R), Version 12.0(3)T, RELEASE SOFTWARE (fc1)
Company uptime is 16 hours, 24 minutes
System returned to ROM by power-on
System image file is "flash:c1600-y-mz.121-3.T"
cisco 1601 (68360) processor (revision C) with 9728K/512K bytes of memory.
Processor board ID 26437977, with hardware revision 00000005
Bridging software.
X.25 software, Version 3.0.0.
1 Ethernet/IEEE 802.3 interface(s)
1 Serial(sync/async) network interface(s)
System/IO memory with parity disabled
8192K bytes of DRAM onboard 2048K bytes of DRAM on SIMM
System running from RAM
7K bytes of non-volatile configuration memory.
6144K bytes of processor board PCMCIA flash (Read/Write)
Configuration register is 0x2102
------------------ show running-config ------------------
------------------ show stacks ------------------
Minimum process stacks:
Free/Size Name
756/1000 c1000 LED
2028/4000 Init
3412/4000 RADIUS INITCONFIG
4156/5000 DHCP Client
Interrupt level stacks:
Level Called Unused/Size Name
4 1717490 1744/3000 CPIC interrupts
7 0 2976/3000 Programmable Interval Timer
------------------ show interfaces ------------------
Ethernet0 is up, line protocol is up
Hardware is QUICC Ethernet, address is 000x.xx0x.0xxx (xxxx 000x.xx0x.0xxx)
Description: connected to EthernetLAN
Internet address is xx.xx.xx.xx/xx
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
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
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 1/75, 0 drops
5 minute input rate 10000 bits/sec, 13 packets/sec
5 minute output rate 6000 bits/sec, 6 packets/sec
119901 packets input, 13976797 bytes, 0 no buffer
Received 50505 broadcasts, 0 runts, 0 giants, 0 throttles
4 input errors, 2 CRC, 2 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
40272 packets output, 14281659 bytes, 0 underruns(131/585/0)
3 output errors, 716 collisions, 1 interface resets
0 babbles, 3 late collision, 1028 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Serial0 is up, line protocol is up
Hardware is QUICC Serial
Description: connected to Internet
Internet address is xxxx.xx.xxxx.xxx/xx
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 223/255, txload 31/255, rxload 23/255
Encapsulation HDLC, loopback not set
Keepalive set (10 sec)
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 2/75, 0 drops
30 second input rate 6000 bits/sec, 6 packets/sec
30 second output rate 8000 bits/sec, 11 packets/sec
70553 packets input, 15744561 bytes, 0 no buffer
Received 6414 broadcasts, 0 runts, 1 giants, 0 throttles
1379811 input errors, 520802 CRC, 264039 frame, 0 overrun, 0 ignored, 59497
0 abort
107889 packets output, 10130693 bytes, 0 underruns
0 output errors, 0 collisions, 46 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
------------------ show controllers ------------------
I have copied a few significant lines from the Show Tech, the come from the Serial 0 Interface statistics:
reliability 223/255, txload 31/255, rxload 23/255
This is a 1 byte reliability metric. It has a value of 0 - 255 with 255 being perfect. you have a value of 223. This is calculated from the quantity of data seen on the Interface, and the quantity of damaged data seen on the interface. You are seeing roughly a 10% loss of data. If you look at the way TCP/IP handles data loss you will understand that a 10% loss of packets could result in an exponentially larger loss of performance.
1379811 input errors
This is the total count of errors (bad frames) that have com in on the interface. This is a total of all the errors I will list below
520802 CRC
This incriments by 1 every time a packet comes in on the Interface that is corrupt or dammaged. These pactets are dropped after they are found to be bad
264039 frame
This incriments by 1 every time a packet comes in on the interface that does not appear to be aligned properly with the timing signal
594970 abort
This counter incriments by 1 every time the interface aborts trying to recieve a packet due to problems.
That is the end of the input errors
There is another indication of a line problem:
46 interface resets
I will past in Cisco's explanation as it is easier than typing it.
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
It should be noted that there are no carrier transitions. A carrier transition happens when the interface no longer sees the line available.
Summary:
I think you were correct to try replacing the cable, I would also recomend that you present this data to your provider and ask them to do line diags.
thanks, Jay ,
I already change the utp cable, from the cisco to the switch, but the other cable v35, only the isp has a replace for it, and hope the inetrnet still fast, and wait to my isp, to read all my lines.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.