>>I wish Novell had never used that word "primary" since it's so
>>confusing. SINGLE (if you have only one) or REFERENCE (if you want
>>redundancy) is the highest level of the time sync. hierarchy in
>>Netware. PRIMARY servers want to get their time from a SINGLE or
>>REFERENCE server but will redistribute it to SECONDARY servers.
>>Nobody but clients will trust a SECONDARY.
>>I've seen quite knowledgable people stumble over this bit of
> Alas..... et tu Brute?
> SINGLE is mutially exclusive with PRIMARY OR REFERENCE.
> REFERENCE has a voiting power of 16, while Primary only has 1 (or 8?).
> REF will not change it's time so other PRI's will eventually converge to
> the REF server.
What can I say? A while back, I got a call from one of the corporate
networking guys, someone whose opinion I trust. He was scanning the
timesync report in DSREPAIR and saw that I had a PRIMARY. He felt it
was inappropriate for a departmental server to be providing time for
the whole corp. net. I had to explain that PRIMARY doesn't mean what
it looks like; that his pair of REFERENCE servers were the(1) ones
that provide time to the others and that my PRIMARY server(2)
redistributes that time to our other departmental servers so we don't
hit his REFERENCE boxes so much.
Theoretically 33 PRIMARY servers that all pretty much agreed on the
*wrong* time could outvote the REFERENCE servers, but I don't expect
to live long enough to see it make a significant difference in
anyone's life. In our tree there *are* no other PRIMARY servers, so
my box is never going to win an argument.
Thanks for pointing out some of the internal details of time sync.
1. I actually wrote the word "primary" here at first. See how
confusing it is?
2. I still want to write "primarily" here. I had to oversimplify the
operation of a PRIMARY server to prevent overcomplicating my sentence.
"Where's the kaboom? There was supposed to be an Earth-shattering kaboom!"
-- Marvin Martian, 01/01/2000 00:00:00