Re: [SLE] ntp failure

From: Dave Howorth (dhoworth_at_mrc-lmb.cam.ac.uk)
Date: 11/08/05

  • Next message: Kevanf1: "Re: [SLE] [OTAnn] Feedback"
    To: suse-linux-e@suse.com
    Date: Tue, 08 Nov 2005 10:07:30 +0000
    
    

    On Mon, 2005-11-07 at 19:21 +0100, Joachim Schrod wrote:

    > E.g., my internal time server has the output
    >
    > remote refid st t when poll reach delay offset jitter
    > ==============================================================================
    > LOCAL(0) LOCAL(0) 10 l - 64 377 0.000 0.000 0.008
    > *ntp2.ptb.de .PTB. 1 u 887 1024 377 44.424 0.697 0.826
    > +rustime01.rus.u .DCFp. 1 u 968 1024 377 38.228 -2.858 0.927
    > +hora.cs.tu-berl .PPS. 1 u 3 1024 377 48.561 -3.353 1.365
    >
    > This means I'm synchronized to PTB, and if that connection gets lost, rustime01
    > and hora could take over. (All three servers are stratum 1 servers and give
    > definitive times. PTB is the reference time source for Germany.)

    I don't know your situation, but many readers of this list are
    individuals rather than network administrators, so perhaps it's worth
    pointing out for those who don't know that individuals should generally
    not use stratum 1 servers. See for example:

    http://ntp.isc.org/bin/view/Servers/RulesOfEngagement
    "As the load on the hosts supporting NTP primary (stratum 1) time
    service is heavy and always increasing, clients should avoid using the
    primary servers whenever possible. In most cases the accuracy of the NTP
    secondary (stratum 2) servers is only slightly degraded relative to the
    primary servers and, as a group, the secondary servers may be just as
    reliable. As a general rule, a secondary server should use a primary
    server only under the following conditions:

         1. The secondary server provides synchronization to a sizable
            population of other servers and clients on the order of 100 or
            more.
         2. The server operates with at least two and preferably three other
            secondary servers in a common synchronization subnet designed to
            provide reliable service, even if some servers or the lines
            connecting them fail.
         3. The administration(s) that operates these servers coordinates
            other servers within the region, in order to reduce the
            resources required outside that region. Note that at least some
            interregional resources are required in order to ensure reliable
            service."

    Cheers, Dave

    -- 
    Check the headers for your unsubscription address
    For additional commands send e-mail to suse-linux-e-help@suse.com
    Also check the archives at http://lists.suse.com
    Please read the FAQs: suse-linux-e-faq@suse.com
    

  • Next message: Kevanf1: "Re: [SLE] [OTAnn] Feedback"

    Relevant Pages

    • Cannot remove SMS server from AdminUI
      ... We have one central primary SMS server and two primary servers below it. ... child secondaries for each primary server). ...
      (microsoft.public.sms.admin)
    • Re: Cannot remove SMS server from AdminUI
      ... SMS 2003 Technical FAQ: ... > We have one central primary SMS server and two primary servers below it. ... This removed both offending SMS from the SMS ...
      (microsoft.public.sms.admin)
    • Time Sync
      ... can't get my primary servers to sync with my master ... root domain and the primary servers are in the child ... I can also sync using net time ...
      (microsoft.public.win2000.general)
    • Re: Computers in AD, users in NT 4 domain
      ... The "given" that I failed to mention before is that our primary servers are ... and will remain UNIX based. ... NT4 domain - the SAMBA server will participate in an NT4 domain but I don't ...
      (microsoft.public.windows.server.active_directory)
    • Re: Computers in AD, users in NT 4 domain
      ... The "given" that I failed to mention before is that our primary servers are ... and will remain UNIX based. ... NT4 domain - the SAMBA server will participate in an NT4 domain but I don't ...
      (microsoft.public.windows.server.general)