Veröffentlicht 24. Oktober 200618 j Hallo. Wir haben hier mehrere Linux-Server, die die korrekte Uhrzeit benötigen. Auf allen drei läuft der NTP ohne Bauschschmerzen in /var/log/ntp. Die Uhrzeit (date +%H%M%S) ist auch halbwegs korrekt, aber die Anzeige(n) verstehe ich nicht. "Border" ist ne Windows-Firewall-Maschine. "GPS-Clock" ist ne echte GPS-Clock. lx1:~ # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) LOCAL(0) 10 l 43 64 377 0.000 0.000 0.004 border.FIRMA. 129.69.1.153 2 u 36 64 7 0.379 616.761 7.726 *gps-clock.FIRMA 0.0.0.0 1 u 39 64 377 1.957 -23.311 52.209 li2:/var/log # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) LOCAL(0) 10 l 15 64 377 0.000 0.000 0.001 border.FIRMA. 129.69.1.153 2 u 10 64 7 0.289 581.340 27.873 *gps-clock.FIRMA 0.0.0.0 1 u 3 64 377 1.919 -66.774 24.389 li1.FIRMA.d .DROP. 16 u 962 64 0 0.000 0.000 4000.00 li2.FIRMA.d .INIT. 16 u - 512 0 0.000 0.000 4000.00 li3.FIRMA.d .INIT. 16 u 41 128 0 0.000 0.000 4000.00 xlx1.FIRMA.d 172.16.1.100 2 u 7 64 377 0.201 -20.366 24.218 lx2.FIRMA.d LOCAL(0) 11 u 31 64 3 0.180 -37.928 9.472 li3:/var/log # ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== LOCAL(0) LOCAL(0) 10 l 57 64 3 0.000 0.000 0.002 border.FIRMA. 1xx.xx.x.153 2 u 57 64 3 0.383 651.094 58.092 gps-clock.FIRMA 0.0.0.0 1 u 53 64 3 2.275 -46.746 61.747 li1.FIRMA.d .DROP. 16 u 971 64 0 0.000 0.000 4000.00 li2.FIRMA.d .DROP. 16 u 273 64 0 0.000 0.000 4000.00 li3.FIRMA.d .INIT. 16 u - 64 0 0.000 0.000 4000.00 lx1.FIRMA.d 172.16.1.100 2 u 52 64 3 0.159 -8.432 52.716 lx2.FIRMA.d .DROP. 16 u 818 64 0 0.000 0.000 4000.00 Kann da jemand Licht drauf werfen? Ciao.
24. Oktober 200618 j lx1:~ # ntpq -p remote refid st t when poll reach delay offset jitter ================================================== LOCAL(0) LOCAL(0) 10 l 43 64 377 0.000 0.000 0.004 border.FIRMA. 129.69.1.153 2 u 36 64 7 0.379 616.761 7.726 *gps-clock.FIRMA 0.0.0.0 1 u 39 64 377 1.957 -23.311 52.209 The remote (server name) column depicts the hosts specified in the local host’s configuration file plus other hosts that are configured as peers with the local host. The host address can be preceded by the following special characters: * indicates the current synchronization source. # indicates that the host is selected for synchronization, but distance from the host to the server exceeds the maximum value. o indicates that the host is selected for synchronization, and the PPS signal is in use. + indicates the host included in the final synchronization selection set. x indicates that the host is the designated false ticker by the intersection algorithm. . indicates that the host is selected from the end of the candidate list. - indicates a host discarded by the clustering algorithm. blank indicates a host is discarded due to high stratum and/or failed sanity checks. The refid (reference identification) column indicates the current source of synchronization for the remote host. .WWVB. indicates that the host uses a radio clock that receives time signals from the U.S. government radio station WWVB. The st (stratum) column indicates the stratum level of the remote host. The t (types) column denotes the available types, which include l=local (such as a GPS clock) u=unicast (this is the common type) m = multicast b= broadcast - = netaddr (usually 0) The when column indicates the number of seconds since the remote host response was received. The poll (poll period) column indicates the polling interval to the remote host, as determined by xntpd. You can define the minimum polling interval with the minpoll option in the peer, server, or broadcast definitions in the /etc/ntp.conf file. Some popular values for network connections include 512 and 1024 seconds (approximately 8 mins. and 17 mins.). Systems with external clocks, like GPS, must poll every 64 seconds or less. The reach (reachability) column indicates how successful attempts to reach the server are. This is an 8-bit shift register with the most recent probe in the 2^0 position. The value 001 indicates the most recent probe was answered, while 357 indicates one probe was not answered. The value 377 indicates that all the recent probes have been answered. The delay (round trip time) column indicates the time (in milliseconds) taken by the reply packet to return in response, to a query sent by the server. The offset (time difference) column indicates the time difference (in milliseconds) between the server’s clock and the client’s clock. When this number exceeds 128, and the message synchronization lost appears in the log file. The disp (dispersion) column indicates the difference in the offset measurement between two samples. This is an error-bound estimate. The dispersion is a primary measure of the network service quality. s'Amstel
Archiv
Dieses Thema wurde archiviert und kann nicht mehr beantwortet werden.