[nsp] Setting sync on PA-A3-T3

[Eric Osborne]

On Tue, Apr 08, 2003 at 06:05:53PM +0100, Stephen J. Wilcox wrote:
> 
> On Tue, 8 Apr 2003, James-lists wrote:
> 
> > : the person who suggested "clock-source internal" was on the mark.
> > : 
> > : do not, however, mistake NTP stratum 1 (clock synchronization for the
> > : time of year clock on your router) with a telco "stratum 1" clock.
> > : telco clocks provide frequency discipline for the data clocking on
> > : your circuit, but no time of year functionality.  ntp provides time of
> > : year functionality to a high degree of accuracy, but no frequency discipline.
> > : 
> > : hope this helps,
> > 
> > 
> > Thanks, that clears some things up. So when running "clock-source internal"
> > what makes sure the data clocking is accurate ?
> 
> Nothing, your relying on the internal clock generator of the router.. thats the 
> point of it being internal, as opposed to line which means you take a sync from 
> the network
> 

Note that the internal clocking for such a thing is a stratum 3 PLL
timer, so plenty good enough for b2b and dark-fiber applications.  If
you have no timeslots to fit into in the SONET cloud, it doesn't
really matter much how accurate your timesource is; frames go out,
frames come in, life goes on. :)



eric

> Steve
> 
> 
>  > 
> > James Edwards
> > Routing and Security
> > jamesh at cybermesa.com
> > At the Santa Fe Office: Internet at Cyber Mesa
> > 
> > 
> > _______________________________________________
> > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > 
> 
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/