ctman47 wrote:
>
> I have 50+ NW65SP7 servers in a WAN environment. I have a reference
> server (server name = HOMNDSF5) that gets time via NTP:
...
> I have one primary server (server name = HOMNDSF3):
...
> The rest of the servers are secondary servers
That's an illegal configuration. *If* you want a Ref > Pri > Sec config,
you need *minimum* three primaries. That's not negotiable.
CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
ataubman wrote:
>
> Also, the REF must ONLY point to the external time source, not to any of
> the PRI servers.
Huh? Quite the opposite, the REF *must* point to *at least* one (better
all) primaries, otherwise the time on the REF will *never* go into sync.
Also, *all* three primary servers must point to each other *and* the
reference, otherwise time will go out of sync treewide should the REF
ever fail.
Back in the days of IPX, Timesync took care of all this fully
automatically, no matter what you configured (e.g the reference found
it's primaries automatically to vote with them). In the IP days, where
Timesync regularly can't find the setup on it's own, this is crucial.
But as a more general side-note: A reference > primary > secondary time
setup is virtualy never necessary, and unless there are very good
reasons, should be avoided. Use a simply single > secondary schema
instead, *especially* when you have an external timesource to sync with.
ataubman wrote:
> But if there is to be an external NTP
> time source then the REF must only point to it; pointing it to that and
> a PRI causes confusion as to whether the authoritative time source is
> internal or external to the tree and time provider group.
No. I think I know where you come from though. At one time, there was a
bug in Timesync, where that setup indeed wasn't working (a REF with an
external NTP source didn't properly participate in the voting with the
primaries). But as I said, that was a bug, and not a generally correct
setup, and in the meantime has been fixed.
> I assure you
> the REF only pointing to an external time source works and the tree
> certainly goes into, and maintains, time sync.
Not my experience. At least not in an all IP tree.
> > Also, *all* three primary servers must point to each other *and* the
> > reference ...
> I did say exactly that:
> > Each of the PRI servers must point to each other PRI and the REF
Yes, I just restated it for completeness.