sysconf ntp status
Display the NTP service status.
Refer to Parameters for a description of the parameters that are displayed after running sysconf ntp status.
TIP The command sysconf ntp status sends packets to the configured NTP servers. The response time from the server using unreliable UDP protocol, especially over large distances, is random due to the network delay, server availability etc. If no response is received from the server, the command eventually times out after some attempts; this causes a ‘random’ delay in the command output. Five-to-ten seconds seems to be the timeout period if no response is received from the server. The default timeout is 5000 milliseconds. Note that since the command retries each query once after a timeout, the total waiting time for a timeout will be twice the timeout value set. For these reasons, you might see the command output begin, then pause for several seconds, before resuming. In other network configurations, and with "nearby" fast-responding NTP servers configured, you might never notice a pause.
NOTE It can take a few minutes to synchronize the NTP server. Checking immediately might return an error.
Parameters
The following parameters are displayed after running sysconf ntp status:
| Parameter | Description |
|---|---|
| remote |
Name of the remote NTP server. A plus (+) before an NTP server name means that it is a good candidate for synchronization. More than one NTP server could be a good candidate. An asterisk (*) before an NTP server name means that the it is the source of synchronization and the client has been synchronized to it. Only one NTP server at a time will be chosen as the source of synchronization. |
| st | Stratum of the remote peer. |
| t |
The type of peer. Can be one of the following: >local >unicast >multicast >broadcast |
| when | Time the last packet was received ( in seconds). |
| poll | How frequently to query the server (in seconds). |
| reach | Octal bitmask of success or failure of the last 8 queries. |
| delay | Network round trip time (in milliseconds). |
| offset | Difference between the local clock and remote clock (in milliseconds) |
| jitter | Difference of successive time values from the server. |
User Privileges
Users with the following privileges can perform this command:
>Admin
>Operator
>Monitor
Syntax
sysconf ntp status
Example
lunash:> sysconf ntp status NTP is running
NTP is enabled Peers:
==============================================================================
remote refid st t when poll reach delay offset jitter
==============================================================================
*LOCAL(0) LOCL. 10 l 15 64 7 0.000 0.000 0.000 ============================================================================== Associations: ============================================================================== ind assid status conf reach auth condition last_event cnt =========================================================== 1 12393 963a yes yes none sys.peer sys_peer 3 ============================================================================== NTP Time: ============================================================================== ntp_gettime() returns code 0 (OK) time d2407aa3.4e858000 Wed, Oct 12 2011 13:44:19.306, (.306725), maximum error 8020716 us, estimated error 0 us ntp_adjtime() returns code 0 (OK) modes 0x0 (), offset 0.000 us, frequency 0.000 ppm, interval 1 s, maximum error 8020716 us, estimated error 0 us, status 0x1 (PLL), time constant 2, precision 1.000 us, tolerance 512 ppm, ============================================================================== Command Result : 0 (Success)
