[ntp:questions] Troubleshooting who's at fault

Harlan Stenn stenn at ntp.org
Fri Jun 26 00:08:23 UTC 2009


>>> In article <d8384c7d-f151-4405-86b6-d6a96e6561b3 at j19g2000vbp.googlegroups.com>, Ronaldo Mexico <ronaldo.hawk.mexico at gmail.com> writes:

Ronaldo> In reply to Gene Miller and Steve Kostecke:
>> If the PTS is connected to a reference clock, why does it report itself
>> as a stratum 2 with a refid of either 73.78.73.84 or LOCAL(0), as shown
>> in the original posting:

Ronaldo> The PTS -is- it's reference.  It's time is based on GPS-fed data,
Ronaldo> then internally disciplined using a rubidium oscillator.
Ronaldo> Technically, it's the master time server, which is probably why
Ronaldo> it's showing a refid of LOCAL(0) and/or 73.78.73.84

The refid is used for loop prevention/detection.

If you are using LOCAL as a fallback on your client, and your upstream
server is using LOCAL ias the name for its PTS-sync'd refid, then the client
just sees that the 2 sources it knows about are using the same refid and
will flag that as a loop.

If the upstream machine is sync'd to PTS with an Rb oscillator, give the
upstream system a "better" refid name than LOCAL(0) or LOCAL.

-- 
Harlan Stenn <stenn at ntp.org>
http://ntpforum.isc.org  - be a member!




More information about the questions mailing list