<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I suppose it is possible that a DACS could introduce enough jitter
into the signal to keep the other system from deriving clock from
the line. This is not a problem in the general case though.<br>
<br>
<hr size="2" width="100%"><br>
<div class="moz-cite-prefix">On 10/9/2012 9:31 PM,
<a class="moz-txt-link-abbreviated" href="mailto:jfmays@launchpad.win.net">jfmays@launchpad.win.net</a> (Joe Mays) wrote:<br>
</div>
<blockquote cite="mid:1630FE1D0F6F45DE949F0A783E09B10F@mainbay"
type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19328">
<div><font face="Arial" size="2">
<div><font face="Arial" size="2">It has been suggested that if
those circuits go through a DAX, the clocking signal may
not be making it to the other system.</font></div>
</font></div>
<blockquote style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT:
5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<div style="FONT: 10pt arial">----- Original Message ----- </div>
<div style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color:
black"><b>From:</b> <a moz-do-not-send="true"
title="Aaron@cisco.com" href="mailto:Aaron@cisco.com">Aaron
Leonard</a> </div>
<div style="FONT: 10pt arial"><b>To:</b> <a
moz-do-not-send="true" title="mays@win.net"
href="mailto:mays@win.net">Joseph Mays</a> </div>
<div style="FONT: 10pt arial"><b>Cc:</b> <a
moz-do-not-send="true" title="cisco-nas@puck.nether.net"
href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a>
</div>
<div style="FONT: 10pt arial"><b>Sent:</b> Tuesday, October 09,
2012 7:00 PM</div>
<div style="FONT: 10pt arial"><b>Subject:</b> Re: [cisco-nas]
Slips</div>
<div><br>
</div>
The 5400 has only one clocking domain. So, if you are getting
clock from slot 6 port 0, then this is the time source for the
whole TDM bus. So, all other T1s on the 5400 will be
synchronized to that source, and anything that takes clock from
those T1s should be synchronized.<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a008014f8a6.shtml">http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a008014f8a6.shtml</a><br>
<br>
That's why I suspect that the system on the other side of T1 6/1
is not actually taking clock from the line. Maybe it's free
running or maybe it's taking clock from something else.<br>
<br>
Aaron<br>
<br>
<hr size="2" width="100%"> <br>
<div class="moz-cite-prefix">On 10/9/2012 2:46 PM, <a
moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:mays@win.net">mays@win.net</a> (Joseph Mays)
wrote:<br>
</div>
<blockquote
cite="mid:4CEC500DF8EF4B37AC042E19C178B9B6@win2snvu0x4eg9"
type="cite">
<meta name="GENERATOR" content="MSHTML 8.00.6001.19328">
<style></style>
<div><font face="Arial" size="2">I would like to change port
6/1 to clocking internal, but I can't find any way change
the clocking on an individual t1 port controller to
internal. Am I missing something?</font></div>
<blockquote style="BORDER-LEFT: #000000 2px solid;
PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px;
MARGIN-RIGHT: 0px">
<div style="FONT: 10pt arial">----- Original Message ----- </div>
<div style="FONT: 10pt arial; BACKGROUND: #e4e4e4;
font-color: black"><b>From:</b> <a title="mays@win.net"
href="mailto:mays@win.net" moz-do-not-send="true">Joseph
Mays</a> </div>
<div style="FONT: 10pt arial"><b>To:</b> <a
title="Aaron@cisco.com" href="mailto:Aaron@cisco.com"
moz-do-not-send="true">Aaron Leonard</a> </div>
<div style="FONT: 10pt arial"><b>Cc:</b> <a
title="cisco-nas@puck.nether.net"
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true">cisco-nas@puck.nether.net</a> </div>
<div style="FONT: 10pt arial"><b>Sent:</b> Tuesday, October
09, 2012 4:48 PM</div>
<div style="FONT: 10pt arial"><b>Subject:</b> Re:
[cisco-nas] Slips</div>
<div><br>
</div>
<div><font face="Arial" size="2">Thank you for your
response.</font></div>
<div> </div>
<div><font face="Arial" size="2">Show tdm clocks shows the
AS5400 is using the circuit in port 6/0 for primary
clocking.</font></div>
<div> </div>
<div><font face="Courier New" size="2">Primary Clock:<br>
--------------<br>
System primary is slot 6 port 0 of priority 1<br>
TDM Bus Master Clock Generator State = NORMAL</font></div>
<div> </div>
<div><font face="Courier New" size="2">Backup clocks for
primary:<br>
Source Slot Port DS3-Port Priority Status
State<br>
-------------------------------------------------------------<br>
Trunk 1 1 YES 2 Good
Configured<br>
Trunk 1 2 YES 3 Good
Configured<br>
Trunk 1 3 YES 4 Good
Configured<br>
Trunk 1 4 YES 5 Good
Configured<br>
Trunk 1 5 YES 6 Good
Configured<br>
Trunk 6 1 NO 213 Good
Default<br>
Trunk 1 28 YES 202 Good
Default<br>
Trunk 1 27 YES 203 Good
Default</font></div>
<div> </div>
<div><font face="Courier New" size="2">Trunk cards
controllers clock health information<br>
------------------------------------------------<br>
CT3 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1<br>
Slot Port Type 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
9 8 7 6 5 4 3 2 1<br>
1 0 T3 G G G B B G G B B G B G B B B B B B B
B B B B G G G G G</font></div>
<div> </div>
<div><font face="Arial" size="2">We had considered the
possibility that the problem might be coming from the
mux that everything was passing through. I rewired the
pinouts from telco in order to connect them directly to
a t1 port on the AS5400 (Controller 6/1), rather than
passing them through the mux and coming across a channel
on the t3. It works, but the slips are exactly the same.</font></div>
<div> </div>
<div><font face="Arial" size="2">ArmoryPl-AS5400#show
controller t1 6/1<br>
T1 6/1 is up.<br>
Applique type is Channelized T1<br>
Cablelength is long gain36 0db<br>
Description: Leonard Brush MUX Bypass<br>
No alarms detected.<br>
alarm-trigger is not set<br>
Version info of slot 6: HW: 768, PLD Rev: 1<br>
Framer Version: 0x8</font></div>
<div> </div>
<div><font face="Arial" size="2">Manufacture Cookie Info:<br>
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x02,<br>
Board Hardware Version 3.0, Item Number 73-3996-03,<br>
Board Revision A0, Serial Number JAB044106K3,<br>
PLD/ISP Version <unset>, Manufacture Date
11-Oct-2000.</font></div>
<div> </div>
<div><font face="Arial" size="2"> Framing is ESF, Line Code
is B8ZS, Clock Source is Line.<br>
Data in current interval (638 seconds elapsed):<br>
0 Line Code Violations, 0 Path Code Violations<br>
54 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0
Degraded Mins<br>
54 Errored Secs, 0 Bursty Err Secs, 0 Severely Err
Secs, 0 Unavail Secs<br>
</font></div>
<div><font face="Arial" size="2">Right next to it is the
trunking circut plugged into 6/0, it runs fine, no
slips. I would like to change 6/1 to internal clocking,
btw, so that it should be following the clock that is
being derived on 6/0, but can't find anyway to change
that on the t1 ports. So as it stands right now, both
6/1 and the customer router on the other end of that t1
are set to clock-source line, with no mux between them.
And getting slips.</font></div>
<div> </div>
<div> </div>
<div><font face="Arial" size="2">----- Original Message
----- </font>
<div><font face="Arial" size="2">From: "Aaron Leonard"
<</font><a href="mailto:Aaron@cisco.com"
moz-do-not-send="true"><font face="Arial" size="2">Aaron@cisco.com</font></a><font
face="Arial" size="2">></font></div>
<div><font face="Arial" size="2">To: "Joseph Mays" <</font><a
href="mailto:jfmays@launchpad.win.net"
moz-do-not-send="true"><font face="Arial" size="2">jfmays@launchpad.win.net</font></a><font
face="Arial" size="2">></font></div>
<div><font face="Arial" size="2">Cc: <</font><a
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true"><font face="Arial" size="2">cisco-nas@puck.nether.net</font></a><font
face="Arial" size="2">></font></div>
<div><font face="Arial" size="2">Sent: Tuesday, October
09, 2012 3:21 PM</font></div>
<div><font face="Arial" size="2">Subject: Re: [cisco-nas]
Slips</font></div>
</div>
<div><font face="Arial"><br>
</font></div>
<font face="Arial" size="2">> Joe,<br>
> <br>
> Sounds like, conceptually, you've set things up
right. I would <br>
> doublecheck on the customer routers to make sure that
they really are <br>
> taking clock from the right T1 line.<br>
> <br>
> On the 5400, you should be using "tdm clock priority"
to set the clock <br>
> source, and "show tdm clocks" to validate the
clocking. <br>
> </font><a
href="http://www.cisco.com/en/US/docs/ios/12_3/dial/command/reference/dia_s6g.html#wp1140246"
moz-do-not-send="true"><font face="Arial" size="2">http://www.cisco.com/en/US/docs/ios/12_3/dial/command/reference/dia_s6g.html#wp1140246</font></a><br>
<font face="Arial" size="2">> <br>
> Aaron<br>
> <br>
> ----<br>
> <br>
> On 10/9/2012 8:43 AM, </font><a
href="mailto:jfmays@launchpad.win.net"
moz-do-not-send="true"><font face="Arial" size="2">jfmays@launchpad.win.net</font></a><font
face="Arial" size="2"> (Joseph Mays) wrote:<br>
>> It occurs to me that there is an assumption built
into this that is<br>
>> unproven. Does setting the AS5400 to internal
clocking on the T3 cause it to<br>
>> provide clocking for the T1's on the T3? We have
assumed that it does. If<br>
>> not, how do we tell it to provide an outgoing
clock signal for the T1's on<br>
>> the T3?<br>
>><br>
>> ----- Original Message -----<br>
>> From: "Joe Mays" <</font><a
href="mailto:mays@win.net" moz-do-not-send="true"><font
face="Arial" size="2">mays@win.net</font></a><font
face="Arial" size="2">><br>
>> To: "cisco-nsp" <</font><a
href="mailto:cisco-nsp@puck.nether.net"
moz-do-not-send="true"><font face="Arial" size="2">cisco-nsp@puck.nether.net</font></a><font
face="Arial" size="2">>; <</font><a
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true"><font face="Arial" size="2">cisco-nas@puck.nether.net</font></a><font
face="Arial" size="2">><br>
>> Sent: Tuesday, October 09, 2012 12:57 AM<br>
>> Subject: [cisco-nas] Slips<br>
>><br>
>><br>
>>> We have an AS5400 that we are using to
provide PRI's to customers. It has<br>
>>> the following circuits coming into it from
the Telco (AT&T).<br>
>>><br>
>>> 5 Trunking circuits that come across T1 ties
into a t3 mux, and then are<br>
>>> then delivered to a T3 port on the AS5400. !
trunking circuit that is<br>
>>> connected into a T1 card on the AS5400.
Several circuits to customers that<br>
>>> are delivered out of the T3 through the mux
to T1 tie pairs through AT&T,<br>
>>> and some of which go through HDSL T1's that
we provide.<br>
>>><br>
>>> We have clocking set up thusly. The T1 port
that has the trunk line in it<br>
>>> (Serial6/0) is set to clock source line, to
get clocking from AT&T.<br>
>>> The TDM clock priority on AS5400 is set to
Serial6/0.<br>
>>> The T3 that has all the other T1's is set to
clock source internal, on the<br>
>>> assumption that the internal clock on the
AS5400 should now be<br>
>>> synchronizing to the trunk line coming in on
6/0. So all the T1 channels<br>
>>> on the T3 should be following the Cisco
clock.<br>
>>> The mux is set to clocking is set on the t3
to clock source line, to get<br>
>>> clocking from the T3 coming from the AS5400.<br>
>>> The customers at the end are all set to clock
source line.<br>
>>><br>
>>> None of the trunks is having slips, but
several of the AT&T customers are<br>
>>> showing a slip every 10 seconds or so. The
clocking chain we have set up<br>
>>> seems logical to me. Is there something I'm
missing? Why would the<br>
>>> customers be having slips.<br>
>>><br>
>>> We asked AT&T to monitor one of the lines
that we are seeing slips on.<br>
>>> They watched it for a bit and said no slips
are occurring, though I am<br>
>>> seeing them both on the AS5400 and on the
Customer router. They are<br>
>>> performing a more indepth test now.<br>
>>><br>
>>><br>
>>>
_______________________________________________<br>
>>> cisco-nas mailing list<br>
>>> </font><a
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true"><font face="Arial" size="2">cisco-nas@puck.nether.net</font></a><br>
<font face="Arial" size="2">>>> </font><a
href="https://puck.nether.net/mailman/listinfo/cisco-nas"
moz-do-not-send="true"><font face="Arial" size="2">https://puck.nether.net/mailman/listinfo/cisco-nas</font></a><br>
<font face="Arial" size="2">>><br>
>> _______________________________________________<br>
>> cisco-nas mailing list<br>
>> </font><a
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true"><font face="Arial" size="2">cisco-nas@puck.nether.net</font></a><br>
<font face="Arial" size="2">>> </font><a
href="https://puck.nether.net/mailman/listinfo/cisco-nas"
moz-do-not-send="true"><font face="Arial" size="2">https://puck.nether.net/mailman/listinfo/cisco-nas</font></a><br>
<font face="Arial" size="2">>><br>
> _______________________________________________<br>
> cisco-nas mailing list<br>
> </font><a href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true"><font face="Arial" size="2">cisco-nas@puck.nether.net</font></a><br>
<font face="Arial" size="2">> </font><a
href="https://puck.nether.net/mailman/listinfo/cisco-nas"
moz-do-not-send="true"><font face="Arial" size="2">https://puck.nether.net/mailman/listinfo/cisco-nas</font></a>
<hr> _______________________________________________<br>
cisco-nas mailing list<br>
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a><br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://puck.nether.net/mailman/listinfo/cisco-nas">https://puck.nether.net/mailman/listinfo/cisco-nas</a></blockquote>
</blockquote>
<br>
<p> </p>
<hr> _______________________________________________<br>
cisco-nas mailing list<br>
<a class="moz-txt-link-abbreviated" href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a><br>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-nas">https://puck.nether.net/mailman/listinfo/cisco-nas</a></blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
cisco-nas mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-nas">https://puck.nether.net/mailman/listinfo/cisco-nas</a></pre>
</blockquote>
<br>
</body>
</html>