connection problem. [7:65491]
Priscilla Oppenheimer wrote:
I logged into the routers and did some ping tests, pinging the
routers own serial interface I still get the 1% packet loss.
It may surprise you to learn that when you ping from a router's
serial interface to the router's own
I was wondering if an extended ping with a high zero density (0x) could
reveal something (maybe a line encoding issue.
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=65688t=65491
--
FAQ, list archives, and subscription info:
Hello all,
I am a collegue of Mark's who has been working on this fault over the
weekend with Mark.
We have done some further tests today and we are still experiencing errors
on the line, here are some of the results we have seen:
1.) Each time we have changed the clocking on the line, we have
Stephen,
Also, what has the carrier told you about this circuit? Most
carrier-class transport equipment can report the types of errors being
incurred and where they first appear in the network. For instance, coding
violations, framing errors/violations, simple FCS failure, etc.
Also, did your
Stephen,
Thanks for the update. It sounds as if this circiut is not back-to-back.
Since there is a carrier involved, you might want to think about how the
service might be provisioned. For example, the carrier may have all the
transport equipment set up to accept a channelized DS3 and you
Thanks,
We will speak to the Carrier today and find out what their configuration is.
We have 3 other DS3 45mbps circuits on the Network connecting through
another Carrier and we are NOT seeing the same problems.
I'll keep you updated.
Thanks
Stephen
s vermill wrote:
Stephen,
Thanks for
Priscilla Oppenheimer wrote:
I logged into the routers and did some ping tests, pinging the
routers own serial interface I still get the 1% packet loss.
It may surprise you to learn that when you ping from a router's
serial interface to the router's own serial interface, the
packets
As others are saying, get the carrier involved. Do some loopbacks with
their
help. (Do loopbacks still make sense with DS3? I've only worked with DS1).
Regardless, I think you've done the requisite testing and swapping on your
side. Time to hassle the carrier.
I haven't been reading
As others are saying, get the carrier involved. Do some loopbacks with
their
help. (Do loopbacks still make sense with DS3? I've only worked with DS1).
Regardless, I think you've done the requisite testing and swapping on your
side. Time to hassle the carrier.
I haven't been reading
Darrell Newcomb wrote:
As others are saying, get the carrier involved. Do some
loopbacks with
their
help. (Do loopbacks still make sense with DS3? I've only
worked with DS1).
Regardless, I think you've done the requisite testing and
swapping on your
side. Time to hassle the carrier.
Hi Again Everyone,
Just to let you all know, this morning I changed the 7200 router serial
interface clock to int and left the 7500 clock set to line, this actually
made the connection worse, I got 5% packet loss as opposed to 1% packet loss
when both router interfaces were set to line, I changed
could be a problem as well.
Of course, everything I have said could absolutely be obsoleted by the damn
PA being bad, but it doesn't sound like it is bad.
Thanks,
Jim
- Original Message -
From: Mark Walmsley
To:
Sent: Sunday, March 16, 2003 5:16 AM
Subject: RE: DS3 slow connection problem
Hi Jim,
Here's the output you wanted. I was thinking about the cablelength so I
might give it a try in the morning becaause it looks to me like more than 10
feet but not alot more perhaps 15-20, Also, the wiring was previously
working fine in the same place but conected to a converter then into
Mark Walmsley wrote:
Hi Again Everyone,
Just to let you all know, this morning I changed the 7200
router serial interface clock to int and left the 7500 clock
set to line, this actually made the connection worse, I got 5%
packet loss as opposed to 1% packet loss when both router
Mark,
Saying that THE problem is one thing or another is always dangerous (and,
frankly, a little unprofessional). I should have said that A problem is
that you didn't have a clock source on the line. You need at least one.
Two doesn't hurt either (both can be internal). There may well be
clear the counters on both routers and find out the rate of new error
accumulation.
check the interface after say 5 mins and see if you get new more errors and
we can take it from there.
check the controllers for errors too.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL
: DS3 slow connection problem. [7:65491]
clear the counters on both routers and find out the rate of new error
accumulation.
check the interface after say 5 mins and see if you get new more errors
and
we can take it from there.
check the controllers for errors too.
-Original Message-
From
Thanks Spio,
I've cleared the counters for show int and noticed that the input errors
are showing up on the 7200 and not on the 7500 which might make things a bit
clearer, the counters hadn't been cleared since installation so the 7500
input errors might have been from when it was first brought
Mark,
Your problem is that both routers are set to recover timing from the line.
Telcos don't generally provide timing for DS3s, so you'll need to set one
router for internal clock.
A lot of folks that work with T1s know that telcos can and do provide timing
for those lower-rate circuits. How
issue the show buffers command to see if the counter
of misses and failed is incrementing. In this case
tune the buffer according to the size of packets u
receive.
Input errors overrun and underrun errors showed in ur
output are linked to buffer allocation problem.
--- Spio Wagus wrote:
clear
and connectors.. Did you change them?...
mustafa
-Original Message-
From: Spio Wagus [mailto:[EMAIL PROTECTED]
Sent: Saturday, March 15, 2003 5:18 PM
To: [EMAIL PROTECTED]
Subject: RE: DS3 slow connection problem. [7:65491]
clear the counters on both routers and find out the rate of new
, March 15, 2003 8:54 AM
Subject: RE: DS3 slow connection problem. [7:65491]
That' right...
But for me any reliability value less than 255/255 is a line problem..
check the cables and connectors.. Did you change them?...
mustafa
-Original Message-
From: Spio Wagus [mailto:[EMAIL
s vermill wrote:
Mark,
Your problem is that both routers are set to recover timing
from the line. Telcos don't generally provide timing for DS3s,
so you'll need to set one router for internal clock.
Wow. I'm impressed that you pinpointed the problem, unlike those of us who
copied and
Brilliant! Thanks everyone. I'm going to work on it in the morning and i'll
let you know how I get on.
Mark.
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=65523t=65491
--
FAQ, list archives, and subscription info:
24 matches
Mail list logo
