Re: Help with xntp config ( xntpd on AIX 5.1 and 5.2 )

From: those who know me have no need of my name (not-a-real-address_at_usa.net)
Date: 05/21/04


Date: 21 May 2004 17:06:38 GMT

in comp.unix.admin i read:

>I'm trying to setup an ntp hierarchy and I'm getting more and more
>confused by the stratum, server, peer, fudge, and prefer settings in
>the /etc/ntp.conf file.

really? did you search using google groups before posting? there's plenty
of documentation on what each of those things does, when it's useful, &c.
there's an entire newsgroup devoted to ntp: comp.protocol.ntp -- which i'll
grant sounds like it's all about the protocol, but is also used to discuss
ntp in general, including configuration and conceptual issues.

there is a faq as well -- which points to a document which discusses
setting up a local ntp hierarchy -- i hope you've looked at it.

>We have 4 very distinct environments (DEV, TEST, QA, and PROD) each
>with between 3 and 10 AIX 5L images.
>
>I would like one server in the PROD environment to be the one system
>that syncs its time with clocks outside of our company. Would this
>system be considered a stratum 1 system?

no.

>Also, the other systems in the PROD environment would sync to this.

what happens if that one server is down?

>I would also like one server in the other 3 environments to sync to
>the "company time master" from above. Also, the other systems in the
>same environment(Test, Dev, or QA) would sync to these 3 systems.

sounds like your whole company's would be unsync'd when that one server is
down. often that's acceptable, good hardware won't drift too much over
some days waiting for the main time server to return to service.

>Would these 3 systems be stratum 2?
>
>Thus, would all my other systems be stratum 3 (including those in the
>PROD environment that I would sync to the stratum 1 system mentioned
>above)?

no and no.

your main time server would only be stratum 1 if it were receiving a tick
from a trusted clock source (e.g., a gps clock or such). since it'll be
receiving time from an external ntp server it will be at most stratum 2 if
you sync to a stratum 1, which you don't really have enough systems to
warrant, so more likely your main time server would be at stratum 3.

unless you are in a penis size contest the stratum at which you sync is
typically not a source of concern.

>Or, would I be better off spreading out the stratum priorities to say
>1, 3, & 5?

stratums are not priorities, per se.

>My confusion stems from the various posts I've read and the lack of
>information available about how to setup ntp.conf in the AIX man
>pages.
>
>Clarification of how I would use the server, peer and fudge keywords
>would be very helpful.

servers provide time to clients. peers share time with each other.
fudging is used when a config entry's default behavior isn't quite
what is needed.

-- 
a signature


Relevant Pages

  • Re: Peer to Peer
    ... My authoritative server would be my ciso router that does sync with stratum ... "problems with w32time" followed the instructions and it seemed to work. ... Configure the machine to sync with an outside time source: ... w32tm -s to run periodically if the time service does not function on peer ...
    (comp.protocols.time.ntp)
  • Re: Stratum 1 configuration hints
    ... The GPS is the only clock source though and I'm wondering whether a stratum ... server should peer with others. ... should peer or server be ... Why, except as a backup, and as a backup you can use a higher stratum ...
    (comp.protocols.time.ntp)
  • Cannot synchronize to server with local clock
    ... fudged at a high stratum like 8 or 10. ... The *server* stratum varies from 16 ... Without sync machines will diverge. ... and another one stratum 14 on a given client. ...
    (comp.protocols.time.ntp)
  • Re: Architecture / best practice for small/medium company setups
    ... Make your best one the "master" for your network. ... Take your 2nd best server and have it sync to your master and whatever other ... and assign its local refclock to a stratum 2 worse than ...
    (comp.protocols.time.ntp)
  • Re: Cannot synchronize to server with local clock
    ... >> stratum 14 on a given client. ... No "prefer" on server in this case! ... The given client is not a leaf. ... not against MCT, last time I checked. ...
    (comp.protocols.time.ntp)