|
||||||
Time ServerNTS-3000, NTS-4000, NTS-5000, NTS-dialupUser Manual
Select chapter: 1 , 2 , 3 , 4 , 5 , 6 , 7 , 8 , 9 , 10 , 11 , 12 , 12.1, 12.2, 12.3
Page 11/12
11. NTPq client diagnostic utility
Any NTP implementation supports special diagnostic client ntpq. The command ntpq requests the actual status of NTS-xxxx. An command interpreter appears. Type "?" for a list of all available commands
with the following meaning:
•remote list of all valid time sources,
•refid reference number,
•st actual stratum value,
•when time of last successful answered request in seconds,
•poll period of requesting the time server in seconds,
•reach octal notation of the successful requests, shifted left,
•delay delay of the network transmission in milliseconds,
•offset difference between system time and reference time in milliseconds,
•jitter variance of the offsets in milliseconds,
where:
•"*" indicates stabilized source of time,
•''o'' indicates stabilized PPS like source of time,
•"+" points best candidate to become a new stable source of time.
After while stratum hierarchy can change (it does not mean it has to) selecting new source for NTP. Than peer looks like:
Repeatedly a "peer" command lets the user observe the accuracy of the NTP daemon. Every 16 seconds (value of -poll) a new time string is read in from the radio clock. The NTP daemon needs approx. 3...5 minutes for initialization and to get stabilized. This is indicated by a wildcard (*) on the left side of the remote name. Sometimes wildcard (+) appears in-front of single peer line. This indicated a possible change of timeservers to that one indicated by wildcard (+). Wildcard (-) papers to indicate timeserver with low priority. Those servers can not be chosen by NTP as far as wildcard (-) appear, however situation can change with next pool interval.
Previous Page Top of page Next Page
|
||||||
|
