<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Aaron,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks for your help on this, we were able to resolve it. You are right, it was the other end (the 2400's). In this case our AS5400 was delivering PRIs to 7 locations: 4 had Cisco 2400s, they all had slips, 3 were to various PBXs, none had slips.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Even though the 2400 IAD T1 controller says "Clock Source is Line.", it doesn't seem to actually mean that. Instead, there is an additional configuration command that is present by default in the 2400:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> network-clock-participate T1 1/0<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>which seems to sync the T1 controller to the internal motherboard TDM clock. That would be OK, but another command is needed, which is not there by default, to then sync the internal clock to the incoming T1 line. It is:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> network-clock-select 1 T1 1/0<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>With that, the internal clock picks up its clocking from the T1 which then via the participate command controls the T1 controller. With the addition of the select command in each of the 2400's all slips have stopped. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks for your help!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>BTW, we would appreciate a working definition for what "Clock Source is Line" really means. In the case of the 2400, does "Line" still have any meaning, or does the network-clock-participate command just by-pass that? That is, the controller's clock source can be set to ANYTHING, but is completely ignored because the "network-clock-participate" command means use the motherboard clock instead, or does the controller clock still retains some meaning?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Similarly, on the AS5400, it too says "Clock Source is Line", but it seems to actually be picking up its clocking from the TDM backplane clock which is controlled with the "tdm clock priority …" command. There does not seem to be the equivalent of the participate command.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Finally, in the case of say a 7200 router talking to a 2600 router with an ordinary Internet T1 between them, we have always configured both ends to use "line" clock source. That seems to work, but what does it mean? Does it mean transmit using your own clock, but adapt and receive whatever the other sends (in which case the two sides of the T1 could have different clocking) or are they somehow more coupled? Until this evet, we never realized that the point-to-point telco provided T1 in the middle might as well be a plain wire: both ends are getting their clocking from the other side? What does "line" really mean?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Michael (I work with Joseph Mays)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> cisco-nas-bounces@puck.nether.net [mailto:cisco-nas-bounces@puck.nether.net] <b>On Behalf Of </b>Joseph Mays<br><b>Sent:</b> Wednesday, October 10, 2012 5:03 PM<br><b>To:</b> Aaron Leonard<br><b>Cc:</b> cisco-nas@puck.nether.net<br><b>Subject:</b> Re: [cisco-nas] Slips<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Perhaps. Let me work with it. Thank you for your help, btw.</span><o:p></o:p></p></div><blockquote style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>----- Original Message ----- <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:#E4E4E4'><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:Aaron@cisco.com" title="Aaron@cisco.com">Aaron Leonard</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>To:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:mays@win.net" title="mays@win.net">Joseph Mays</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Cc:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:cisco-nas@puck.nether.net" title="cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Sent:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Wednesday, October 10, 2012 4:30 PM<o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Subject:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Re: [cisco-nas] Slips<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>OK ... so I've never laid a finger on an IAD2400, but I cheated and looked at an old email from a knowledgeable source, and here's what he says (for the case where the IAD2400 is taking clock from one T1 and providing to another):<o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><pre>network-clock base-rate [56k | 64k ] as appropriate<o:p></o:p></pre><pre>network-clock-select 1 T1 [0 | 1 ] as appropriate<o:p></o:p></pre><pre>clock source line on the appropriate controller<o:p></o:p></pre><pre>clock source internal on the other controller<o:p></o:p></pre><pre><o:p> </o:p></pre><pre>If the peer devices are providing clocking and accepting clocking as you've set<o:p></o:p></pre><pre>on the IAD, then you should get no slips.<o:p></o:p></pre></blockquote><pre><o:p> </o:p></pre><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Arial","sans-serif"'>Does this help?<br><br>Aaron</span><o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 10/10/2012 12:57 PM, <a href="mailto:mays@win.net">mays@win.net</a> (Joseph Mays) wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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?</span><o:p></o:p></p></div><blockquote style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>----- Original Message ----- <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:#E4E4E4'><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:Aaron@cisco.com" title="Aaron@cisco.com">Aaron Leonard</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>To:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:mays@win.net" title="mays@win.net">Joseph Mays</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Cc:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:cisco-nas@puck.nether.net" title="cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Sent:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Wednesday, October 10, 2012 3:30 PM<o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Subject:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Re: [cisco-nas] Slips<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>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.<o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 10/10/2012 12:21 PM, <a href="mailto:mays@win.net">mays@win.net</a> (Joseph Mays) wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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.</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>On the AS5400....</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"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</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>The second one, on 1/0:23, gets slips about once every 10 seconds.</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>----- Original Message ----- <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:#E4E4E4'><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:Aaron@cisco.com" title="Aaron@cisco.com">Aaron Leonard</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>To:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:jfmays@launchpad.win.net" title="jfmays@launchpad.win.net">Joe Mays</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Cc:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:cisco-nas@puck.nether.net" title="cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Sent:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Wednesday, October 10, 2012 2:09 PM<o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Subject:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Re: [cisco-nas] Slips<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>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.<o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 10/9/2012 9:31 PM, <a href="mailto:jfmays@launchpad.win.net">jfmays@launchpad.win.net</a> (Joe Mays) wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>It has been suggested that if those circuits go through a DAX, the clocking signal may not be making it to the other system.<o:p></o:p></span></p></div></div><blockquote style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>----- Original Message ----- <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:#E4E4E4'><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:Aaron@cisco.com" title="Aaron@cisco.com">Aaron Leonard</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>To:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:mays@win.net" title="mays@win.net">Joseph Mays</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Cc:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:cisco-nas@puck.nether.net" title="cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Sent:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Tuesday, October 09, 2012 7:00 PM<o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Subject:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Re: [cisco-nas] Slips<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal style='margin-bottom:12.0pt'>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 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<o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On 10/9/2012 2:46 PM, <a href="mailto:mays@win.net">mays@win.net</a> (Joseph Mays) wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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?</span><o:p></o:p></p></div><blockquote style='border:none;border-left:solid black 1.5pt;padding:0in 0in 0in 4.0pt;margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>----- Original Message ----- <o:p></o:p></span></p></div><div><p class=MsoNormal style='background:#E4E4E4'><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:mays@win.net" title="mays@win.net">Joseph Mays</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>To:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:Aaron@cisco.com" title="Aaron@cisco.com">Aaron Leonard</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Cc:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> <a href="mailto:cisco-nas@puck.nether.net" title="cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a> <o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Sent:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Tuesday, October 09, 2012 4:48 PM<o:p></o:p></span></p></div><div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Subject:</span></b><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> Re: [cisco-nas] Slips<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Thank you for your response.</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Show tdm clocks shows the AS5400 is using the circuit in port 6/0 for primary clocking.</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>Primary Clock:<br>--------------<br>System primary is slot 6 port 0 of priority 1<br>TDM Bus Master Clock Generator State = NORMAL</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"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</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"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</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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.</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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.</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> 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</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>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.</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>----- Original Message ----- </span><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>From: "Aaron Leonard" <</span><a href="mailto:Aaron@cisco.com"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Aaron@cisco.com</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>></span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>To: "Joseph Mays" <</span><a href="mailto:jfmays@launchpad.win.net"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>jfmays@launchpad.win.net</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>></span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Cc: <</span><a href="mailto:cisco-nas@puck.nether.net"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>cisco-nas@puck.nether.net</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>></span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Sent: Tuesday, October 09, 2012 3:21 PM</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Subject: Re: [cisco-nas] Slips</span><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>> 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>> </span><a href="http://www.cisco.com/en/US/docs/ios/12_3/dial/command/reference/dia_s6g.html#wp1140246"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>http://www.cisco.com/en/US/docs/ios/12_3/dial/command/reference/dia_s6g.html#wp1140246</span></a><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>> <br>> Aaron<br>> <br>> ----<br>> <br>> On 10/9/2012 8:43 AM, </span><a href="mailto:jfmays@launchpad.win.net"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>jfmays@launchpad.win.net</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> (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" <</span><a href="mailto:mays@win.net"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>mays@win.net</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>><br>>> To: "cisco-nsp" <</span><a href="mailto:cisco-nsp@puck.nether.net"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>cisco-nsp@puck.nether.net</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>>; <</span><a href="mailto:cisco-nas@puck.nether.net"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>cisco-nas@puck.nether.net</span></a><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>><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>>>> </span><a href="mailto:cisco-nas@puck.nether.net"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>cisco-nas@puck.nether.net</span></a><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>>>> </span><a href="https://puck.nether.net/mailman/listinfo/cisco-nas"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>https://puck.nether.net/mailman/listinfo/cisco-nas</span></a><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>>><br>>> _______________________________________________<br>>> cisco-nas mailing list<br>>> </span><a href="mailto:cisco-nas@puck.nether.net"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>cisco-nas@puck.nether.net</span></a><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>>> </span><a href="https://puck.nether.net/mailman/listinfo/cisco-nas"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>https://puck.nether.net/mailman/listinfo/cisco-nas</span></a><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>>><br>> _______________________________________________<br>> cisco-nas mailing list<br>> </span><a href="mailto:cisco-nas@puck.nether.net"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>cisco-nas@puck.nether.net</span></a><br><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>> </span><a href="https://puck.nether.net/mailman/listinfo/cisco-nas"><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>https://puck.nether.net/mailman/listinfo/cisco-nas</span></a> <o:p></o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal>_______________________________________________<br>cisco-nas mailing list<br><a href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-nas">https://puck.nether.net/mailman/listinfo/cisco-nas</a><o:p></o:p></p></blockquote></blockquote><p class=MsoNormal><o:p> </o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal>_______________________________________________<br>cisco-nas mailing list<br><a href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-nas">https://puck.nether.net/mailman/listinfo/cisco-nas</a><o:p></o:p></p></blockquote><p class=MsoNormal><br><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-nas mailing list<o:p></o:p></pre><pre><a href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a><o:p></o:p></pre><pre><a href="https://puck.nether.net/mailman/listinfo/cisco-nas">https://puck.nether.net/mailman/listinfo/cisco-nas</a><o:p></o:p></pre></blockquote><p class=MsoNormal><o:p> </o:p></p><div class=MsoNormal align=center style='text-align:center'><hr size=2 width="100%" align=center></div><p class=MsoNormal>_______________________________________________<br>cisco-nas mailing list<br><a href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-nas">https://puck.nether.net/mailman/listinfo/cisco-nas</a><o:p></o:p></p></blockquote></blockquote><p class=MsoNormal><o:p> </o:p></p></blockquote></blockquote><p class=MsoNormal><o:p> </o:p></p></blockquote><div><div class=MsoNormal align=center style='text-align:center'><span style='font-size:13.5pt;background:white'><hr size=2 width="100%" align=center></span></div><p class=MsoNormal><b><span style='font-size:7.5pt;background:white'><br><a href="http://filter.win.net/canit/b.php?i=02I9x9fuX&m=6e8db57b64fe&t=20121010&c=s">Click here to mark this message as spam.</a><br><br><a href="http://filter.win.net/canit/b.php?i=02I9x9fuX&m=6e8db57b64fe&t=20121010&c=f">Click here if you accidentally marked this message as spam when it is not spam.</a></span></b><b><o:p></o:p></b></p></div></div></body></html>