[ntp:questions] Aberrant NTP behavior

Richard B. Gilbert rgilbert88 at comcast.net
Wed Jan 28 00:15:25 UTC 2004


With a great deal of help from Reg.Clemens, NTP finally sees the 
Motorola Oncore M12.  He fixed a bunch of problems in the driver and 
gently pointed out some of my fat fingerd/fat minded configuration errors.

Unfortunately, things are still not working properly.  Witness the 
following aberrant behavior!

sunblok_# ntpq -p
     remote           refid      st t when poll reach   delay   offset  
jitter
==============================================================================
 GPS_ONCORE(0)   .GPS.            0 l    -   16    0    0.000    0.000 
4000.00
+louie.udel.edu  128.4.40.10      2 u    5   64  377   23.561  -24.166  
10.687
+filbert.cc.colu 128.59.39.48     2 u   35   64  377   14.876  -20.670   
2.002
+otc2.psu.edu    128.118.25.12    2 u   46   64  377   20.767  -23.330   
1.132
*LOCAL(0)        LOCAL(0)        10 l   65   64  377    0.000    0.000   
0.001

The Oncore is unreachable even though the driver seems able to read what 
it's saying.  The clockstats file demonstrates that the Oncore is able 
to report it's name, serial number, firmware version, etc.  LED's on the 
board show that the PPS is working and that TxData line is active once 
per second.

With three perfectly good stratum 2 servers on tap, the local clock, at 
stratum ten, is being selected.

sunblok_# ntptrace
localhost: stratum 11, offset 0.000000, root distance 0.000000
127.127.1.0: timed out, nothing received
***Request timed out

sunblok_# more /etc/ntp.conf
#
# NTP Time Servers
#
# Reference Clock (Motorola Oncore M12)
server 127.127.30.0 prefer
#
# Network servers
#
# Stratum 1
#server navobs1.mit.edu
#server clock.nyc.he.net
#
# Stratum 2
#
server louie.udel.edu iburst
server sundial.columbia.edu iburst
server clock.psu.edu
#
# Declare the local clock to be the clock of last resort.
# It will be used to serve time in the absence of any other.
#
server 127.127.1.0 prefer
fudge 127.127.1.0 stratum 10
#
# Authentication parameters
#
#keys /etc/inet/ntp.keys
#trustedkey  2 3 4
#controlkey 3
#
# NTP monitoring parameters
#
statsdir /var/ntp/ntpstats/
driftfile /etc/inet/ntp.drift
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
sunblok_# more /etc/ntp.oncore0
# /etc/ntp.oncore0
#
# Reference Clock configuration for Motorola Oncore M12
#
# Five Choices for MODE
#    (0) ONCORE is preinitialized, don't do anything to change it.
#          nb, DON'T set 0D mode, DON'T set Delay, position...
#    (1) NO RESET, Read Position, delays from data file, lock it in, go 
to 0D mode.
#    (2) NO RESET, Read Delays from data file, do SITE SURVEY to get 
position,
#                  lock this in, go to 0D mode.
#    (3) HARD RESET, Read Position, delays from data file, lock it in, 
go to 0D mode.
#    (4) HARD RESET, Read Delays from data file, do SITE SURVEY to get 
position,
MODE 1
#     NB. If a POSITION is specified in the config file with mode=(2,4) 
[SITE SURVEY]
#         then this position is set as the INITIAL position of the ONCORE.
#         This can reduce the time to first fix.
LAT 39 45.3753          # Positive is North.
LONG -75 04.27187       # Negative is West
HTGPS 18.28 M           # Height in meters.


Does anyone have any suggestions?







More information about the questions mailing list