[ntp:questions] Looking for a NTP stratum 2 appliance

Matthew Huff mhuff at ox.com
Fri May 26 12:11:30 UTC 2017

Thanks. I agree that the appliance doesn’t appear to exist. It’s a shame that it doesn’t, I think it would be a good idea.

The 50 msec isn’t that hard to reach on an average basis, but we routinely see drifts away from that on occasions. The minpoll idea would probably fix this, but was hesitant to poll that frequently. I just found NIST’s NTP page and they specify to not poll more frequently that every 4 seconds (minpoll 2). I wouldn’t have thought that they would want polling with minpoll 3, but it appears I was wrong. This may fix the issue by itself.

Matthew Huff             | 1 Manhattanville Rd
Director of Operations   | Purchase, NY 10577
OTA Management LLC       | Phone: 914-460-4039
aim: matthewbhuff        | Fax:   914-694-5669

From: Paul [mailto:tik-tok at bodosom.net]
Sent: Friday, May 26, 2017 8:03 AM
To: Matthew Huff <mhuff at ox.com>
Cc: NTP Questions <questions at lists.ntp.org>
Subject: Re: [ntp:questions] Looking for a NTP stratum 2 appliance

"The Securities and Exchange Commission (SEC) approved a new clock synchronization standard of 50 milliseconds applicable to computer clocks that are used to record certain events in NMS securities or OTC equity securities. Firms have six months from the effective date, until February 20, 2017, to apply the new 50 millisecond standard to impacted system clocks that capture time in milliseconds. Firms have eighteen months from the effective date, until February 19, 2018, to apply the new standard to impacted system clocks that do not capture time in milliseconds. [http://www.finra.org/industry/notices/16-23]"
Perhaps you are referring to something other than the above requirement.  In any case 50 or 5 milliseconds is easily achieved on any random computer unless there are uncontrolled external events.  You should control those events.  A common problem is setting minpoll to some value other than 3.  Another is a misconfigured NIC or a speed mismatch.

Our nearly unmaintained S2 Linux servers manage  less than 100 microseconds of jitter and 500 microseconds of offset compared to the S1 servers.
I'd be surprised if an appliance as spec'ed exists.

On Fri, May 26, 2017 at 6:25 AM, Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>> wrote:
The issues is that sometimes our stratum 2 servers drift away from NIST time (our stratum 2 servers are synced to NIST stratum 1 servers) by > 5 msec, violating FINRA regulations (it's a silly requirement).

More information about the questions mailing list