Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Clocking Sources (was NTp sources that work in a datacenter (was Re: Is latency equivalentto RTT?))

  • From: N. Richard Solis
  • Date: Mon Jun 02 16:40:45 2003

Peter Lothberg wrote:
> > The desire for everyone to have a timing source that is tracable to
> > a Cesium clock comes from the SONET standard.  If you tie two SONET
> > networks together, if they both don't have timing that's tracable to
> > a Stratum 1 (PRS) source, they'll drift at the points where they
> > interconnect and PSE (Positive Stuff Event) and NSE (Negative Stuff
> > Event) errors will be the result.  This is BAD BAD BAD for the voice
> > networks that are provisioned over SONET.
> BITS and SONET systems do not carry time-of-day information. It's only
> frequency.
> Sonet/GR253C SDH/G811 stratum-1 is 1x10-11 that will give you one
> pointer update every 72 days. But you can do one pointer-update every
> two frames...
> -P
> (you do stuffing on PDH systems)

I reread my post and I didn't think I mentioned TOD information being a part of the BITS/SONET requirements.

BUT, most if not all BITS systems that have a GPS component will also provide an NTP feed derived from the almanac and TOD information provided by the satellites.  That's true of the Datum and the Symmetricom products and I'm pretty sure of the Larus products as well.


Discussion Communities

About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home

Merit Network, Inc.