Skip to main content
NetApp Knowledge Base

Is NetApp hardware faulty when ONTAP reports NTP clock skew detected with normal network connectivity?

  1. Last updated
  2. Save as PDF
Views:
48
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • Network Time Protocol (NTP)
  • Multiple external NTP servers

Answer

  • No,NetApp hardware is not faulty in this scenario.
  • The EMS event NTP CLOCK SKEW DETECTED occurs when the time difference between the ONTAP system clock and an NTP server exceeds the configured threshold.
  • Observed behavior:
    • EMS logs show no network port link down or link up events at the time of the alert.

Indicates stable physical network connectivity.

    • ntpdc -p output shows at least one NTP peer in a synchronized state.

Confirms ONTAP NTP functionality is operating correctly.

    • A large offset is observed on only one NTP server, while other peers remain synchronized.
    • Isolates the issue to a specific external NTP server.

remote           local       st poll reach  delay    offset      disp

========================================================================

=<NTP_Server_A>  <local>      5 1024  377   0.00008  -0.003680   0.13898

=<NTP_Server_B>  <local>      6 1024  377   0.00049 +154.4744   0.12419

  • Based on the available evidence, the condition is caused by an external NTP server time offset and not by a NetApp hardware or network failure.
  • Conclusion:
    • ONTAP system clock and networking operate as expected.
    • At least one NTP server remains synchronized.
    • The clock skew is isolated to a specific external NTP server.
    • No NetApp hardware replacement or corrective action is required.

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.