[ntp:questions] High offset value for Palisade GPS under ntpd

Ronaldo Vasconcellos ronaldo at cais.rnp.br
Wed Jun 1 14:40:36 UTC 2005


Hi folks,

I'm experiencing high offset values for a Palisade GPS:


 # ntpq -p
      remote           refid      st t when poll reach   delay   offset  jitter 
 ==============================================================================
 xGPS_PALISADE(1) .GPS.            0 l    8   16  377    0.000  -622.25   4.974
 -time.nist.gov   .ACTS.           1 u   40 1024  377  388.621   17.386   1.635
 +pcdsh05.on.br   .IRIG.           1 u   35 1024  377   30.081   15.763   1.503
 -clock.via.net   .GPS.            1 u  430 1024  377  400.009  -79.251  15.245
 *NAVOBS1.MIT.EDU .PSC.            1 u  534 1024  377  338.327   12.453   6.844
 -navobs1.oar.net .USNO.           1 u  446 1024  377  398.506  -80.998   2.390
 +navobs1.wustl.e .USNO.           1 u  452 1024  377  367.240   12.921   5.048
 -nist1.symmetric .ACTS.           1 u  543 1024  377  387.169  -84.522   8.453
 -ntp-nasa.arc.na .GPS.            1 u  538 1024  377  391.177  -77.095  17.248
 +tick.ucla.edu   .PSC.            1 u  546 1024  377  416.298   12.341   0.081
 -time-nw.nist.go .ACTS.           1 u  458 1024  377  384.315  -64.719  15.336


Any clues? NTP clients are choosing other other servers for 
synchronization. GPS is preferred (server 127.127.29.1 prefer) over peers 
in the configuration file.

More info:


 # ntptrace
 localhost.x.x.br: stratum 2, offset 0.012490, root distance 0.338327
 NAVOBS1.MIT.EDU: stratum 1, offset -0.000008, root distance 0.000000, refid 'PSC'


I would appreciate any help very much.

Best regards,

--
Ronaldo C Vasconcellos
CAIS/RNP - Brazilian Research and Academic Network CSIRT 
http://www.rnp.br/en/cais



More information about the questions mailing list