Skip to main content
NetApp Knowledgebase

What impact does a timezone change have?

Last Updated:

Applies to

Product Model: FAS3250
OS: Clustered Data ONTAP 8.2.1


A controller in Europe with time zone Amsterdam Universal Coordinated Time (UTC)+1 needs to be changed to time zone UTC. What impact does this change have on controller operations?

The change of time zone only has an impact on the running system, if its UTC, time changes. For example, if the time is 17.00 UTC + 2 before the change, then it will be 15.00 UTC after the change. Do not change this time.

Note: It is important to remember that Kerberos authentication does not work if the time skew between client, controller and the domain controller is more than five minutes. Kerberos uses UTC when comparing the dates and times for tickets. That is, it translates the current system time from its current time zone to a common reference time. Both KDC and Client does this - which implies, if both clocks are correctly set, and both have time zone settings that are correct, the comparison of time should be correct. If either system has the wrong timezone setting, this might cause the reference time to be computed incorrectly. That is, verify if the timezone is correctly set or ensure that the calculated UTC time on all machines is the same.

Run the following command to check the timezone:

cluster::> node date show -node local

Node: node-1
Time Zone: Europe/Amsterdam
Date and Time: 11/26/2014 12:24:38 +01:00 UTC Date and Time: 11/26/2014 11:24:38
Date and Time: Wed Nov 26 12:24:38 2014 UTC Date and Time: Wed Nov 26 11:24:38 2014

Warning: The snapshot schedules depend on the current time, and not on UTC time. Also, the schedules are not automatically adjusted with a time zone or time change.

Additional Information