I have two Cisco 2620 routers connected via T1 between offices and the users in the remote office started to complain of the speed on Tuesday. I checked and saw they were indeed correct and the connection seems to have slowed down significantly. I am new to this installation and am still trying to figure out what all the connections throughout the company are so I ran the Cisco ConfigMaker and had it look up the devices. The remote device came back and it seemed to have recognized everything in the configuration but the local router did not show the T1 interface. I tried pinging from the remote site (via PCAnywhere) and the average times were around 60ms while pinging from the local site times were <10ms. Any help as to where to go from here would be appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
T1 line slowed down
- Thread starter techshoot
- Start date
the local router you stated that you can not see the t1 interface card. Do a
( sh ver ) and look into your hardware.
what does your config look like? Point-to-point is easy we should have you back up in no time given there is not an actual hardware issue.
Try a shutdown on the interface and a no shut Jeter@LasVegas.com
J.Fisher CCNA
( sh ver ) and look into your hardware.
what does your config look like? Point-to-point is easy we should have you back up in no time given there is not an actual hardware issue.
Try a shutdown on the interface and a no shut Jeter@LasVegas.com
J.Fisher CCNA
- Thread starter
- #3
Below is the results of a "sh ver" command. I had already done a restart and then today did a power down restart and have the same situation.
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-IS-M), Version 12.0(5)XK, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
TAC:Home:SW:IOS:Specials for info
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 22-Jul-99 05:15 by linda
Image text-base: 0x80008088, data-base: 0x80B88420
ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
ROM: C2600 Software (C2600-IS-M), Version 12.0(5)XK, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
router uptime is 1 week, 1 hour, 12 minutes
System returned to ROM by power-on
System image file is "flash:c2600-is-mz.120-5.XK.bin"
cisco 2620 (MPC860) processor (revision 0x101) with 39936K/9216K bytes of memory.
Processor board ID JAB033203PZ (3140175221)
M860 processor: part number 0, mask 49
Bridging software.
X.25 software, Version 3.0.0.
Primary Rate ISDN software, Version 1.1.
1 FastEthernet/IEEE 802.3 interface(s)
2 Serial network interface(s)
2 Channelized T1/PRI port(s)
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read/Write)
Configuration register is 0x2102
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-IS-M), Version 12.0(5)XK, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
TAC:Home:SW:IOS:Specials for info
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Thu 22-Jul-99 05:15 by linda
Image text-base: 0x80008088, data-base: 0x80B88420
ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
ROM: C2600 Software (C2600-IS-M), Version 12.0(5)XK, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
router uptime is 1 week, 1 hour, 12 minutes
System returned to ROM by power-on
System image file is "flash:c2600-is-mz.120-5.XK.bin"
cisco 2620 (MPC860) processor (revision 0x101) with 39936K/9216K bytes of memory.
Processor board ID JAB033203PZ (3140175221)
M860 processor: part number 0, mask 49
Bridging software.
X.25 software, Version 3.0.0.
Primary Rate ISDN software, Version 1.1.
1 FastEthernet/IEEE 802.3 interface(s)
2 Serial network interface(s)
2 Channelized T1/PRI port(s)
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read/Write)
Configuration register is 0x2102
debug , debug, debug.
The link wasn't actually down; it's just slow: restart and
then run debug serial packet, and then move up through the
debug events looking for problems; set up logging if possible, or use snmp to keep an eye over a period of time and set traps for slowdowns.
Just basic tshooting.
What is the link encapsulation?
The link wasn't actually down; it's just slow: restart and
then run debug serial packet, and then move up through the
debug events looking for problems; set up logging if possible, or use snmp to keep an eye over a period of time and set traps for slowdowns.
Just basic tshooting.
What is the link encapsulation?
- Thread starter
- #5
Since there was data communications, I figured the link wasn't down but something was slowing it. I am completely new to Cisco routers and the technology so please bear with me. I believe can figure how to do logging, though not certain what to log and do not understand "link encapsulation" and how to find or decypher any results. I did realize that the same day the problem began the telephone PBX service man was there doing work on their end of the T1 link and when I ran Cisco ConfigMaker it could not fint the T1 interface at the local office but found it in the remoter configuration.
your last statement the telephone pbx was on site would not indicate why the span would slow down. I would go with the info already given run your debug test and or check out the csu/dsu the cisco and the pbx is setup on. Check the parameters on the csu/dsu. Jeter@LasVegas.com
J.Fisher CCNA
J.Fisher CCNA
- Status
Similar threads
- Locked
- Question