mark.gebert@MED.UMICH.EDU (The Geeb) (11/20/90)
________
---------- Your Message ---------
Date: Mon, 19 Nov 90 17:32:31 EST
To: mark.gebert
From: Dave Katz <katz@merit.edu>
Subject: Re: Setup.....
I would set up a server on each LAN that peers with the campus servers.
The ntp.conf files would look pretty much like the ones on pub/xntp
on merit.edu.
I haven't any experience with running NTP on DS5000s; you might drop
a note to ntp@trantor.umd.edu for real-life experiences.
Let me know when you would like the machines configured into the campus
server's tables.
------- End of Your Message ------
We already have two time servers hendrix and bartok that are registered.
But our DEC 5000 (bartok) will not sync anybody even though it has the
ntp.conf.dept (modified for our network).
# NTP configuration file for departmental server
#
# Please send a message to "ntp-request@umich.edu" with the address
# of your server and contact information (name, phone #, and email
# address) to enable time service to your machine.
# Save drift information in a file so NTP converges more quickly
# the next time it runs.
#resolver /usr/local/bin/xntpres
driftfile /etc/ntp.drift
# Peer with the two campus time servers.
peer 35.1.1.42
peer 35.1.1.91
# Distribute broadcast time service on the local Ethernet. The
# "xx.xx.xx.xx" below should be set to the broadcast IP address
# on the local Ethernet (normally 255 in the host part) and
# the leading "#" should be removed.
broadcast 141.214.4.255
This is what happens when we try to sync a client off of it:
ives# ntpdate -d -b bartok.itn.med.umich.edu
ntpdate: ntpdate version 1.0
transmit(141.214.4.149)
receive(141.214.4.149)
transmit(141.214.4.149)
receive(141.214.4.149)
transmit(141.214.4.149)
receive(141.214.4.149)
transmit(141.214.4.149)
receive(141.214.4.149)
transmit(141.214.4.149)
server 141.214.4.149, port 123
stratum 16, precision -6, leap 11, trust 000
refid [0.0.0.0], distance 0.0000, dispersion 0.0000
transmitted 4, in filter 4
reference time: 00000000.00000000 Thu, Feb 7 2036 1:28:16.000
originate timestamp: aaf2e2ce.cd7cd000 Mon, Nov 19 1990 18:01:34.802
transmit timestamp: aaf2e23c.2666a000 Mon, Nov 19 1990 17:59:08.150
filter delay: 0.0412 0.0412 0.0473 0.0412
0.0000 0.0000 0.0000 0.0000
filter offset: 146.6531 146.6509 146.6518 146.6526
0.00000 0.00000 0.00000 0.00000
estdelay 0.0412, estdisp 0.0014
estoffset 146.6531544
ntpdate: no server suitable for synchronization found
But our sun hendrix (configured the exact same way) sync's a host fine:
ives# ntpdate -d -b med.umich.edu
ntpdate: ntpdate version 1.0
transmit(141.214.4.144)
receive(141.214.4.144)
transmit(141.214.4.144)
receive(141.214.4.144)
transmit(141.214.4.144)
receive(141.214.4.144)
transmit(141.214.4.144)
receive(141.214.4.144)
transmit(141.214.4.144)
server 141.214.4.144, port 123
stratum 3, precision -6, leap 00, trust 000
refid [35.1.1.42], distance 0.1573, dispersion 1.5229
transmitted 4, in filter 4
reference time: aaf2e2da.5393d000 Mon, Nov 19 1990 18:01:46.326
originate timestamp: aaf2e2da.bbf0f000 Mon, Nov 19 1990 18:01:46.734
transmit timestamp: aaf2e248.0f5cb000 Mon, Nov 19 1990 17:59:20.060
filter delay: 0.0409 0.0509 0.0409 0.0509
0.0000 0.0000 0.0000 0.0000
filter offset: 146.6677 146.6684 146.6688 146.6690
0.00000 0.00000 0.00000 0.00000
estdelay 0.0409, estdisp 0.0007
estoffset 146.6688333
ntpdate: step time server 141.214.4.144 offset 146.6688333
Any idea's????
Mark A Gebert