Verifying The Ntp Configuration - Cisco ASR 5500 System Administration Manual

Verifying the NTP Configuration

balancer may distribute those packets dynamically and confuse the NTP client. NTP packets are latency and
jitter sensitive. Relaying them through a load balancer can confuse the NTP client and is not a supported
practice.
Verifying the NTP Configuration
Verify the NTP configuration is correct. Enter the following command at the Exec mode prompt:
show ntp associations
The output displays information about all NTP servers. See the output below for an example deploying two
NTP servers.
+----Peer Selection: ( ) - Rejected / No Response
|
|
|
|
|
|
|
v
==============================================================================
*10.81.254.202
The following table describes the parameters output by the show ntp associations command.
Table 2: NTP Parameters
Column Title
remote
refid
st
t
when
ASR 5500 System Administration Guide, StarOS Release 21.5
28
(x) - False Tick
(.) - Excess
(-) - Outlyer
(+) - Candidate
(#) - Selected
(*) - System Peer
(o) - PPS Peer
remote refid
.GPS.
Description
List of the current NTP servers. One of these characters precedes each IP address to
show the server's current condition:
• ( ) Rejected/No response
• X False tick
• . Excess
• - Outlyer
• + Candidate
• # Selected
• * System peer
• (o) PPS peer
Last reported NTP reference to which the server is synchronizing.
NTP server stratum level.
Communication type: broadcast, multicast, etc.
Number of seconds since the last contact.
st t when poll reach delay
1 u 160 1024 377 21.516
System Settings
offset jitter
0.019 0.009