<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=ISO-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19328"></HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV><FONT size=2 face=Arial>I have noticed something that I have not noticed
prior to this, which is that all the units that are experiencing slips are
IAD2400's All are set to get clocking from the line, but does the IAD2400 behave
differently with regard to clocking than most things somehow?</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=Aaron@cisco.com href="mailto:Aaron@cisco.com">Aaron Leonard</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=mays@win.net
href="mailto:mays@win.net">Joseph Mays</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A 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> Wednesday, October 10, 2012 3:30
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-nas] Slips</DIV>
<DIV><BR></DIV>The pri-group config is weird, but I would not think it's
relevant.<BR><BR>My theory continues to be, until disproven, that the device
that is on the far side of the slipping span is not configured right.<BR><BR>
<HR SIZE=2 width="100%">
<BR>
<DIV class=moz-cite-prefix>On 10/10/2012 12:21 PM, <A
class=moz-txt-link-abbreviated href="mailto:mays@win.net">mays@win.net</A>
(Joseph Mays) wrote:<BR></DIV>
<BLOCKQUOTE cite=mid:2B2EF52535744F038D0B661D228673E7@win2snvu0x4eg9
type="cite">
<META name=GENERATOR content="MSHTML 8.00.6001.19328">
<DIV><FONT size=2 face=Arial>Yeah. The DACS is not the problem though,
because we have two circuits going through the DACS, in fact they are two
circuits that are exactly the same, following the same path from our AS5400
through the telco to the same router (an IAD2400) at the same customer,
one is getting slips one is not. Both go through the DACS. The only
difference between them is that one has just a channel group for T1 service
and the other has both a channel group and a PRI group. The one with
just the channel group is plugged into the native T1 port on the IAD2400.
The one with both is plugged into a card that will support multilple tdm
groups on a card.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>On the AS5400....</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face="Courier New">controller T1 1/0:22<BR> framing
esf<BR> channel-group 0 timeslots 1-22 speed 64<BR> description
Glass Doctor combo PRI and T1 1<BR>!<BR>controller T1
1/0:23<BR> framing esf<BR> channel-group 0 timeslots 1-22 speed
64<BR> pri-group timeslots 23-24<BR> description Glass Doctor
combo PRI and T1 2<BR></FONT></DIV>
<DIV><FONT size=2 face=Arial>The second one, on 1/0:23, gets slips about
once every 10 seconds.</FONT></DIV>
<DIV><FONT size=2 face=Arial></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=Aaron@cisco.com href="mailto:Aaron@cisco.com"
moz-do-not-send="true">Aaron Leonard</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=jfmays@launchpad.win.net
href="mailto:jfmays@launchpad.win.net" moz-do-not-send="true">Joe Mays</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> Wednesday, October 10, 2012
2:09 PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [cisco-nas] Slips</DIV>
<DIV><BR></DIV>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"
moz-do-not-send="true">jfmays@launchpad.win.net</A> (Joe Mays)
wrote:<BR></DIV>
<BLOCKQUOTE cite=mid:1630FE1D0F6F45DE949F0A783E09B10F@mainbay
type="cite"><META name=GENERATOR content="MSHTML 8.00.6001.19328">
<DIV><FONT size=2 face=Arial>
<DIV><FONT size=2 face=Arial>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 title=Aaron@cisco.com href="mailto:Aaron@cisco.com"
moz-do-not-send="true">Aaron Leonard</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</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>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
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 class=moz-txt-link-freetext
href="http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a008014f8a6.shtml"
moz-do-not-send="true">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
class=moz-txt-link-abbreviated href="mailto:mays@win.net"
moz-do-not-send="true">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 size=2 face=Arial>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 size=2 face=Arial>Thank you for your
response.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>Show tdm clocks shows the AS5400 is
using the circuit in port 6/0 for primary clocking.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face="Courier New">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 size=2 face="Courier New">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 size=2 face="Courier New">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 size=2 face=Arial>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 size=2 face=Arial>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 size=2 face=Arial>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 size=2 face=Arial> 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 size=2 face=Arial>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 size=2 face=Arial>----- Original Message ----- </FONT>
<DIV><FONT size=2 face=Arial>From: "Aaron Leonard" <</FONT><A
href="mailto:Aaron@cisco.com" moz-do-not-send="true"><FONT size=2
face=Arial>Aaron@cisco.com</FONT></A><FONT size=2
face=Arial>></FONT></DIV>
<DIV><FONT size=2 face=Arial>To: "Joseph Mays" <</FONT><A
href="mailto:jfmays@launchpad.win.net"
moz-do-not-send="true"><FONT size=2
face=Arial>jfmays@launchpad.win.net</FONT></A><FONT size=2
face=Arial>></FONT></DIV>
<DIV><FONT size=2 face=Arial>Cc: <</FONT><A
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true"><FONT size=2
face=Arial>cisco-nas@puck.nether.net</FONT></A><FONT size=2
face=Arial>></FONT></DIV>
<DIV><FONT size=2 face=Arial>Sent: Tuesday, October 09, 2012 3:21
PM</FONT></DIV>
<DIV><FONT size=2 face=Arial>Subject: Re: [cisco-nas]
Slips</FONT></DIV></DIV>
<DIV><FONT face=Arial><BR></FONT></DIV><FONT size=2
face=Arial>> 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 size=2
face=Arial>http://www.cisco.com/en/US/docs/ios/12_3/dial/command/reference/dia_s6g.html#wp1140246</FONT></A><BR><FONT
size=2 face=Arial>> <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 size=2
face=Arial>jfmays@launchpad.win.net</FONT></A><FONT size=2
face=Arial> (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 size=2
face=Arial>mays@win.net</FONT></A><FONT size=2
face=Arial>><BR>>> To: "cisco-nsp" <</FONT><A
href="mailto:cisco-nsp@puck.nether.net"
moz-do-not-send="true"><FONT size=2
face=Arial>cisco-nsp@puck.nether.net</FONT></A><FONT size=2
face=Arial>>; <</FONT><A
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true"><FONT size=2
face=Arial>cisco-nas@puck.nether.net</FONT></A><FONT size=2
face=Arial>><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 size=2
face=Arial>cisco-nas@puck.nether.net</FONT></A><BR><FONT size=2
face=Arial>>>> </FONT><A
href="https://puck.nether.net/mailman/listinfo/cisco-nas"
moz-do-not-send="true"><FONT size=2
face=Arial>https://puck.nether.net/mailman/listinfo/cisco-nas</FONT></A><BR><FONT
size=2 face=Arial>>><BR>>>
_______________________________________________<BR>>>
cisco-nas mailing list<BR>>> </FONT><A
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true"><FONT size=2
face=Arial>cisco-nas@puck.nether.net</FONT></A><BR><FONT size=2
face=Arial>>> </FONT><A
href="https://puck.nether.net/mailman/listinfo/cisco-nas"
moz-do-not-send="true"><FONT size=2
face=Arial>https://puck.nether.net/mailman/listinfo/cisco-nas</FONT></A><BR><FONT
size=2 face=Arial>>><BR>>
_______________________________________________<BR>> cisco-nas
mailing list<BR>> </FONT><A
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true"><FONT size=2
face=Arial>cisco-nas@puck.nether.net</FONT></A><BR><FONT size=2
face=Arial>> </FONT><A
href="https://puck.nether.net/mailman/listinfo/cisco-nas"
moz-do-not-send="true"><FONT size=2
face=Arial>https://puck.nether.net/mailman/listinfo/cisco-nas</FONT></A>
<HR>
_______________________________________________<BR>cisco-nas
mailing list<BR><A class=moz-txt-link-abbreviated
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true">cisco-nas@puck.nether.net</A><BR><A
class=moz-txt-link-freetext
href="https://puck.nether.net/mailman/listinfo/cisco-nas"
moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/cisco-nas</A></BLOCKQUOTE></BLOCKQUOTE><BR>
<HR>
_______________________________________________<BR>cisco-nas mailing
list<BR><A class=moz-txt-link-abbreviated
href="mailto:cisco-nas@puck.nether.net"
moz-do-not-send="true">cisco-nas@puck.nether.net</A><BR><A
class=moz-txt-link-freetext
href="https://puck.nether.net/mailman/listinfo/cisco-nas"
moz-do-not-send="true">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" moz-do-not-send="true">cisco-nas@puck.nether.net</A>
<A class=moz-txt-link-freetext href="https://puck.nether.net/mailman/listinfo/cisco-nas" moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/cisco-nas</A></PRE></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></BLOCKQUOTE><BR></BLOCKQUOTE></BODY></HTML>