Oh I absolutely agree and that's how it's always been however I thought I had heard that was one of the "great things" announced about the ISR2 and the newer VWIC3s but it's very possible I was not paying attention closely enough. I'll find the slides tomorrow and confirm but it's probably just what was listed in that doc posted above about having data and voice clocked independently off the same card, that would make a lot more sense since I don't see any new commands to "partition" the DSP or anything of that nature.<br>
<br><div class="gmail_quote">On Tue, Oct 16, 2012 at 7:30 PM, Heim, Dennis <span dir="ltr"><<a href="mailto:Dennis.Heim@wwt.com" target="_blank">Dennis.Heim@wwt.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">
<div lang="EN-US" vlink="purple" link="blue" bgcolor="white"><div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";font-size:10pt">The problem like Jason said with voice is those DSPs. The NM module works because it has its own dedicated PVDMs.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif";font-size:10pt"><u></u> <u></u></span></p><div><p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";font-size:11pt">Dennis Heim</span><span style="font-family:"Calibri","sans-serif";font-size:11pt"><u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";font-size:11pt">Sr. UC Engineer<u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";font-size:11pt">World Wide Technology<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";font-size:11pt">Office: <a href="tel:314.212.1814" target="_blank" value="+13142121814">314.212.1814</a><u></u><u></u></span></p><p class="MsoNormal">
<span style="font-family:"Calibri","sans-serif";font-size:11pt">Email: <a href="mailto:dennis.heim@wwt.com" target="_blank">dennis.heim@wwt.com</a><u></u><u></u></span></p><p class="MsoNormal"><span style="font-family:"Calibri","sans-serif";font-size:11pt"><a href="http://www.wwt.com/" target="_blank">www.wwt.com</a><u></u><u></u></span></p>
</div><p class="MsoNormal"><span style="font-family:"Arial","sans-serif";font-size:10pt"><u></u> <u></u></span></p><div><div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Tahoma","sans-serif";font-size:10pt">From:</span></b><span style="font-family:"Tahoma","sans-serif";font-size:10pt"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Jason Aarons (AM)<br>
<b>Sent:</b> Tuesday, October 16, 2012 7:26 PM<br><b>To:</b> Steven Sarte; Ted Nugent</span><div><div class="h5"><br><b>Cc:</b> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> Re: [cisco-voip] Avoid Clocking issues with PRI<u></u><u></u></div></div><p></p></p></div></div><div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt">I suspect you still can’t have 2 voice PRIs with different clocks. How would your carve up the mother board/backplane DSP resources to clock to each port? I’d still go with a separate router for voice PRIs to separate carriers.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:rgb(31,73,125);font-family:"Calibri","sans-serif";font-size:11pt"><u></u> <u></u></span></p><div><div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentColor currentColor;padding:3pt 0in 0in">
<p class="MsoNormal"><b><span style="font-family:"Tahoma","sans-serif";font-size:10pt">From:</span></b><span style="font-family:"Tahoma","sans-serif";font-size:10pt"> Steven Sarte <a href="mailto:[mailto:steven.sarte@gmail.com]" target="_blank">[mailto:steven.sarte@gmail.com]</a> <br>
<b>Sent:</b> Tuesday, October 16, 2012 7:23 PM<br><b>To:</b> Ted Nugent<br><b>Cc:</b> Jason Aarons (AM); <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><b>Subject:</b> Re: [cisco-voip] Avoid Clocking issues with PRI<u></u><u></u></span></p>
</div></div><p class="MsoNormal"><u></u> <u></u></p><div><p class="MsoNormal">With the new VWIC3 you can have independent clocking when you have a voice PRI and data T1 on a 2 port card. <u></u><u></u></p></div><div><p class="MsoNormal">
<u></u> <u></u></p></div><div><p class="MsoNormal">As for NM I'm reading that it's a separate clocking domain from the VWIC cards.<u></u><u></u></p></div><div><p class="MsoNormal"><br>Sent from my iPhone<u></u><u></u></p>
</div><div><p style="margin-bottom:12pt" class="MsoNormal"><br>On Oct 16, 2012, at 7:08 PM, Ted Nugent <<a href="mailto:tednugent73@gmail.com" target="_blank">tednugent73@gmail.com</a>> wrote:<u></u><u></u></p></div>
<blockquote style="margin-top:5pt;margin-bottom:5pt"><div><div><p class="MsoNormal">Hmm, does this imply that you can have 2 seperate VWIC3s in the same ISR2 chassis supporting thier own voice clocking domains or are we still under the same restrictions where the ISR2 only supports a single clocking domain for voice? Thought that was what I heard but it's possible this is what I'm remembering.<u></u><u></u></p>
</div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><p class="MsoNormal"><a href="http://www.cisco.com/en/US/prod/collateral/routers/ps5855/prod_qas0900aecd8028d2e5_ps10537_Products_Q_and_A_Item.html" target="_blank">http://www.cisco.com/en/US/prod/collateral/routers/ps5855/prod_qas0900aecd8028d2e5_ps10537_Products_Q_and_A_Item.html</a><u></u><u></u></p>
</div><div><p class="MsoNormal"> <u></u><u></u></p></div><div><div style="margin-left:0.25in"><p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">Q.</span> How do the Cisco VWIC3 cards differ from the VWIC2 cards?<u></u><u></u></b></p>
</div><div style="margin-bottom:7pt;margin-left:0.25in"><p class="MsoNormal"><a name="13a6be9f87032661_wp9000141"></a><b><span style="font-family:"Arial","sans-serif"">A.</span></b> The Cisco VWIC3 cards are supported only on the Cisco Integrated Services Router (ISR) 1900, 2900, 3900 and 3900E series platforms. The VWIC3 cards add enhancements to the previous generation VWIC2 cards, including:<u></u><u></u></p>
</div><div style="margin-bottom:7pt;margin-left:0.25in"><p class="MsoNormal"><a name="13a6be9f87032661_wp9000142"></a><span><b>Enhanced clocking capabilities</b></span>: The Cisco VWIC3 cards can enable each port to be clocked from an independent clock source for data applications. Data ports can also be clocked independent of voice ports. All voice ports on the card much use the same clock source.<u></u><u></u></p>
</div><div style="margin-bottom:7pt;margin-left:0.25in"><div style="margin-left:0.25in"><p class="MsoNormal"><b><span style="font-family:"Arial","sans-serif"">Q.</span> Can the 2- and 4-port VWIC3 cards support different clocking domains?<u></u><u></u></b></p>
</div><div style="margin-bottom:7pt;margin-left:0.25in"><p class="MsoNormal"><a name="13a6be9f87032661_wp9000200"></a><b><span style="font-family:"Arial","sans-serif"">A.</span></b> When the 2- or 4-port VWIC3 is used in data only, non-ATM applications, each port can connect to a different clocking domain, for example, when two different T1/E1 carriers are used. When the VWIC3 is used for voice applications, all voice T1/E1s have to be synchronized to a single clock source and any difference in clocks risk clock slips or interface flaps. When the VWIC3 is used for mixed data and voice applications, each data port can use an independent clock, and the voice ports can use a clock source independent from the data ports.<u></u><u></u></p>
</div></div><div style="margin-bottom:7pt;margin-left:0.25in"><p class="MsoNormal"> <u></u><u></u></p></div><div style="margin-bottom:7pt;margin-left:0.25in"><p class="MsoNormal"> <u></u><u></u></p></div><div style="margin-bottom:7pt;margin-left:0.25in">
<p class="MsoNormal"><br><br> <u></u><u></u></p></div></div><div><p class="MsoNormal">On Tue, Oct 16, 2012 at 5:48 PM, Ted Nugent <<a href="mailto:tednugent73@gmail.com" target="_blank">tednugent73@gmail.com</a>> wrote:<u></u><u></u></p>
<p class="MsoNormal">I thought for sure I heard at a partners summit or networkers that ISR2/VWIC3 no longer fall under those restrictions. Time to start scouring my slides...<u></u><u></u></p><div><div><p style="margin-bottom:12pt" class="MsoNormal">
<u></u> <u></u></p><div><p class="MsoNormal">On Tue, Oct 16, 2012 at 5:44 PM, Steven Sarte <<a href="mailto:steven.sarte@gmail.com" target="_blank">steven.sarte@gmail.com</a>> wrote:<u></u><u></u></p><p class="MsoNormal">
Take a look at this white paper:<br><a href="http://www.cisco.com/en/US/prod/collateral/routers/ps5854/prod_white_paper0900aecd805b9915.html" target="_blank">http://www.cisco.com/en/US/prod/collateral/routers/ps5854/prod_white_paper0900aecd805b9915.html</a><br>
<br>Under the section titled: Clocking and Timing Options<br><br>Thanks,<br>Steven<u></u><u></u></p><div><div><p class="MsoNormal"><br>On Tue, Oct 16, 2012 at 5:32 PM, Jason Aarons (AM)<br><<a href="mailto:jason.aarons@dimensiondata.com" target="_blank">jason.aarons@dimensiondata.com</a>> wrote:<br>
> This doesn’t work when you have PRIs from different providers.<br>><br>><br>><br>> The original VWIC2 has a single PLL and backplane could not clock from<br>> multiple sources.<br>><br>><br>><br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a><br>> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Roger Wiklund<br>
> Sent: Tuesday, October 16, 2012 4:40 PM<br>> To: Steven Sarte<br>> Cc: <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>> Subject: Re: [cisco-voip] Avoid Clocking issues with PRI<br>
><br>><br>><br>><br>><br>> Dunno about the NM, I just use network-clock-select 1 e1 x/y/z and<br>> ensure you have clock source line. That's enough to keep it slips<br>> free.<br>><br>> Regards<br>
> Roger<br>><br>> On Tue, Oct 16, 2012 at 10:28 PM, Steven Sarte <<a href="mailto:steven.sarte@gmail.com" target="_blank">steven.sarte@gmail.com</a>><br>> wrote:<br>>> I have two SP's for my PRI's on a 2921 currenty using a<br>
>> VWIC3-4MFT-T1/E1. I opened a Cisco Partner case and they told me you<br>>> can avoid timing slips by using a Network Module PRI, like a<br>>> NM-HDV2-T1/E1 and a VWIC3-4MFT-T1/E1 in the WIC slots.<br>
>><br>>> Has anyone configured this before? What would the clocking<br>>> configuration look like. I did open a Cisco TAC case but he was not<br>>> very helpful in his first reply.<br>>><br>>> Thanks in advance,<br>
>> Steven<br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>><br>> itevomcid<br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><u></u><u></u></p>
</div></div></div><p class="MsoNormal"><u></u> <u></u></p></div></div></div><p class="MsoNormal"><u></u> <u></u></p></div></blockquote></div></div></div></div></blockquote></div><br>