[cisco-voip] Avoid Clocking issues with PRI

[Steven Sarte]

With the new VWIC3 you can have independent clocking when you have a voice PRI and data T1 on a 2 port card.  

As for NM I'm reading that it's a separate clocking domain from the VWIC cards.

Sent from my iPhone

On Oct 16, 2012, at 7:08 PM, Ted Nugent <tednugent73 at gmail.com> wrote:

> 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.
>  
> http://www.cisco.com/en/US/prod/collateral/routers/ps5855/prod_qas0900aecd8028d2e5_ps10537_Products_Q_and_A_Item.html
>  
> Q. How do the Cisco VWIC3 cards differ from the VWIC2 cards?
> A. 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:
> Enhanced clocking capabilities: 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.
> Q. Can the 2- and 4-port VWIC3 cards support different clocking domains?
> A. 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.
>  
>  
> 
> 
>  
> On Tue, Oct 16, 2012 at 5:48 PM, Ted Nugent <tednugent73 at gmail.com> wrote:
> 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...
> 
> 
> On Tue, Oct 16, 2012 at 5:44 PM, Steven Sarte <steven.sarte at gmail.com> wrote:
> Take a look at this white paper:
> http://www.cisco.com/en/US/prod/collateral/routers/ps5854/prod_white_paper0900aecd805b9915.html
> 
> Under the section titled: Clocking and Timing Options
> 
> Thanks,
> Steven
> 
> On Tue, Oct 16, 2012 at 5:32 PM, Jason Aarons (AM)
> <jason.aarons at dimensiondata.com> wrote:
> > This doesn’t work when you have PRIs from different providers.
> >
> >
> >
> > The original VWIC2 has a single PLL and backplane could not clock from
> > multiple sources.
> >
> >
> >
> > From: cisco-voip-bounces at puck.nether.net
> > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Roger Wiklund
> > Sent: Tuesday, October 16, 2012 4:40 PM
> > To: Steven Sarte
> > Cc: cisco-voip at puck.nether.net
> > Subject: Re: [cisco-voip] Avoid Clocking issues with PRI
> >
> >
> >
> >
> >
> > Dunno about the NM, I just use network-clock-select 1 e1 x/y/z and
> > ensure you have clock source line. That's enough to keep it slips
> > free.
> >
> > Regards
> > Roger
> >
> > On Tue, Oct 16, 2012 at 10:28 PM, Steven Sarte <steven.sarte at gmail.com>
> > wrote:
> >> I have two SP's for my PRI's on a 2921 currenty using a
> >> VWIC3-4MFT-T1/E1. I opened a Cisco Partner case and they told me you
> >> can avoid timing slips by using a Network Module PRI, like a
> >> NM-HDV2-T1/E1 and a VWIC3-4MFT-T1/E1 in the WIC slots.
> >>
> >> Has anyone configured this before? What would the clocking
> >> configuration look like. I did open a Cisco TAC case but he was not
> >> very helpful in his first reply.
> >>
> >> Thanks in advance,
> >> Steven
> >> _______________________________________________
> >> cisco-voip mailing list
> >> cisco-voip at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/cisco-voip
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> > itevomcid
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121016/c2c05256/attachment.html>