Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!think.com!linus!agate!ucbvax!smokey.sandiego.NCR.COM!debbieg
From: debbieg@smokey.sandiego.NCR.COM
Newsgroups: comp.protocols.time.ntp
Subject: isolated network & xntpd
Message-ID: <9104021624.aa17693@ncrcom.DaytonOH.NCR.COM>
Date: 2 Apr 91 19:10:38 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: Debbie Galeazzi <debbie.galeazzi@SanDiego.NCR.COM>
Distribution: inet
Organization: NCR E&M-San Diego, CA
Lines: 36

Keith,

I also run a local isolated network with 4 servers (not SUNs).
What I do is set up 1 server as the main server.  It synchronizes to
its local clock as a stratum 1 clock.  Its config file looks like:
 
server 127.127.1.1 #local clock
fudge 127.127.1.1 time1 0.00 flag1 1

The second server synchronizes to server 1 plus to its own local clock
at stratum 2 in case the main server dies.

peer 132.242.114.201 #main
server 127.127.1.2 #local clock
fudge 127.127.1.2 time1 0.00 flag1 1

The third server syncs to servers 1,2 plus its own clock at stratum 3.
The fourth server syncs to servers 1,2,3 plus its own clock at stratum 4.

All other hosts on the network sync to servers 2,3,4.

Plus in the rc file (on servers and hosts), I run ntpdate specifying
all 4 servers before starting xntpd.  (Note - it is important to set
the time to that of already running servers especially if you reboot
the main server.)

I hesitate to post this as I know it is not the intended use of NTP,
however, it does seem to work really well to keep an isolated network 
of systems sync'ed to each other.

Debbie

Debbie Galeazzi
NCR Corporation
E&M - San Diego, California
Debbie.Galeazzi@SanDiego.NCR.COM