[ntp:questions] Re: Reach error codes

You have no need to know anjahnoaoed at fl.net.invalid
Tue Jan 24 11:57:08 UTC 2006


Abandoning the right to remain silent, SivaKumar Subramani at Mon, 23 Jan
2006 13:05:27 +0000 said:

> When I execute the "ntpq -p" displays reach value for all the time
> source as 377.
> What it means? When this shall be set to proper value and system clock
> shall be sync'd.
> 
> ntpq -p
>      remote           refid      st t when poll reach   delay
> offset    disp
> ==============================================================================
> 
>  143.209.133.66  143.209.150.72   3 u  696 1024  377   199.74  -725421
> 15875.0
>  143.209.150.72  131.107.1.10     2 u  691 1024  377   199.89  -726021
> 15875.0
>  143.209.150.232 143.209.150.72   3 u  707 1024  377   199.75  -723621
> 15875.0
> 
> What could be the problem?

Nothing is wrong with "reach". reach is a mask of the last 8 polls to
that server/peer. 377 means all 8 polls got responses. 001 is the mask for
the most recent, 200 is for the oldest.

The rest of the output is beyond strange. What version of NTP is this?

How could you have the poll interval at 1024 seconds when your clock
offset is over 700 seconds. Have you set "minpoll 10"?

How can you have an dispersion of 15875.0 with 8 successful polls? Until
the dispersion falls to a small value (something under 100, I forget
the exact number) the clock will never sync.

Is your path extremely assymetric? Is the link dial-on-demand? 199ms
delay suggests dialup. Have you tried adding the "iburst" option? e.g.

server 143.209.133.66 iburst maxpoll 12

-- 
Avoid reality at all costs.
$email =~ s/n(.)a(.)n(.)a(.)e(.+)invalid/$1$2$3$4$5au/;
icbm: 33.43.46S 150.59.27E




More information about the questions mailing list