Printer FriendlyEmail Article Link

STCLive Probe: Why does the REPT-DIAG TIME command show "Request timed out" for the NTP SERVERS REPORT for some NTP Servers?

Environment/Versions

STCLive 7521, 7531, 7541, 7500, 6500, 7502, 7506

Answer

The NTP Server must be configured to allow that information to be passed.   Please contact the owner of the NTP server regarding having it enabled.

Example:  NTP Server 10.32.89.89 is configured to allow the report and 10.32.90.75 is not configured.  Both NTP servers are working as can tell by the PEERS section.  The  " * " and " + " symbols before the addresses and the 377 values reach column.

<rept-diag::time:fdsa;
IP FDSA
<OK 0
<OK 0
<

   STAC-7502 14-08-08 15:31:40
M  FDSA COMPLD
   TIME OUTPUT:
   NTP PEERS
           remote           refid      st t when poll reach   delay   offset  jitter
      ==============================================================================
      *10.32.89.89     .GPS.            1 u  140  256  377    0.508   -0.045   0.031
      +10.32.90.75     128.118.25.3     3 u  183  256  377    0.294   -0.085   0.031
       LOCAL(0)        .LOCL.          10 l   33   64  377    0.000    0.000   0.031
   NTP SERVERS REPORT
      server=10.32.89.89
       assID=0 status=0415 leap_none, sync_uhf_clock, 1 event, event_clock_reset,
       version="ntpd 4.2.6p3@1.2290-o Tue Jul  5 22:39:48 UTC 2011 (1)",
       processor="i486", system="Linux/2.4.31-IPV4", leap=00, stratum=1,
       precision=-16, rootdelay=0.000, rootdisp=0.398, refid=GPS,
       reftime=d78f6bb5.967ded6e  Fri, Aug  8 2014 15:31:01.587,
       clock=d78f6bbe.d6c55c99  Fri, Aug  8 2014 15:31:10.838, peer=9953, tc=4,
       mintc=3, offset=0.001, frequency=32.521, sys_jitter=0.015,
       clk_jitter=0.015, clk_wander=0.000
      server=10.32.90.75
       10.32.90.75: timed out, nothing received
       ***Request timed out
   PTP DISABLED
;


Product : VisionWorks Probe