NTP Configuration

rob.leadbeater_at_lynx.co.uk
Date: 08/23/04

  • Next message: Ron Bramblett: "Addendium: Summary KZPSC-BA Raid Controller Panic"
    Date: Mon, 23 Aug 2004 10:05:43 +0100
    To: tru64-unix-managers@ornl.gov
    
    

    Hi Managers,

    For some reason NTP doesn't appear to be working correctly for us, or (probably) isn't configured correctly.

    On a two node 5.1B memory channel cluster, I've got the following ntp.conf files:

    Node1:
    server ntp0.pipex.net version 1
    server ntp1.pipex.net version 1
    server ntp2.pipex.net version 1
    peer node2-ics0 version 3

    Node2:
    server ntp0.pipex.net version 1
    server ntp1.pipex.net version 1
    server ntp2.pipex.net version 1
    peer node1-ics0 version 3

    The output from ntpq -p indicates that no peer/server was selected:

    ntpq -p
         remote refid st t when poll reach delay offset jitter
    ==============================================================================
     ntp0.pipex.net 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00
     ntp1.pipex.net 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00
     ntp2.pipex.net 0.0.0.0 16 u - 64 0 0.000 0.000 4000.00
     node2-ics0 0.0.0.0 16 u 4 64 0 0.000 0.000 4000.00

    however, if I query the external servers I can get the time OK:

    node1 # ntpdate -q ntp0.pipex.net
    server 158.43.128.33, stratum 2, offset -4.104927, delay 0.41115
    23 Aug 09:41:28 ntpdate[791358]: step time server 158.43.128.33 offset -4.104927 sec
    node1 # ntpdate -q ntp1.pipex.net
    server 158.43.128.66, stratum 2, offset -3.999647, delay 0.20505
    23 Aug 09:41:39 ntpdate[791362]: step time server 158.43.128.66 offset -3.999647 sec
    node1 # ntpdate -q ntp2.pipex.net
    server 158.43.192.66, stratum 2, offset -4.116835, delay 0.43454
    23 Aug 09:41:47 ntpdate[791393]: step time server 158.43.192.66 offset -4.116835 sec

    but querying the peer on the other node returns:

    node1 # ntpdate -q node2-ics0
    server 192.168.0.2, stratum 16, offset 7.979337, delay 0.02611
    23 Aug 09:42:02 ntpdate[791399]: no server suitable for synchronization found

    Can someone give me some pointers as to what could be wrong...?

    Cheers,

    Rob

    This message is intended only for the use of the person(s) ("The intended
    Recipient(s)") to whom it is addressed. It may contain information which
    is privileged and confidential within the meaning of applicable law. If
    you are not the intended recipient, please contact the sender as soon as
    possible. The views expressed in this communication are not necessarily
    those held by LYNX Express Limited.


  • Next message: Ron Bramblett: "Addendium: Summary KZPSC-BA Raid Controller Panic"

    Relevant Pages

    • Re: Question about NTP.CONF master and local-master commands
      ... than a single client trying to sync with a server. ... the more inaccurate the clock will be. ... NTP attempts ... I tried setting up two test servers to peer each other. ...
      (comp.os.vms)
    • Re: w32Time - External Source Sinc - HELP!!
      ... Got it, that functionallity is by design ISA default behaviour, my mistake ... Mi DC is a VPC hosted on Virtual Server 2005 R2. ... The time provider NtpClient is configured to acquire time from one ... This peer will be discarded as a time source and NtpClient will ...
      (microsoft.public.windows.server.active_directory)
    • Re: Client Server Setup
      ... So tell those people to get their network set up in a domain or ... IE Peer to peer. ... > From the systems I have worked with before its been client server setup. ... Go to a client computer right ...
      (microsoft.public.windowsxp.general)
    • New to SBS 2003 and really struggling
      ... SBS 2003 having always had Peer to Peer networks. ... I decided to upgrade our peer to peer network to SBS 2003 with I have to say ... broadband connection via an ADSL modem. ... Ethernet to the server. ...
      (microsoft.public.windows.server.sbs)
    • Re: Client Server Setup
      ... > a workgroup, and that is to have everyone with the exact same logon ... IE Peer to peer. ... >> would be 7 computers and 2 laptops, and a server if it was taken away ... Go to a client computer right ...
      (microsoft.public.windowsxp.general)