Skip to main content
NetApp Knowledge Base

clockSkewExceedsFaultThreshold is caused by packets dropped

  1. Last updated
  2. Save as PDF
Views:
44
Visibility:
Public
Votes:
0
Category:
element-software
Specialty:
solidfire
Last Updated:

Applies to

NetApp Element software

Issue

  • Intermittent clockSkewExceedsFaultThreshold alerts that occur repeatedly after reboot of network switch that Bond1G is connected to.

Error Code: clockSkewExceedsFaultThreshold

Details : Time difference between the Cluster Master and node(s): {<Node-MIP>} (set of node IP Addresses) exceeds the recommended clock skew limit. To resolve the fault, use NTP servers internal to your network. If issue still persists, contact support to fix the time offset.

  • Some ping requests to storage nodes time out.

Example:
Reply from <Node-MIP>: bytes=32 time<1ms TTL=64
Request timed out.
Reply from <Node-MIP>: bytes=32 time<1ms TTL=64
Reply from <Node-MIP>: bytes=32 time<1ms TTL=64

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.