SPECTRACOM (GPS) - no server suitable forsynchronization found - NTP

This is a discussion on SPECTRACOM (GPS) - no server suitable forsynchronization found - NTP ; Hello All, I have one GPS "SPECTRACOM(2) - stratum=0", so i connected on Sparc T1(Solaris 9) through serial port, i know that my sparc is my stratum 1, but is wrong? Sparc: bash-2.05# /usr/local/bin/ntptrace localhost localhost: stratum 1, offset -0.000004, ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: SPECTRACOM (GPS) - no server suitable forsynchronization found

  1. SPECTRACOM (GPS) - no server suitable forsynchronization found

    Hello All,

    I have one GPS "SPECTRACOM(2) - stratum=0", so i connected on Sparc
    T1(Solaris 9) through serial port, i know that my sparc is my stratum
    1, but is wrong?

    Sparc:
    bash-2.05# /usr/local/bin/ntptrace localhost
    localhost: stratum 1, offset -0.000004, root distance 0.000000, refid 'WWVB'
    ---------------------------------------------------------------------------------------------------------------
    bash-2.05# /usr/local/bin/ntpdate -q localhost
    Looking for host localhost and service ntp
    host found : localhost
    server ::1, stratum 0, offset 0.000000, delay 0.00000
    18 Sep 14:48:32 ntpdate[2223]: no server suitable for synchronization found

    after sniffing my interface i got:
    NTP: ----- Network Time Protocol -----
    NTP:
    NTP: Leap = 0x0 (OK)
    NTP: Version = 4
    NTP: Mode = 3 (client)
    NTP: Stratum = 2 (secondary reference)
    NTP: Poll = 10
    NTP: Precision = 237 seconds
    NTP: Synchronizing distance = 0x0000.0073 (0.001755)
    NTP: Synchronizing dispersion = 0x001d.96fb (29.589767)
    NTP: Reference clock = 200.225.64.68 (br-nsps18)
    NTP: Reference time = 0xc89c381e.6ec83ec8 (Sun Aug 27 12:26:22 2006)
    NTP: Originate time = 0xc8b943c8.ad2cfe21 (Mon Sep 18 13:11:52 2006)
    NTP: Receive time = 0xc8b943c2.6ce1c582 (Mon Sep 18 13:11:46 2006)
    NTP: Transmit time = 0xc8b947c4.6c6d9381 (Mon Sep 18 13:28:52 2006)
    UDP: Destination port = 123 (NTP)
    NTP: ----- Network Time Protocol -----
    NTP:
    NTP: Leap = 0x0 (OK)
    NTP: Version = 4
    NTP: Mode = 4 (server)
    NTP: Stratum = 1 (primary reference)
    NTP: Poll = 10
    NTP: Precision = 236 seconds
    NTP: Synchronizing distance = 0x0000.0000 (0.000000)
    NTP: Synchronizing dispersion = 0x001d.8d74 (29.552551)
    NTP: Reference clock = WWVB
    NTP: Reference time = 0xc89b38a4.dc08377a (Sat Aug 26 18:16:20 2006)
    NTP: Originate time = 0xc8b947c4.6c6d9381 (Mon Sep 18 13:28:52 2006)
    NTP: Receive time = 0xc8b947ca.ad85d3fb (Mon Sep 18 13:28:58 2006)
    NTP: Transmit time = 0xc8b947ca.ad9a8f33 (Mon Sep 18 13:28:58 2006)
    UDP: Destination port = 123 (NTP)
    NTP: ----- Network Time Protocol -----
    NTP:
    NTP: Leap = 0x3 (alarm condition (clock unsynchronized))
    NTP: Version = 4
    NTP: Mode = 1 (symmetric active)
    NTP: Stratum = 0 (unspecified)
    NTP: Poll = 8
    NTP: Precision = 235 seconds
    NTP: Synchronizing distance = 0x0000.0000 (0.000000)
    NTP: Synchronizing dispersion = 0x0008.fb0b (8.980637)
    NTP: Reference clock = INIT
    NTP: Reference time = 0x00000000.00000000 (Thu Feb 7 04:28:16 2036)
    NTP: Originate time = 0x00000000.00000000 (Thu Feb 7 04:28:16 2036)
    NTP: Receive time = 0x00000000.00000000 (Thu Feb 7 04:28:16 2036)
    NTP: Transmit time = 0xc8b9480d.bf7b96e8 (Mon Sep 18 13:30:05 2006)

    I don't understand what is wrong..

    Where i took this time "Feb 7 2036 OR Aug 26 2006"?

    Maybe my GPS's time it's wrong?

    Can anyone help me please?

    I appreciate some help!!!!

    Thanks a lot,

    Marcos Luiz Onisto
    _______________________________________________
    questions mailing list
    questions@lists.ntp.isc.org
    https://lists.ntp.isc.org/mailman/listinfo/questions


  2. Re: SPECTRACOM (GPS) - no server suitable for synchronization found

    What does 'ntpq -p' show on the host with the Spectracom clock?

    H

  3. Re: SPECTRACOM (GPS) - no server suitable forsynchronization found

    Hello Harlan,

    bash-2.05# ntpq -p
    remote refid st t when poll reach delay offset disp
    ================================================== ============================
    WWVB_SPEC(2) .WWVB. 0 l 23d 64 0 0.00 0.000 0.00
    host19 . STEP. 16 u - 1024 0
    0.00 0.000 0.00

    What is wrong?

    Thanks a lot,

    Marcos


    On 9/18/06, Harlan Stenn wrote:
    > What does 'ntpq -p' show on the host with the Spectracom clock?
    >
    > H
    >
    > _______________________________________________
    > questions mailing list
    > questions@lists.ntp.isc.org
    > https://lists.ntp.isc.org/mailman/listinfo/questions
    >

    _______________________________________________
    questions mailing list
    questions@lists.ntp.isc.org
    https://lists.ntp.isc.org/mailman/listinfo/questions


  4. SPECTRACOM (GPS) - no server suitable for synchronization found

    In article ,
    mlonisto@gmail.com (Marcos Onisto) wrote:

    > bash-2.05# /usr/local/bin/ntpdate -q localhost


    I wouldn't use ntpdate on the same machine, but if I did, I would use -d
    as it gives more information and is documnented as not using port 123 as
    source.

    > NTP: Precision = 237 seconds


    This value is not possible. Precision is always a power of two and
    generally a relatively large negative power. I suspect you have
    a broken protocol analyzer.

    > NTP: Synchronizing dispersion = 0x001d.96fb (29.589767)


    Estimated error. The drop dead value is about 1.0 (and that is
    after adding root distance).

    > NTP: Reference clock = 200.225.64.68 (br-nsps18)
    > NTP: Reference time = 0xc89c381e.6ec83ec8 (Sun Aug 27 12:26:22 2006)


    Time hasn't been updated since August 27th.

    > NTP: Mode = 1 (symmetric active)


    Why are you using this mode? Is this a w32time, which is known to have
    this bug.

    > Where i took this time "Feb 7 2036 OR Aug 26 2006"?


    This is the value you get when the binary value of the time is all
    zeroes, i.e. it means the time has never been set on the machine that
    is sending this value.

    > Maybe my GPS's time it's wrong?


    You are claiming to use WWVB, not GPS, and it is not returning times at all.

  5. Re: SPECTRACOM (GPS) - no server suitable for synchronization found

    On Mon, 18 Sep 2006 22:09:41 +0100 in comp.protocols.time.ntp,
    david@djwhome.demon.co.uk (David Woolley) wrote:

    >In article ,
    >mlonisto@gmail.com (Marcos Onisto) wrote:


    >> NTP: Precision = 237 seconds

    >
    >This value is not possible. Precision is always a power of two and
    >generally a relatively large negative power. I suspect you have
    >a broken protocol analyzer.


    Stratum 0 report says 235, 1 says 236, 2 says 237: perhaps a bug when
    reporting positive precisions -- 2^35, 2^36, 2^37, doubling each
    stratum?

    --
    Thanks. Take care, Brian Inglis Calgary, Alberta, Canada

    Brian.Inglis@CSi.com (Brian[dot]Inglis{at}SystematicSW[dot]ab[dot]ca)
    fake address use address above to reply

  6. Re: SPECTRACOM (GPS) - no server suitable for synchronization found

    In article ,
    Brian Inglis wrote:

    > Stratum 0 report says 235, 1 says 236, 2 says 237: perhaps a bug when
    > reporting positive precisions -- 2^35, 2^36, 2^37, doubling each
    > stratum?


    That doesn't make any sense at all. Typical values are around 2^-13,
    and the value should not be a function of stratum; it depends only
    on the machine that is sending the value.

    A correlation also doesn't make sense as printing the raw byte, as both
    precision and stratum have a byte to themselves.

    As an uninterpreted value, 235 would be -21, which is rather good:
    2^-21 = 100ns, but not impossible. 236 and 237 are 1 microsecond and
    10 microseconds, respectively.

    I think it is printing the uninterpreted, signed, logarithmic value as
    though it were an unsigned, linear, number of seconds, and the correlation
    with stratum is coincidental.

+ Reply to Thread