Trace ntp sanity checks? - NTP

This is a discussion on Trace ntp sanity checks? - NTP ; Hello, we are having problems to synchronize linux & aix ntp-clients to a ntp-broadcastserver. ntp-broadcast-packets are received by the clients, but all servers are rejected by the clients after a few minutes. we found out, that the ntp-servers do not ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Trace ntp sanity checks?

  1. Trace ntp sanity checks?

    Hello,



    we are having problems to synchronize linux & aix ntp-clients to a
    ntp-broadcastserver.

    ntp-broadcast-packets are received by the clients, but all servers are
    rejected by the clients after a few minutes.

    we found out, that the ntp-servers do not pass the sanity-checks on the
    clients and get probably rejected because of that.

    How can we further track down which of the sanity-checks fails and why...



    Thanks in advance

    Frank



    __________________________________________________ _________________

    This E-Mail is confidential. If you are not the intended recipient, you must
    not copy, disclose or use its contents. If you have received it in error,
    please inform us immediately by return E-Mail and delete the document.


    Diese E-Mail ist vertraulich. Wenn Sie nicht der rechtmäßige Empfänge
    r sind,
    dürfen Sie den Inhalt weder kopieren, verbreiten noch benutzen. Sollten S
    ie
    diese E-Mail versehentlich erhalten haben, senden Sie sie bitte an uns
    zurück und löschen sie anschließend.


    Cet e-mail est confidentiel. Si vous n'etes pas le destinataire de ce
    message, vous ne devez pas copier, divulguer ou utiliser le contenu. Si vous
    avez recu cet e-mail par erreur, veuillez nous informer en retournant ce
    message a l'expediteur et detruisez-le.


    Esta mensagem, e qualquer de seus anexos, eh confidencial e privilegiada.
    Caso voce nao seja o destinatario, nao esta autorizado a reproduzir ou
    divulgar a terceiros o conteudo desta mensagem e de qualquer anexo da mesma
    e deve apagar com os seus respectivos anexos.

    __________________________________________________ _________________

    ANDREAS STIHL AG & Co. KG
    Kommanditgesellschaft mit Sitz in Waiblingen, HRA 260269, Amtsgericht Stutt
    gart

    Persönlich haftende Gesellschafter: Hans Peter Stihl und STIHL Aktiengese
    llschaft
    mit Sitz in Waiblingen, HRB 263722, Amtsgericht Stuttgart
    Vorstand der STIHL AG: Dr. Bertram Kandziora (Vorstandsvorsitzender),

    Dr. Peter Dürolf, Jürgen Steinhauser, Wolfgang Zahn
    Vorsitzender des Aufsichtsrats der STIHL AG: Hans Peter Stihl

  2. Re: Trace ntp sanity checks?

    Frank,

    linux@stihl.de wrote:
    > Hello,
    >
    > we are having problems to synchronize linux & aix ntp-clients to a
    > ntp-broadcastserver.
    >
    > ntp-broadcast-packets are received by the clients, but all servers are
    > rejected by the clients after a few minutes.
    >
    > we found out, that the ntp-servers do not pass the sanity-checks on the
    > clients and get probably rejected because of that.
    >
    > How can we further track down which of the sanity-checks fails and why...


    If the NTP on the client has been compiled with debug option then you can
    run ntpd with the -d option ans see what it prints on the console.

    Otherwise, if the broadcast server is listed in the output of "ntpq -p" you
    can see details of the server association using the following commands.

    Print billboard of the associations:

    # ntpq -p
    remote refid st t when poll reach delay offset jitter
    ================================================== =======================
    *gateway.py.mein .GPSi. 1 u 34 64 377 0.148 -0.011 0.362

    Find out the association IDs:

    # ntpq -c as

    ind assID status conf reach auth condition last_event cnt
    ================================================== =========
    1 41266 9614 yes yes none sys.peer reachable 1

    In this case the association ID is 41266. Use the ID to find more details on
    the association:

    # ntpq -c "rv 41266"
    assID=41266 status=9614 reach, conf, sel_sys.peer, 1 event, event_reach,
    srcadr=gateway.py.meinberg.de, srcport=123, dstadr=172.16.3.27,
    dstport=123, leap=00, stratum=1, precision=-18, rootdelay=0.000,
    rootdisp=0.580, refid=GPSi, reach=377, unreach=0, hmode=3, pmode=4,
    hpoll=6, ppoll=6, flash=00 ok, keyid=0, ttl=0, offset=-0.659,
    delay=0.163, dispersion=2.055, jitter=0.307,
    reftime=cb00fb6b.000192a7 Wed, Dec 5 2007 11:26:51.000,
    org=cb00fb71.b05ff1d8 Wed, Dec 5 2007 11:26:57.688,
    rec=cb00fb71.b0814599 Wed, Dec 5 2007 11:26:57.689,
    xmt=00000000.00000000 Thu, Feb 7 2036 7:28:16.000,
    filtdelay= 0.18 0.19 0.16 0.23 0.20 0.23 0.19 0.21,
    filtoffset= -0.42 -0.61 -0.66 -0.76 -0.88 -1.04 -1.14 -1.06,
    filtdisp= 0.01 1.00 1.97 2.96 3.92 4.90 5.86 6.85

    You should not interpret the output above. It's just a quick test to show
    how to proceed.

    If you post your output of the ntpq -p and ntpq -c "rv ..." commands here
    then we may be able to help.

    And, the versions of NTP on the server and on the clients might be
    interesting ...

    Martin
    --
    Martin Burnicki

    Meinberg Funkuhren
    Bad Pyrmont
    Germany

+ Reply to Thread