1753770 Members
5040 Online
108799 Solutions
New Discussion юеВ

Interpreting NTPQ output

 
SOLVED
Go to solution
Yogeeraj_1
Honored Contributor

Interpreting NTPQ output

Dear experts!

I recently has a thread which permitted me to troubleshoot my timeserver problem (http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=947300).
Unfortunately, i am still not at ease with the ntp command and outputs.

As such, can any one please help me interprete the output produced when i run the ntpq command on my server?

Note that, i was previously using time zone GMT04:00 which i have just change to GMT+4 (using set_parms timezone) after which i also had to correct the current time using set_parms datetime.

Below the current output of the "ntpq" command:
# ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
*LOCAL(1) LOCAL(1) 10 l 28 64 377 0.00 0.000 10.01
ntptsvr.yd.mu LOCAL(1) 13 u 75 256 377 4.87 -286550 1.46
# date
Thu Sep 1 10:21:49 GMT 2005
# echo $TZ
GMT+4
#

thanking you in advance for all your replies.

kind regards
yogeeraj

No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
37 REPLIES 37
Steve Steel
Honored Contributor
Solution

Re: Interpreting NTPQ output

Hi

http://docs.hp.com/en/B2355-90774/ch04s02.html


table 4.7


Steve Steel
If you want truly to understand something, try to change it. (Kurt Lewin)
Alessandro Pilati
Esteemed Contributor

Re: Interpreting NTPQ output

Yogeeraj,
these are some explanation of the output:

REMOTE=the localhost plus peers hosts specified in the configuration files, from which your host will take time sinchronization

Charachter that may be before hostname:
* indicates the current synchronization source.

# indicates that the host is selected for synchronization, but distance from the host to the server exceeds the maximum value.

o indicates that the host is selected for synchronization, and the PPS signal is in use.

+ indicates the host included in the final synchronization selection set.

x indicates that the host is the designated false ticker by the intersection algorithm.

. indicates that the host is selected from the end of the candidate list.

- indicates a host discarded by the clustering algorithm.

blank indicates a host is discarded due to high stratum and/or failed sanity checks.


REFID=the current source of synchronization for the remote host

STRATUM=the stratum level of the remote host

T=types available
l local (such as a GPS clock)

u unicast (this is the common type)

m multicast

b broadcast

- netaddr (usually 0)

WHEN=number of seconds passed since the remote host response

POLL=polling interval to the remote host, defined with the "minpoll" value in ntp.conf file

REACH=indicates how successful attempts to reach the server are. This is an 8-bit shift register with the most recent probe in the 2^0 position. The value 001 indicates the most recent probe was answered, while 357 indicates one probe was not answered. The value 377 indicates that all the recent probes have been answered.

DELAY= (round trip time) indicates the time (in milliseconds) taken by the reply packet to return in response, to a query sent by the server.

OFFSET=indicates the time difference (in milliseconds) between the server's clock and the client's clock. When this number exceeds 128, and the message synchronization lost appears in the log file

DISP=indicates the difference in the offset measurement between two samples. This is an error-bound estimate. The dispersion is a primary measure of the network service quality.


Hope this helps.
Rgds,
Alex
if you don't try, you'll never know if you are able to
Alessandro Pilati
Esteemed Contributor

Re: Interpreting NTPQ output

Yogeeraj_1
Honored Contributor

Re: Interpreting NTPQ output

hi,

thank you all for your quick responses, can anyone help me clarify the following line:
LOCAL(1)
13
u
605
1024
377
4.79
-286549
19.39

(nb. translated to vertical for clarity)

thanking you in advance

kind regards
yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Alessandro Pilati
Esteemed Contributor

Re: Interpreting NTPQ output

LOCAL(1) Indicates your localhost
13 is the stratum of one of the servers to contact for synchronization, the lower the better, 1=primary...16=not synchronized ( the server must be at lower or equal stratum than client, to avoid loops in configuration )
u is the type of server, in your case is UNICAST
605 time passed since the last interrogation of this server ( in seconds )
1024 is the poll value, the interval between the interrogations
377 reachability of the last 8 interrogation ( 377 means that all the last 8 responses from the server have been correctly received )
4.79 Delay of propagation ( MUST BE < 16, otherwise your xntpd consider the server unaffordable, so 4,79 is OK )
-286549 Difference from the local time
19.39 Time of dispersion of the last 8 interrogation


Anyway,
here it is a SUPER document about NTP.
Take care of it

http://www.sun.com/blueprints/0901/NTPpt3.pdf

Hope all it helped you

Regards,
Alex
if you don't try, you'll never know if you are able to
Yogeeraj_1
Honored Contributor

Re: Interpreting NTPQ output

hi again,

seems like my server is not synchronising with my time server. am i right?

below some observations:

# ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
*LOCAL(1) LOCAL(1) 10 l 21 64 377 0.00 0.000 10.01
ntptsvr.yd.mu LOCAL(1) 13 u 901 1024 367 5.52 -286544 13.66

# ntpq -p ntptsvr.yd.mu
remote refid st t when poll reach delay offset disp
==============================================================================
*LOCAL(1) LOCAL(1) 12 l 8h 64 377 0.00 0.000 0.94
#


attaching txt file for a better formatted output.

your comments would be most appreciated.

Kind regards
yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Alessandro Pilati
Esteemed Contributor

Re: Interpreting NTPQ output

OK,
verify if the server ntp is failing in authentication:

Run:
xntpdc
at the "xntpdc>" prompt run:
pstats

And post the output ( Bad authentication should be 0 )
if you don't try, you'll never know if you are able to
Yogeeraj_1
Honored Contributor

Re: Interpreting NTPQ output

hi,
below the output you requested:
# xntpdc
xntpdc> pstats ntptsvr.yd.mu
remote host: ntptsvr.yd.mu
local interface: x.x.x.x
time last received: 311s
time until next send: 713s
reachability change: 98152s
packets sent: 109
packets received: 108
bad authentication: 0
bogus origin: 0
duplicate: 0
bad dispersion: 8
bad reference time: 0
candidate order: 0
xntpdc>

regards
yogeeraj
No person was ever honoured for what he received. Honour has been the reward for what he gave (clavin coolidge)
Alessandro Pilati
Esteemed Contributor

Re: Interpreting NTPQ output

Authentication is ok.
But you host is using itself as the ntp source.

Check if you did this procedure to enable ntp client:

/sbin/init.d/xntp stop
cd /etc/rc.config.d
vi netdaemons

export NTPDATE_SERVER=node name
export XNTPD=1

then run:
ntpdate
/sbin/init.d/xntp start

Wait 10 mins, run ntpq -p again to check the status.
if you don't try, you'll never know if you are able to