Sponsored Content
Full Discussion: Ntpq - when=9d - not right?
Operating Systems Solaris Ntpq - when=9d - not right? Post 302997762 by psychocandy on Friday 19th of May 2017 05:56:02 AM
Old 05-19-2017
Ntpq - when=9d - not right?

Problem with external aerial and galleonm time server just turned back on. I'm guessing this is telling me its not worked for 9 days?

Should I now force a poll or wait?


Code:
$ntpq -p
     remote           refid      st t when poll reach   delay   offset    disp
==============================================================================
 time-p1      .MSF.            1 -   9d   64    0     0.43    0.027 16000.0
 time-s1      0.0.0.0         16 -    - 1024    0     0.00    0.000 16000.0
*LOCAL(0)        LOCAL(0)         9 l   25   64  377     0.00    0.000   10.01

 

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

output of ntpq -p

Howdy guys, I have 2 sun solaris server(T200) in cluster mode. I put the command below ntpq -p. I need your help to understand the output. I plan to change the date and time in both server. node1:/home/mydir> ntpq -p remote refid st t when poll reach delay ... (6 Replies)
Discussion started by: thepurple
6 Replies

2. Red Hat

What fields we need to consider ntpq -p output?

In our environment we used to lot of events for ntp issues. I am unable to find the what needs to consider here. :( ntpq -p fields. remote refid st t when poll reach delay offset jitter ---------- Post updated at 05:13 AM ---------- Previous update was at 04:47 AM... (1 Reply)
Discussion started by: Naveen.6025
1 Replies

3. Shell Programming and Scripting

Problem in ntpq

Hi i an not able to understand what below command in saying in its O/P what i understand is the astrick(*) one is acting as a ntp master. but not able to understand what insane and sys.peer here means. # ntpq ntpq> pe remote refid st when poll reach delay ... (2 Replies)
Discussion started by: scriptor
2 Replies
NTPDC(8)						      System Manager's Manual							  NTPDC(8)

NAME
ntpdc - monitor operation of ntp daemon SYNOPSIS
ntpdc [-n] [-v] hosts... DESCRIPTION
ntpdc sends an INFO_QUERY packet to an ntp daemon running on the given hosts. Each daemon responds with information about each of its peers, which ntpdc formats on the standard output. Normally, the name of the responding host and its peers are printed. The -n switch disables this, printing only internet addresses. Default is a terse, table-style report. The -t switch generates an alternate form of the terse report. The -v switch generates a verbose report. TERSE REPORT
A typical terse report looks like: (rem) Address (lcl) Strat Poll Reach Delay Offset Disp ========================================================================== -umd1 128.8.10.14 1 64 266 3.0 -65.0 0.0 *DCN1.ARPA 128.8.10.14 1 256 332 155.0 -4.0 0.0 128.8.251.92 128.8.10.14 2 64 367 -16.0 -61.0 0.0 idunno.Princeto 128.8.10.14 3 64 252 60.0 -53.0 0.0 leo 128.8.10.14 2 64 275 4.0 -273.0 1536.2 The alternate form is only slightly different; it looks like: Address Reference Strat Poll Reach Delay Offset Disp ========================================================================== -umd1 WWVB 1 64 266 3.0 -65.0 0.0 *DCN1.ARPA WWVB 1 256 332 155.0 -4.0 0.0 128.8.251.92 umd1 2 64 367 -16.0 -61.0 0.0 idunno.Prince trantor 3 64 252 60.0 -53.0 0.0 leo umd1 2 64 275 4.0 -273.0 1536.2 Fields are interpreted as follows: - or *: The - mark indicates a pre-configured peer (mentioned in ntp.conf). the * mark shows which pre-configured peer (if any) is cur- rently being used for synchronization. (rem) address: The remote host name or internet address of a peer. (lcl) address: The "local" host as specified as an argument to ntpdc. Reference: The reference time source being used for synchronization by the peer. Strat: The stratum level of the peer (as perceived by the local host). Poll: Current polling interval in seconds for this peer. Reach: Octal value of a shift register indicating which responses were received from the previous 8 polls to this peer (see RFC-????). Delay: Round-trip delay in milliseconds for this peer as of the latest poll. Disp: Current value of dispersion (see RFC-????) in milliseconds for this peer. VERBOSE REPORTS
When the -v flag is given a series of verbose reports are presented. A typical one looks like this: Neighbor address 128.4.0.6 port:123 local address 192.35.201.47 Reach: 0376 stratum: 1 poll int(HPI): 10 precision: -10 Sync distance: 0 disp: 0.014000 flags: 0 leap: 0 Reference clock ID: WWV timestamp: a7c2832e.6f9d0000 Poll int(MPI): 10 threshold: 1024 timer: 1024 send: 266 received: 192 samples: 9 Delay(ms) 1144.00 1296.00 1118.00 1115.00 1225.00 1129.00 1086.00 1087.00 Offset(ms) 19.00 92.00 -17.00 12.00 41.00 4.00 -1.00 -14.00 delay: 1086.000000 offset: -1.000000 dsp 0.014000 Fields are interpreted as follows: Neighbor address...: The address and port number of this neighbor, followed by the local address. Reach: nn Reachability in response to last 8 polls (octal value of shift register) stratum: n Stratum level. poll interval: time precision: nn The precision of this clock, given in seconds as a power of 2. e.g A clock derived from the power line frequency (60 Hz) has a pre- cision of 1/60 second (about 2^-6) and would be indicated by a precision of -6. Syn distance: 0 Synchronizing distance. Always zero in the current implementation. disp: nn Dispersion. flags: nn leap: flag The leap second indicator. Non-zero if there is to be a leap second added or subtracted at the new year. Reference clock ID: [address] timestamp: nn Poll interval: time threshold: nn timer: nn send: nn The number of ntp packets sent to this neighbor. received: nn The number of ntp packets received from this neighbor. samples: nn Delay and Offset The round-trip delay and clock offset for the last eight ntp packet exchanges. If there are fewer than eight valid samples, the delay field will be zero. delay: avg-delay offset: avg-offset dsp ??? Average delay, offset, and dispersion calculated from the above samples. Meanings...??? BUGS
Probably a few. Report bugs to Louis A. Mamakos (louie@trantor.umd.edu). SEE ALSO
RFC-???? Network Time Protocol(1), Dave Mills and ... ntpd(8), ntp(8) 10 March 1989 NTPDC(8)
All times are GMT -4. The time now is 12:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy