VNX, eNAS: Correcting Control Stations to add Brazil's 2019 NO Daylight Saving Time settings (Dell EMC Correctable)
Summary: Brazil DST Information
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
| This Article is about how to update Control stations Time zone to 2019 tzdata release . Severity Rating: Low to Medium Impact Description: Brazil has announced that it won t be observing the daylight saving time (DST) in 2019. VNX1, VNX2 and eNAS control stations use the timezone information to display system messages and events, which need to be accurate with respect to the timezone that is followed for the region. Thus they will be impacted in the sense that the information shown would be inaccurate, if the 2019 changes are not incorporated on these systems. To address this issue, an upgrade patch is delivered for such systems, which when installed, will follow the new timezone rules. The upgrade patch comes in form of an RPM package, which is installed on a control station. Note: Root access is required for the same, and it s recommended that control station be rebooted for the changes to take effect although not necessary. Following steps will help identify if the control stations are using outdated timezone data: [root@-CS0 ~]# /usr/sbin/zdump -v Brazil/East | grep 2019 /usr/sbin/zdump: warning: zone "Brazil/East" abbreviation "-03" lacks alphabetic at start Brazil/East Sun Feb 17 01:59:59 2019 UTC = Sat Feb 16 23:59:59 2019 -02 isdst=1 gmtoff=-7200 Brazil/East Sun Feb 17 02:00:00 2019 UTC = Sat Feb 16 23:00:00 2019 -03 isdst=0 gmtoff=-10800 Brazil/East Sun Nov 3 02:59:59 2019 UTC = Sat Nov 2 23:59:59 2019 -03 isdst=0 gmtoff=-10800 <<<<< This line points to old data Brazil/East Sun Nov 3 03:00:00 2019 UTC = Sun Nov 3 01:00:00 2019 -02 isdst=1 gmtoff=-7200 <<<<< This line points to old data indicating start of DST with clock moved ahead by 1 week. Unity/VNX Block only platforms are NOT impacted by the Time Zone issue. Data Movers are also not affected as it will utilize external NTP Servers for Time Synchronization. |
Cause
Brazil's DST was abolished by brazilian government.
For more info, please check the following links:
For more info, please check the following links:
Resolution
Upgrading to latest changes
1. Download the latest patch rpm, attached, that is provided on the control station. In this case it is:
tzdata-2019c-1.el5.noarch.rpm .
2. Login as root on control station and upgrade as follows: rpm Uvh tzdata-2019c-1.el5.noarch.rpm :
[root@CS0 ~]# rpm -Uvh tzdata-2019c-1.el5.noarch.rpm
Preparing... ########################################### [100%]
1:tzdata ########################################### [100%]
Timezone package 2019c successfully installed, Now updating Java JRE TimeZone...
Using file:///usr/share/zoneinfo/tzdata2019c.tar.gz as source for tzdata bundle.
Java JRE TimeZone update is completed. Java TimeZone can be verified via : "java
-classpath /usr/share/zoneinfo checkJavaDst
3. Verify that the new changes have taken effect:
[root@CS0 ~]# /usr/sbin/zdump -v Brazil/East | grep 2019
/usr/sbin/zdump: warning: zone "Brazil/East" abbreviation "-03" lacks alphabetic at start
Brazil/East Sun Feb 17 01:59:59 2019 UTC = Sat Feb 16 23:59:59 2019 -02 isdst=1 gmtoff=-7200
Brazil/East Sun Feb 17 02:00:00 2019 UTC = Sat Feb 16 23:00:00 2019 -03 isdst=0 gmtoff=-10800
A small java tool is packaged with the rpm, by which it can be verified if a given date lies in the DST cycle:
[root@CS0 ~]# java -classpath /usr/share/zoneinfo checkJavaDst Brazil/East
Valid TZ Brazil/East
Enter a date to determine if it is considered in day light saving (Example: 2018-11-01 should not be DST for Brazil in 2018)
Enter Year (Example: 2018) : 2019
Enter Month (Example: 10 for Oct) : 11
Enter Day (Example: 18) : 2
Given date : Sat, 2 Nov 2019 Eastern Daylight Time is in DST? = false <<<< Correct, as there would be no DST in 2019
4. Reboot the control station: /sbin/shutdown r now
5. Carry out the same steps if there is a secondary control station present.
1. Download the latest patch rpm, attached, that is provided on the control station. In this case it is:
tzdata-2019c-1.el5.noarch.rpm .
2. Login as root on control station and upgrade as follows: rpm Uvh tzdata-2019c-1.el5.noarch.rpm :
[root@CS0 ~]# rpm -Uvh tzdata-2019c-1.el5.noarch.rpm
Preparing... ########################################### [100%]
1:tzdata ########################################### [100%]
Timezone package 2019c successfully installed, Now updating Java JRE TimeZone...
Using file:///usr/share/zoneinfo/tzdata2019c.tar.gz as source for tzdata bundle.
Java JRE TimeZone update is completed. Java TimeZone can be verified via : "java
-classpath /usr/share/zoneinfo checkJavaDst
3. Verify that the new changes have taken effect:
[root@CS0 ~]# /usr/sbin/zdump -v Brazil/East | grep 2019
/usr/sbin/zdump: warning: zone "Brazil/East" abbreviation "-03" lacks alphabetic at start
Brazil/East Sun Feb 17 01:59:59 2019 UTC = Sat Feb 16 23:59:59 2019 -02 isdst=1 gmtoff=-7200
Brazil/East Sun Feb 17 02:00:00 2019 UTC = Sat Feb 16 23:00:00 2019 -03 isdst=0 gmtoff=-10800
A small java tool is packaged with the rpm, by which it can be verified if a given date lies in the DST cycle:
[root@CS0 ~]# java -classpath /usr/share/zoneinfo checkJavaDst Brazil/East
Valid TZ Brazil/East
Enter a date to determine if it is considered in day light saving (Example: 2018-11-01 should not be DST for Brazil in 2018)
Enter Year (Example: 2018) : 2019
Enter Month (Example: 10 for Oct) : 11
Enter Day (Example: 18) : 2
Given date : Sat, 2 Nov 2019 Eastern Daylight Time is in DST? = false <<<< Correct, as there would be no DST in 2019
4. Reboot the control station: /sbin/shutdown r now
5. Carry out the same steps if there is a secondary control station present.
Additional Information
About this statement "Data Movers are also not affected as it will utilize external NTP Servers for Time Synchronization.".
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. Therefore, since AD/LDAP server and Data Movers (clients in general) are using the same NTP source, Kerberos authentication should work normally.
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. Therefore, since AD/LDAP server and Data Movers (clients in general) are using the same NTP source, Kerberos authentication should work normally.
Affected Products
VNX/VNXeProducts
Dell EMC Unity Family, VNX1 Series, VNX2 Series, VNX/VNXeArticle Properties
Article Number: 000055669
Article Type: Solution
Last Modified: 06 Nov 2025
Version: 3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.