Summary:Setting up NTP Server

hi,

 I got a number of good replies, thanks to all who
replied. Here i am putting 2 of the good replies.

Just add this to /etc/ntp.conf

server  navobs1.usnogps.navy.mil        #
204.34.198.40   (tick)
server  navobs2.usnogps.navy.mil        #
204.34.198.41   (tock)
server  time-b.timefreq.bldrdoc.gov     #
132.163.135.131
server  ntp0.mcs.anl.gov                # 140.221.8.88
server  127.127.1.0     # local clock
fudge   127.127.1.0 	stratum 10

then mkdir /etc/ntp
touch /etc/ntp/drift

2nd reply:

Pretty straightforward... ensure your
/etc/inet/ntp.conf has content
approx thus:

# /etc/inet/ntp.conf
# for local tier-2 time-servers refer to the URL,
# http://www.eecis.udel.edu/~mills/ntp/clock2.htm
# and choose one that is geographically close to you.
#
server time.server.ip.address prefer minpoll 8 maxpoll
12
server time.server2.ip.address minpoll 8 maxpoll 12
#
# have as many external servers specified as you want
for 
# redundancy - just be sure to flag one with
"prefer"...
#
#server time.server3.ip.address minpoll 8 maxpoll 12

# and apparently, we can always fall back to the local
clock.
server 127.127.1.0
fudge 127.127.1.0 stratum 9

# keep local logs so clock can self-adjust based on
known
(self-observed) drift:
enable auth monitor
driftfile /var/ntp/ntp.drift
statsdir /var/ntp/ntpstats/
filegen peerstats file peerstats type day enable
filegen loopstats file loopstats type day enable
filegen clockstats file clockstats type day enable


--end--

Note that minpoll, maxpoll help specify how often you
want to hit the
NTP server for a time-check. Default is 64 seconds
(2^6) I believe. If
you are not so concerned about the time synch then
increase your 
minpoll
value - which is why I've increased minpoll to 2^8=>
256 seconds;
maxpoll of 2^12 seconds. As your local machine "self
calibrates" and
drifts less from the external source, the poll
frequency will gradually
drop off from Minpoll--->Maxpoll. Ultimately it will
never poll less
frequently than specified by maxpoll (in my case, once
ever 2^12 
seconds
or 4096 seconds AKA once every ~68 minutes.)

Also note that your local clients can synch against a
single "local
master" - just provide the "local master" IP as the
"server" instead of
the external NTP time source. Hence, in my network
here we have a 
single
NTP server "master" for each subnet which synchs
against an external
source ; then all other machines are configured to use
these local
masters as their NTP servers. Keeps all clocks nicely
synched and
minimizes the burden on the external time servers.

Be warned: When first setting things up --- NTP will
not synch if the
time is "too far off". You may have to tweak things
with the "date"
command to get it within +/- 60 seconds. I typically
allow "a few 
hours"
(overnight) to be sure that it is / isn't working.

The command, "ntpq -p" is very handy to evaluate if it
is really
working. (if things are good, a "*" will appear next
to the name of the
external NTP server being used.



Oh yes. NTP servers provide up GMT I believe. It is
purely a reference.
Other issues such as time zone, daylight saving, etc
are all dealt with
locally by the OS. Think of NTP as a way to synch your
GMT clock with
another GMT clock.


original question:

Hi,

 I am setting up NTP Server & would like to
synchronize time with external remote time server. 
Can somebody guide me for doing this. 
 My servers are located in Central timezone, USA. 
 Do I need to refer any specific timeservers to
synchronize ? 
 What are the IP address of those servers ? 
 
Can somebody point me some link where i will get list
of standard time servers ?
 What would be the entries in /etc/inet/ntp.conf file.

 Any help in this regard would be highly appreciated.

Thanks in advance




__________________________________________________
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/