Skip to main content
NetApp Knowledge Base

Resolving Skew Between Compliance Clock and System Clock

  1. Last updated
  2. Save as PDF
Views:
67
Visibility:
Public
Votes:
0
Category:
snaplock
Specialty:
dp
Last Updated:

Applies to

  • ONTAP 9.14.1
  • SnapLock

Issue

  • A skew was identified between the compliance clock and the system clock
  • Skew Between Compliance Clock and System Clock is 32093 seconds
  • EMS logs indicated a cluster reboot around the same time:
Sat Feb 08 17:46:36 -0600 [node1: mgwd: clus.reboot.rebootDetected: notice]: Cluster reboot was detected at 2/8/2025 17:46:36. Sequence number for the cluster reboot was 3. Estimated beginning time of the cluster reboot was 2/8/2025 08:50:53
  • The skew was essentially the time difference between the reboot detection and the estimated reboot start time, totaling 32,143 seconds

 

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.