[ntp:questions] DIGITAL CLOCK DISTRIBUTOR / SSU - GTI/C - GPS

Marcos Onisto mlonisto at gmail.com
Tue Nov 21 10:59:37 UTC 2006


Hello All,

Is there someone that already used this hardware or know this hardware?

Thanks a lot,

Marcos


On 11/7/06, Marcos Onisto <mlonisto at gmail.com> wrote:
> Hello All,
>
> I have many doubt's about my equipment. I don't know how it's work.
>
> I have one plate (GPS) in a Rack on my Data Center, follow below some
> information:
>
> DIGITAL CLOCK DISTRIBUTOR / SSU
> LOCAL PRIMARY REFERENCE
> DCD - LPR/C
> GTI/C - GPS
>
> This equipment have a cable that begin of a plug DB9 and It have about
> 9 meter. There is a converter on the end of this cable that convert
> the DB9 to DB25.
>
> My firt doubt is about the second cable that begin of the converter.
> The end of this cable there are two DB25. My doubt is about the two
> DB25. Is it possible 2 box ( Sun - Solaris ) compete using the same
> channel? Or It can be wrong?
>
> The second doubt is about the NTP consult. I'd never got a consult on
> my equipment, but on the firt time that I connect my box's on the GPS,
> after five minutes I got the syncronism, but I'd never got a consult.
> Today It isn't work and I dont know what.
>
> Who knows how can I check out if my equipment GPS is working well? Or
> if possible two box's compete the same channel? Or only one equipment
> is possible to work on this case?
>
> Follow below some commands that i did on my box's:
>
> [ntpadm at host18:~]$ /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
> 30 Oct 14:35:00 ntpdate[2574]: no server suitable for synchronization found
>
>
> [ntpadm at host19:~]$ /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
> 30 Oct 14:36:06 ntpdate[2178]: no server suitable for synchronization found
>
>
> [ntpadm at host18:~]$ /usr/local/bin/ntpq
> ntpq> pe
>     remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
> SPECTRACOM(2)   .WWVB.           0 l  15d   64    0    0.000    0.000 4000.00
> host19       .STEP.          16 u    - 1024    0    0.000    0.000 4000.00
> host19-hme0  .STEP.          16 u    - 1024    0    0.000    0.000 4000.00
> ntpq> as
> ind assID status  conf reach auth condition  last_event cnt
> ===========================================================
>  1 26964  8063   yes   yes  none    reject  lost reach  6
>  2 26965  8000   yes   yes  none    reject
>  3 26966  8000   yes   yes  none    reject
>
>
> [ntpadm at host19:~]$ /usr/local/bin/ntpq
> ntpq> pe
>     remote           refid      st t when poll reach   delay   offset  jitter
> ==============================================================================
> SPECTRACOM(2)   .WWVB.           0 l  15d   64    0    0.000    0.000 4000.00
> host18       .DROP.          16 u  936 1024    0    0.000    0.000 4000.00
> host18-hme0  .DROP.          16 u  964 1024    0    0.000    0.000 4000.00
> ntpq> as
> ind assID status  conf reach auth condition  last_event cnt
> ===========================================================
>  1  1084  8063   yes   yes  none    reject  lost reach  6
>  2  1085  a000   yes   yes  none    reject
>  3  1086  a000   yes   yes  none    reject
>
> Can someone show me the light of the end of the tunnel?
>
> I appreciate some help.
>
> Thanks a lot,
>
> Marcos
>



More information about the questions mailing list