capraez
asked on
PPP Connection from Atlanta to Charlotte drops daily
We have a ppp connection from Atlanta to Charlotte provided by USLec that loses connection daily. I've switched out the WIC card and Serial card for the PPP interface on the Atlanta router in hopes it would correct the problem. I no longer think this is hardware related but more of a configuration issue. I need help in auditing our router scripts to determine the problem. Here is the scenario:
4/15/2005 : Atlanta router configuration script lost. Not sure of cause. Rebuild script pretty close to what we had previously.
4/16/2005: Atlanta to Charlotte PPP dropped. Atlanta T1 Internet fine.
4/17/2005 – 4/20/2005: Atlanta to Charlotte PPP drops every 9 hours. We power down both routers, power charlotte router back up first then power Atlanta router. We average 3 attempts to keep the connection. The first 2 attempts the connection drops within 2-3 minutes.
4/20/2005 evening: Removed Atlanta WIC card with Serial Interface 1/0, this is the PPP WIC. Replaced WIC with a brand new WIC. PPP Connection down.
4/21/2005: Reset both routers at 7:20am. PPP Connection stays up for about 16-18 hours.
4/22/2005: 7:30am Shut down the Atlanta router and had to reboot the Charlotte router. After Charlotte came up, booted up Atlanta. Circuit stay up about 2 to 3 minutes.7:45 I had remote employee reboot the Charlotte router and it came up and the circuit has been up since that time.
4/22/2005 evening: 5:15pm. Connection drops again, purchase new serial interface card swap out old one in Atlanta router. Connection comes right back up, things start to look good.
4/23/2005: Connection drops again.
4/25:2005: Ready to blow up the router.
Throughout this entire problem the Atlanta Internet Connection is just fine. It has not dropped or given us any problems.
4/15/2005 : Atlanta router configuration script lost. Not sure of cause. Rebuild script pretty close to what we had previously.
4/16/2005: Atlanta to Charlotte PPP dropped. Atlanta T1 Internet fine.
4/17/2005 – 4/20/2005: Atlanta to Charlotte PPP drops every 9 hours. We power down both routers, power charlotte router back up first then power Atlanta router. We average 3 attempts to keep the connection. The first 2 attempts the connection drops within 2-3 minutes.
4/20/2005 evening: Removed Atlanta WIC card with Serial Interface 1/0, this is the PPP WIC. Replaced WIC with a brand new WIC. PPP Connection down.
4/21/2005: Reset both routers at 7:20am. PPP Connection stays up for about 16-18 hours.
4/22/2005: 7:30am Shut down the Atlanta router and had to reboot the Charlotte router. After Charlotte came up, booted up Atlanta. Circuit stay up about 2 to 3 minutes.7:45 I had remote employee reboot the Charlotte router and it came up and the circuit has been up since that time.
4/22/2005 evening: 5:15pm. Connection drops again, purchase new serial interface card swap out old one in Atlanta router. Connection comes right back up, things start to look good.
4/23/2005: Connection drops again.
4/25:2005: Ready to blow up the router.
Throughout this entire problem the Atlanta Internet Connection is just fine. It has not dropped or given us any problems.
Sounds like a circuit timing issue. If this is p2p T1, then one end should be providing clocking.
Do you have this on one end?
interface serial 1/0
service-module T1 clock source internal
The other end should be default clock source line, which won't show up in the config...
Do you have any error counts with "show interface serial 1/0"
Do you have this on one end?
interface serial 1/0
service-module T1 clock source internal
The other end should be default clock source line, which won't show up in the config...
Do you have any error counts with "show interface serial 1/0"
ASKER
I set the Atlanta router to:
service-module t1 clock source internal
I set the Charlotte router to:
service-module t1 clock source line
After doing that we could not get the routers to communicate. We rebooted the atlanta router first then rebooted charlotte router. They still would not synch up.
I then tried the following settings:
Atlanta: service-module t1 clock line
Charlotte: service-module t1 clock internal
The line came back up immediately without rebooting. This is working for right now. I cleared the counters on both ends and waited 10 minutes and received no errors on either side.
The weird part is when I do a "show clock detail" on either router it displays: "no time source"
I'm also monitoring an extending ping from atlanta to charlotte. the reply times are <10ms sometimes and then jump from 15ms to 16ms back to <10ms. We'll see how long this will hold up.
service-module t1 clock source internal
I set the Charlotte router to:
service-module t1 clock source line
After doing that we could not get the routers to communicate. We rebooted the atlanta router first then rebooted charlotte router. They still would not synch up.
I then tried the following settings:
Atlanta: service-module t1 clock line
Charlotte: service-module t1 clock internal
The line came back up immediately without rebooting. This is working for right now. I cleared the counters on both ends and waited 10 minutes and received no errors on either side.
The weird part is when I do a "show clock detail" on either router it displays: "no time source"
I'm also monitoring an extending ping from atlanta to charlotte. the reply times are <10ms sometimes and then jump from 15ms to 16ms back to <10ms. We'll see how long this will hold up.
ASKER
Below is the detail of the clocks:
Atlanta Router:
corp-rou#sho clock detail
01:54:06.911 UTC Mon Apr 25 2005
Time source is user configuration
Charlotte Router:
CHAR-ROU#sho clock detail
*00:55:14.011 UTC Mon Mar 1 1993
Atlanta Router:
corp-rou#sho clock detail
01:54:06.911 UTC Mon Apr 25 2005
Time source is user configuration
Charlotte Router:
CHAR-ROU#sho clock detail
*00:55:14.011 UTC Mon Mar 1 1993
ASKER
This is what the extended ping looks like:
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=31ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=15ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=15ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=31ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=31ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=15ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=15ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=31ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time=16ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
Reply from 10.10.40.1: bytes=32 time<10ms TTL=254
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER