Resolving Skew Between Compliance Clock and System Clock
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