Cisco DNCS System Release 2.7 3.7 4.2 Installationsanleitung
4-4
DBDS System Time Maintenance
78-4011510-01 Rev C
DBDS System Time Synchronization Maintenance,
Continued
Verifying DNCS Connectivity
This section provides a procedure for running the Network Time Protocol Query
(NTPQ) on the DNCS to verify that the DNCS is synchronized to the correct timing
source.
Note: You can also verify the DNCS connectivity by reading the ntp.log file located
Note: You can also verify the DNCS connectivity by reading the ntp.log file located
in the /var/adm/log/ directory. The log file should indicate that the xntpd process
is synchronized to the correct timing source (NTP server or GPS).
Follow these steps to run the NTPQ on the DNCS to verify that the DNCS is
Follow these steps to run the NTPQ on the DNCS to verify that the DNCS is
synchronized to the correct timing source.
1.
From a DNCS xterm window type /usr/local/xntpd/ntpq and press Enter.
2.
Does the ntpq> prompt appear on your screen?
•
•
If yes, go to step 3.
•
If no, contact Cisco Services for assistance.
3.
At the ntpq> prompt, type peers and then press Enter.
Result: A result similar to one of the following examples appears on the
Result: A result similar to one of the following examples appears on the
screen.
Note: The appearance and contents of the result will vary according to your
Note: The appearance and contents of the result will vary according to your
system release version.
GPS Example
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
*GENERIC(1) .GPS. 0 l 44 64 377 0.000 -4.482 4000.00
LOCAL(0) .LCL 0 l 43 64 377 0.000 0.000 0.008
NTP Server Example
ntpq> peers
remote refid st t when poll reach delay offset jitter
==============================================================================
*192.168.41.253 130.207.244.240 2 u 962 1024 377 1.785 -0.221 0.174
GENERIC(1) .GPS. 0 l - 64 0 0.000 0.000 4000.00
LOCAL(0) LOCAL(0) 10 l 32 64 377 0.000 0.000 0.008
Notes:
•
•
The asterisk (*) in front of GENERIC (as shown in the above example)
indicates that the DNCS is using the GPS as a reference for clock
information, and that the DNCS is synchronized to the GPS.
•
If the asterisk (*) is in front of an IP address, a URL, or a server name (as
shown in the above example), this indicates that the DNCS is using an
NTP server as a reference for clock information, and that the DNCS is
synchronized to the NTP server.
Important: If the asterisk (*) is in front of LOCAL, then the DNCS is not
synchronized to the GPS or the NTP server. It is synchronized with the
hardware clock on the server. This situation must be corrected immediately.