Skip to main content
NetApp Knowledge Base

In what condition will E-Series system trigger an alert of NTP synchronization failure?

  1. Last updated
  2. Save as PDF
Views:
237
Visibility:
Public
Votes:
2
Category:
e-series-systems
Specialty:
esg
Last Updated:

Applies to

E-Series system

Answer

  • E-series triggers an alert if one or both NTP servers (primary or second) can't be reached. Even if the primary NTP server works, the secondary can still trigger an alert. 
  • NTP sync on E-Series is attempted three times after which it's marked failed. 
  • The system will send an alert once the third attempt fails
  • This can be seen in trace buffer logs for E-Series system:
12/15/20-01:21:15.119830 00 sntpEventTask cmgr cffff sntpEvtHdlr: Checking Primary NTP Server
12/15/20-01:21:15.119832 00 sntpEventTask cmgr cffff sntpQrySrvr: Using NTP IPv4Addr "" ...
12/15/20-01:21:15.119832 00 sntpEventTask cmgr cffff sntpEvtHdlr: stage : 320
12/15/20-01:21:26.119952 00 sntpEventTask vkiCE ffff CE_ERROR 12/15/20-01:21:26.720 sntpcTimeGet: Timedout. No response from base OS
12/15/20-01:21:26.119955 00 sntpEventTask cmgr cffff sntpQuery: Query attempt 1 to NTP Server <IP Address>, Result: -1   <-----The first-time attempt failure
12/15/20-01:21:37.120092 00 sntpEventTask cmgr cffff sntpQuery: Query attempt 2 to NTP Server <IP Address>, Result: -1   <-----The second-time attempt failure
12/15/20-01:21:48.120222 00 sntpEventTask vkiCE ffff CE_ERROR 12/15/20-01:21:48.720 sntpcTimeGet: Timedout. No response from base OS
12/15/20-01:21:48.120225 00 sntpEventTask cmgr cffff sntpQuery: Query attempt 3 to NTP Server <IP Address>, Result: -1    <-----The third-time attempt failure
12/15/20-01:21:48.120226 00 sntpEventTask cmgr cffff sntpEvtHdlr: stage : 330
12/15/20-01:21:48.120227 00 sntpEventTask cmgr cffff sntpEvtHdlr: stage : 331
12/15/20-01:21:48.123183 00 sntpEventTask cmgr cffff Ctlr NTP; Query to NTP Server Failed (22) NeedsAttention submitted for controller xxxxxxxx   <-----Finally marked it as failed

Additional Information

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.