Juniper Netscreen (Screen-OS based products)
Solution: In order for the device to observe the correct DST schedule for 2007 it should be upgraded to one of the following releases before March 11th, 2007:
|Release/Branch||Version||Expected release date|
|5.0-ISG-IDP||5.0.0-IDP1.r10e or later||December 2006|
|5.0-M2A||5.0.0-M2A.r9d or later||November 2006|
|5.1||5.1.0r4g or later||December 2006|
|5.2||5.2.0r3d or later||November 2006|
|5.3||5.3.0r6 or later||November 2006|
|5.4||5.4.0r3 or later||January 2007|
Solution: The fix for the 2007 DST issue is included in IVE OS 5.3R7 and above.
If you are using the Secure Meeting feature, upgrade to the following software releases which contain the fix for the DST: 5.2R7, 5.3R10 and 5.4R2.1. These are available in the IVE OS Software download page. In order for the IVE to observe the correct DST schedule for 2007, the recommendation is to upgrade to a supported build that reflects the new DST before March 11th, 2007.
Network Appliance (NetApp) Filers
1.0 Updating timezone information on filers
Affected Data ONTAP versions1.2 Downloading and installing timezone files1.3 Initializing the new timezone settings2.0 Updating timezone information on NetCache appliances2.1 Affected NetCache software versions2.2 Downloading and installing timezone files2.3 Initializing the new timezone settings
1.0 Updating timezone information on filersIMPORTANT: You must complete the steps in sections 1.2 AND 1.3 to update the zoneinfo files on your filer.
Affected Data ONTAP versionsThe following software releases contain the most recent zoneinfo files. You do NOT need to update zoneinfo files, if your appliance is running one of the following software releases:Data ONTAP 7.0.5 (GD) - Fixed
Data ONTAP 184.108.40.206 (GA) - Fixed
Data ONTAP 7.2.1 (GA) - Fixed
For a full list of releases in which this issue is already fixed, see Bug 195805.1.2 Downloading and installing timezone filesComplete the steps in ONE of the following three methods, based on your site requirements:
2. Method 2 is for customers who would prefer to download the file to a local HTTP server, and then operate the "software install" command without sending an unencrypted username and password through the "software install" command as required in Method 1.3. Method 3 is for customers who do not have a local HTTP server and whose filers do not have access to the NOW site.Method 1: Downloading and installing the timezone file using the “software install” command
- Filers that have unrestricted access to the NOW Web site can use Method 1.
filer> software install http://nowusername:firstname.lastname@example.org/download/tools/ontap_timezone/zoneinfo_current/allzones.zipNote:
You must enter your username and password because NOW requires user authentication; replace nowusername and nowpassword with a valid NOW username and password.2. Proceed to Section 1.3, "Initializing the new timezone settings".IMPORTANT: You do NOT need to reboot after running the software install command.Method 2: Downloading to a local HTTP server and installing using the “software install” command
- Enter the following command as a single line:
2. Save the allzones.zip file to any intermediate location by clicking on the URL shown and choosing “Save as…” or “Save to disk”:http://now.netapp.com/NOW/download/tools/ontap_timezone/zoneinfo_current/allzones.zip3. Copy the ZIP file to a local HTTP server.4. At the filer command line, enter the following command:filer >software install http://local_server/allzones.zip5. Proceed to Section 1.3, "Initializing the new timezone settings".IMPORTANT: You do NOT need to reboot after running the software install command.Method 3: Downloading the file to a Windows/UNIX admin host and extracting it onto the filerFrom a UNIX admin host with an NFS share of the root volumeComplete the following steps to extract the allzones.tar file from a UNIX admin host to the filer's /etc directory:
- Log in to the NOW site.
2. Save the allzones.tar file to your local system (shown as </PATHTOZONEFILE> below by clicking on the URL shown and choosing “Save as…” or “Save to disk”:http://now.netapp.com/NOW/download/tools/ontap_timezone/zoneinfo_current/allzones.tar3. Enter the following command:unix> mount <filername:/vol/ROOTVOLUME> /MOUNTPOINTNote:
An “RPC error” at this stage means that the filer does not have its root volume exported. If you get an RPC error, log in as root on the filer and issue the following command:exportfs –i –o /Retry the mount command.4. Enter the following command:unix> cd </MOUNTPOINT/>etc5. Enter the following command:unix> tar xvf </PATHTOZONEFILE>/allzones.tar6. Enter the following command:unix> cd /7. Enter the following command:unix> umount </MOUNTPOINT>8. Proceed to Section 1.3, "Initializing the new timezone settings".From a Windows admin host with a CIFS share of the root volumeComplete the following steps to extract the allzones.zip file into your filer's ETC$ directory:
- Log in to the NOW site.
2. Save the allzones.zip file to your local system by clicking on the URL shown and choosing “Save as…” or “Save to disk”:http://now.netapp.com/NOW/download/tools/ontap_timezone/zoneinfo_current/allzones.zip3. Map the filer's ETC$ share to a network drive, such as T: on the admin host.Note:
T: is used for example purposes only. Use whatever drive letter you have available.4. Use unzip to extract the allzones.zip file into the T: directory.5. Proceed to Section 1.3, Initializing the new timezone settings.1.3 Initializing the new timezone settingsIMPORTANT: You must complete these steps to successfully update your timezone info.To load the new timezone settings, execute the following commands:
- Log in to the NOW site.
filer> timezoneCurrent time zone is Location/YourTimezone <--- The text in italics will be the entered in the next step.2. Enter the following command:
filer> timezone Location/YourTimezoneNote:
The filer does not have to be rebooted to set the timezone rules.CautionDo not test this patch on production filers by changing the time forward and back. Manipulating filer time to verify the US DST change triggers Bug 234237. Once you roll the filer back to the current time, scheduled Snapshots will fail. The only way to restore scheduled Snapshot functionality is to reboot the filer.NetApp engineering has verified that the procedures documented in this article will successfully apply DST settings for 2007.
- Enter the following command:
- Solaris 8 with timezone patch 109809-06 or later and libc patch 108993-52 or later
- Solaris 9 with timezone patch 113225-08 or later and libc patch 112874-33 or later
- Solaris 10 with timezone patch 122032-04 or later and libc patch 119689-07 or later
- Solaris 8 with timezone patch 109810-06 or later and libc patch 108994-52 or later
- Solaris 9 with timezone patch 116545-06 or later and libc patch 114432-23 or later
- Solaris 10 with timezone patch 122033-04 or later and libc patch 121208-03 or later
(Note that for Solaris 8 I had trouble with the libc patch because it wanted to patch things that were not installed on the system.)