cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3454
Views
0
Helpful
3
Replies

ASR9K NTP Question

zekebashi
Level 4
Level 4

Hello all, 

I received a report from one of the ASR9Ks and when I checked the log and did a little research using this site(http://www.cisco.com/c/en/us/td/docs/ios_xr_sw/iosxr_r4-2/error/messages/em42sems/em42ip.html) and  here is what I found out: 

 

                       1- RP/0/RSP0/CPU0::Apr 30 12:46:17.450 : ntpd[240]: %IP-IP_NTP-5-SYNC_LOSS : Synchronization lost : 10.10.100.254  : System clock selection failed

 

Cisco's Error Explanation: 

a.        %IP-IP_NTP-5-SYNC_LOSS Synchronization lost : [chars] : [chars]

b.        Explanation    NTP lost synchronization due to one of the following reasons: 1. Server authentication failed 2. Access denied by remote server 3. Peer unreachable or clock selection failed 4. The association was removed 5. The clock was stepped and needs to be resynced 6. The ephemeral client association was timeout 7. ntp clear command

c.        Recommended Action    If SYNC_LOSS because 'The clock was stepped and needs to be resynced' keeps occurring constantly during time, try to exec ntp reset drift.

 

2- RP/0/RSP0/CPU0::Apr 30 12:46:17.450 : ntpd[240]: %IP-IP_NTP-5-HP_CONN_LOST : High priority NTP peer connection lost - Stratum 2->4.

 

Cisco's Error Explanation: 

a.        %IP-IP_NTP-5-HP_CONN_LOST High priority NTP peer connection lost - Stratum [dec]-[dec].

b.        Explanation    The ntp server lost the connection with a high-priority clock source. The Stratum tells the change of server stratum.

c.        Recommended Action    No action is required.

 

3- RP/0/RSP0/CPU0::Apr 30 13:03:14.121 : ntpd[240]: %IP-IP_NTP-5-HP_CONN_RECOVERED : High priority NTP peer connection recovered - Stratum 5->2.

 

Cisco's Error Explanation: 

a.        %IP-IP_NTP-5-LP_CONN_RECOVERED At least a low priority NTP peer connection was recovered - Stratum [dec]-[dec].

b.        Explanation    The ntp server recovered a connection with one of the configured clock source. The Stratum tells the change of server stratum.

c.        Recommended Action    No action is required.

 

 I'm not sure if I understand the following statements. I'd really appreciate it if someone can clarify to me what these two statements mean. 

            High priority NTP peer connection lost - Stratum 2->4.

            High priority NTP peer connection recovered - Stratum 5->2.

 

Thanks in advance. 

 

Zeke

1 Accepted Solution

Accepted Solutions

Leo Laohoo
Hall of Fame
Hall of Fame

Your ASR is loosing NTP sync.  Tell me what this client is (IP address 10.10.100.254).  

View solution in original post

3 Replies 3

Leo Laohoo
Hall of Fame
Hall of Fame

Your ASR is loosing NTP sync.  Tell me what this client is (IP address 10.10.100.254).  

Thx for the quick reply. The 10.10.100.254 is an internal NTP peer. Here is the output of the NTP assoc from this ASR9K:

RP/0/RSP0/CPU0:vacrw01001001#sh ntp associations 
Thu May  1 13:49:00.111 PDT

      address         ref clock     st  when  poll reach  delay  offset    disp
*~198.123.30.132   192.58.23.182     2  2898  1024  374    5.95   0.862  18.651
  10.10.100.252    10.10.100.253     4     9  1024  377    1.95  -1.382   0.697
  10.10.100.251    10.10.100.253     4    40  1024  377    2.08  -1.344   0.202
 ~207.26.97.57     .STEP.           16     -  1024    0    0.00   0.000   15937
 ~10.10.100.254    10.10.100.253     4   252  1024  377    3.45  -2.377  18.463
 ~10.10.100.250    10.10.100.253     4   389  1024  377    6.00  -2.489  18.186
 ~192.6.38.127     .STEP.           16     -  1024    0    0.00   0.000   15937
 ~10.10.100.249    198.123.30.132    3   965  1024  377    6.00  -1.942  19.083
 * sys_peer, # selected, + candidate, - outlayer, x falseticker, ~ configured

Much appreciated. 

Best, ~sK 

Do you see the "~" symbol?  This means it's not synchronizing.  Ideally, you want "*" on the left-hand side.  This means only 192.123.30.132, a stratum 2, is synchronizing and is most trusted. 

 

Check this peer.  Check the time and date.  Check to see if there are any NTP ACL or authentication problem.  Maybe the NTP on this peer has a long drift.  

 

Look at all your internal NTP peers (10.10.100.0), they are not synchronizing.  

 

If you can get those peers to synchronize with 198.123.30.132 see if this works.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: