Hi All,
I have an 8 port PA-8T serial card in a router. The card has an
octopus cable that is plugged into a rack of card DSU's. Most
of the DSU's have T1's into them.
One T1 has developed a problem where it runs for a few hours
and then the router serial interface it is on goes down.
If I simply assign something like IP 127.0.0.5/30 to the port and
throw a ton of traffic to 127.0.0.6, will the packets actually
go out the port? Or will the router see that the port is looped
and just discard the traffic?
From the router running extended pings to the 127.0.0.5 address
Is it a Verizon circuit?
We have a T1 circuit with Verizon and have the same problem. We have a
point to point circuit, so one side has clocking set to internal to provide
the clocking and the other side feeds from the line.
I wrote the problem up at http://ccie-security.blogspot.com/
But
Just because its a point to point circuit doesn't mean one side has to
have internal clocking. This is only true if the circuit is copper all
the way. There are lots of reasons that the telco would have its own
equipment installed on the circuit and you would need network timing.
Roy
Luan
On Wednesday 15 October 2008 10:22:17 Luan Nguyen wrote:
Is it a Verizon circuit?
We have a T1 circuit with Verizon and have the same problem. We have a
point to point circuit, so one side has clocking set to internal to provide
the clocking and the other side feeds from the line.
Have you
It's on fiber. I asked if we could get network timing from them, but they
said no, not on this type of circuit.
Also, this circuit has been working for years with the same setting :)
Luan Nguyen
Chesapeake NetCraftsmen, LLC.
www.NetCraftsmen.net
-Original Message-
From: [EMAIL
They claimed they don't provide clocking on point to point circuit...not
even for testing sake! We did played around with both side getting network
timing, with switching the side providing clocking, with both going
internal...etc, but nothing worked. It only works for some hours after they
-Original Message-
From: Brian Turnbow [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 6:50 AM
To: Ted Mittelstaedt; cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] OK, what is a cheap and dirty hack to test a port
If I simply assign something like IP
-Original Message-
From: Luan Nguyen [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 7:22 AM
To: 'Ted Mittelstaedt'; cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] OK, what is a cheap and dirty hack to test a port
Is it a Verizon circuit?
We have a T1 circuit with
Most modern sonet gear does not provide clocking to individual DS1s
running it. The only reason clocking ever existed on point to point
circuits was that the older gear couldn't avoid being an active
participant in the circuit. It's possible the carrier you're using has
upgraded the equipment, and
Ted Mittelstaedt wrote:
My question, is there a way I can configure the router port
so that I can throw a massive amount of (bogus, naturally)
traffic to it, and the traffic will go out the port, through the
DSU, loopback through the hard loopback plug, then come back
into the router and go
Paul,
Thanks.
We do have one side set to internal and the other to line and did forget
about it for years.
I believe one side of our circuit is encapsulated in a DS3, since one tester
said they couldn't loop since they had to loop the whole DS3.
The other side must be just a regular T1 and they
-Original Message-
From: Ted Mittelstaedt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2008 12:01 PM
To: Luan Nguyen; cisco-nsp@puck.nether.net
Subject: RE: [c-nsp] OK, what is a cheap and dirty hack to test a port
-Original Message-
From: Luan Nguyen [mailto:[EMAIL
On Oct 15, 2008, at 9:35 AM, Roy wrote:
Just because its a point to point circuit doesn't mean one side has to
have internal clocking. This is only true if the circuit is copper
all
the way. There are lots of reasons that the telco would have its own
equipment installed on the circuit
14 matches
Mail list logo
