On 30 April 2007, the Honorable Rick Barker, Minister of Internal Affairs, announced a three week extension to the period of daylight saving. Daylight saving time (DST) now runs from the last Sunday in September until the first Sunday in April.
Summary of Changes to Daylight Saving Time | ||
---|---|---|
Prior to 2007 | Year 2007 and After | |
Start | First Sunday in October | 2am on 30 September 2007 (Last Sunday in September) |
End | Third Sunday in March | 3am on 6 April 2008 (First Sunday in April) |
For more information regarding Daylight Savings Time in New Zealand, visit Department of Internal Affairs website:
The configuration changes provided in this document are required to change the “programmed in” dates of daylight saving time for various time zones. Some devices that run newer software may not require this change if the enhancement request is included in the version of software that runs on the device. In software that includes this enhancement, the OLD summertime values have been changed to the NEW summertime values, and the configuration changes in this document are not required. For detailed information about individual products, see Affected Cisco Platforms.
Configuration or OS changes will need to occur on the devices that implement the old rules, so that the device time can be correct, in logs and other time stamped communications from the device/platform.
There are no specific requirements for this document.
This document is not restricted to specific software and hardware versions.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
The DST change affects all devices that support an automatic time change when they are configured to support daylight saving time. This change impacts Cisco and non-Cisco devices. Customers should contact any vendor that uses time-sensitive messaging or other time-stamped communications in order to determine the impact of the change to beginning and end of Daylight Savings Time.
Affected devices that are not changed could display the time exactly 1 hour off from the actual time during DST periods in spring and fall. In 2007, DST starts one week earlier and ends one week later than in past years. This change takes effect for the first time in September of 2007. This change can have a major impact on event correlation activities that are performed as part of normal operations troubleshooting and monitoring.
For security-related devices, where logs are captured, correlated, and stored for future reference, this time change could render them incorrect for situations where they need to be recalled to rebuild a sequence of events. The incorrect timestamps might not be an issue for events that get immediate action. However, in the future, these events would reference incorrect times.
Any device with time-based controls and activities, such as a AAA (Authentication Authorization Accounting) servers, Content Devices (CEs), cron jobs, and video streaming servers can be impacted and should be checked with the appropriate vendor.
Other examples include calls being logged at the wrong times that could affect call detail reporting and billing information or inaccurate campaign dialing times that result in dialing customers outside allotted time periods defined by government agencies, which may be a violation of government regulations.
Consequently, any device with time-based controls and activities, such as authentication servers, synchronization activities, and scheduled events (that is, batch jobs, timed backups, or automated dialing capabilities or scripts for Telemarketing purposes, etc.) that has been configured to use New Zealand DST rules would be impacted during the time period when the new New Zealand DST rules go into effect, but the old New Zealand DST rules are still applied.
The tables in this section list the Cisco enhancement IDs that were created in order to track the changes in the operating system defaults for various platforms. Versions of software that include these enhancements will correctly change the time when configured to observe daylight saving time. Software versions that do not include these enhancements, but support daylight saving time, will use the previous dates, which are invalid after September 30, 2007.
Refer to these categories for more information about your product:
In order to view each enhancement and the version in which it is integrated, click the appropriate Cisco Tracking ID or use the Bug Tool (registered customers only) . You must register with Cisco.com in order to view this information. For a full list of product Field Notices, refer to the Product Field Notice Summary page.
Note: The tables in this section reference Field Notices that have not been released. Once a notice is released, the appropriate reference will be updated with a link to that document.
Cisco Product | Cisco Tracking ID | Notes |
---|---|---|
Application and Content Networking System (ACNS) | CSCsk20769 | For more information, refer to Field Notice: FN - 62896 - New Zealand Daylight Saving Time Policy Changes Effective September 2007 - For Cisco WAAS, WAFS, ACNS. |
Application Control Engine (ACE) | N/A | clock timezone standard <timezone> introduced in A.1.4 and beyond. |
Content Services Switches (CSS) Appliance | N/A | clock summer-time command introduced in version 8.10 / 7.10 and beyond. |
Content Switching Module (CSM) | N/A | From the SUP blade - clock calendar-valid. |
Global Site Selector (GSS) Appliance | N/A | clock user summer-time command introduced in version 1.3.2. |
Wide Area Application Services (WAAS) | CSCsj93996 | For more information, refer to Field Notice: FN - 62896 - New Zealand Daylight Saving Time Policy Changes Effective September 2007 - For Cisco WAAS, WAFS, ACNS. |
Wide Area File Services (WAFS) | N/A | For more information, refer to Field Notice: FN - 62896 - New Zealand Daylight Saving Time Policy Changes Effective September 2007 - For Cisco WAAS, WAFS, ACNS. |
Cisco Product | Cisco Tracking ID | Notes |
---|---|---|
Application Performance Assurance Network Module (NME-APA) Cisco Unity Express Network Module (NM-CUE) Content Engine Network Module (NM-CE) Network Analysis Module (NM-NAM) | CSCsj75969 | For more information, refer to these field notices: |
Cisco Product | Cisco Tracking ID | Notes |
---|---|---|
Cisco IOS® Solutions:
|
N/A | VPN 3K hardware should be manually changed through the GUI. Choose Configuration > System > General, and make changes in the Time and Date dialog box. VPN client applications should be changed through the Windows settings. VPN SPA should be changed with the clock command on Cisco IOS. See Cisco IOS Software Platforms in the Configurations and Workarounds section of this document for more information. |
Cisco IOS Software Platforms | N/A | See Cisco IOS Software Platforms in the Configurations and Workarounds section of this document for information about this product. |
Cisco IOS XR | N/A | See Cisco IOS XR in the Configurations and Workarounds section of this document for information about this product. |
Cisco Product | Cisco Tracking ID | Notes |
---|---|---|
ONG Optical Products | N/A | New Zealand DST Patches not required for Optical Products. |
Cisco Product | Cisco Tracking ID | Notes |
---|---|---|
Adaptive Security Appliances (ASA) Platforms | N/A | Use the clock summer-time command in order to set the Daylight Savings start and end times. |
Adaptive Security Appliances (ASA) WebVPN | N/A | Use the clock summer-time command in order to set the Daylight Savings start and end times. |
Adaptive Security Appliances (ASA) IPSec | N/A | Use the clock summer-time command in order to set the Daylight Savings start and end times. |
Adaptive Security Device Manager (ASDM) | N/A | Use the clock summer-time command in order to set the Daylight Savings start and end times. |
Cisco Trust Agent (CTA) | N/A | Fixed in version 2.4.1. |
CiscoWorks Security Information Management Solution (SIMS) | CSCsk12300 | For more information, refer to Field Notice: FN - 62890 - New Zealand Daylight Saving Time Policy Changes Effective September 2007 - for CiscoWorks Security Information Management Solution (CW-SIMS). |
DDOS Guard and Detector Appliance | N/A | Users should upgrade the system to firmware version 6.0(5) to incorporate the new DST configuration settings. For more information, refer to Field Notice: FN - 62741 - U.S. Daylight Savings Time (DST) Changes - All DDOS Guard and Detector Appliance Versions - Configuration Change or Upgrade Required. |
Intrusion Prevention System (IPS) | N/A | service host > summertime-option recurring |
NAC Appliance (Cisco Clean Access) | N/A | Fixed in these versions: 3.005(011.001), 3.6(4.3), 4.0(3.3), 4.0(4), and 4.1(0). |
PIX Platforms | N/A | Use the clock summer-time command in order to set the Daylight Savings start and end times. |
PIX Device Manager (PDM) | N/A | Use the clock summer-time command in order to set the Daylight Savings start and end times. |
Secure ACS Appliance | N/A | For more information, refer to Field Notice: FN - 62905 - New Zealand Daylight Savings Time policy changes effective September 2007 - For ACS. |
Security Monitoring, Analysis and Response System (CS-MARS) | CSCsk11384 | Fixed in versions 4.3.2 and 5.3.2. For more information, refer to Field Notice: FN - 62891 - New Zealand Daylight Saving Time Policy Changes Effective September 2007 - for Cisco CS-MARS. |
Video Surveillance Stream Manager (ICEVSSW) | N/A | For more information, refer to Field Notice: FN - 62885 - New Zealand Daylight Savings Time policy changes effective September 2007 for ICEVSSW. |
VPN 3K Clients | N/A | VPN 3K hardware should be manually changed through the GUI. Choose Configuration > System > General, and make changes in the Time and Date dialog box. VPN client applications should be changed through the Windows settings. VPN SPA should be changed with the clock command on Cisco IOS. See Cisco IOS Software Platforms in the Configurations and Workarounds section of this document for more information. |
Cisco Product | Cisco Tracking ID | Notes |
---|---|---|
TelePresence Codec | CSCsk44933 | Refer to CSCsk44933—Need to rebuild TZ database in CTS to support DST time change for information about this product. |
TelePresence Manager | N/A | Refer to Field Notice: FN - 62918 - New Zealand Daylight Saving Time Policy Change Effective September 2007 - for Cisco TelePresence Codec, Cisco TelePresence Manager (CTM) and Cisco TelePresence Multipoint Switch (CTMS) for information about this product. |
Cisco Product | Cisco Tracking ID | Notes |
---|---|---|
Ciscoworks IP Telephony Monitor (ITM) Version 2.0 | N/A | |
Unified Operations Manager (CUOM) Versions 1.1 and 2.0 | N/A | |
Unified Service Monitor (CUSM) Versions 1.1 and 2.0 | N/A |
Cisco Product | Cisco Tracking ID | Notes |
---|---|---|
Service Control Solution (SCE) | N/A | For more information, refer to Field Notice: FN - 62641 - SCE - U.S. Daylight Savings Time Policy Changes Effective March 2007 for SCE. |
If you run a system of multiple Cisco Unified Communications products, please consult the appropriate System Upgrade Manual for recommended order in which to update products. There is a separate System Upgrade Manual for each version of Unified CallManager that a system is built around.
In order to locate information for system test releases based on Unified CallManager 4.x, System Upgrade Manuals, complete these steps:
Go to http://www.cisco.com/en/US/docs/voice_ip_comm/uc_system/GB_resources/ipcmtrix.htm.
Click the column heading appropriate to the release set that you use. (Note that the system test release version is not the same as the Unified CallManager version.)
Navigate to the link for the System Upgrade Manual.
Note: If you receive an error that states "Unable to open script," disable any anti-intrusion software or Cisco Security Agent that runs on the Cisco Callmanager before you run the DST patch.
In order to locate information for Unified Communications Systems based on Unified CallManager 5.x, System Upgrade Manuals, complete these steps:
Click the link that corresponds to the system release that you use. (The system release version is usually, but not necessarily, the same as the Unified CallManager version.)
Click the Prepare and Plan tab, and click the Planning Your System Upgrade link located in the Table of Contents on the left side of the page.
Cisco Product | Cisco Tracking ID | Notes |
---|---|---|
Access Points and Wireless Controllers | N/A | For more information, refer to Field Notice: FN - 62894 - New Zealand Daylight Saving Time Policy Change Effective September 2007 - Wireless Products. |
This section contains workarounds or manual configurations for the more common Cisco platforms that support daylight saving time.
Available Configurations | |
---|---|
Cisco Platform | Workaround Available |
Adaptive Security Appliances (ASA) and PIX Platforms | Yes |
Application and Content Networking System (ACNS) | Yes |
CatOS Platforms | Yes |
CiscoWorks | Patch |
Content Services Switch (CSS) | Yes |
Intrusion Detection and Prevention | Yes |
Cisco IOS Software Platforms | Yes |
Cisco IOS XR | Yes |
Storage Switches (SAN-OS)—Storage MDS 9500 Series | Yes |
VPN 3000 Concentrators (Altiga OS) | No—Set manually in March and November |
Although it might appear that the use of Network Time Protocol (NTP) will avert any issues related to these time changes, NTP and daylight saving time are mutually exclusive and one does not help or hinder the other. The Network Time Protocol is a utility used to synchronize clocks on different devices. Typically, NTP takes a reference clock from a source that is based on the Coordinated Universal Time (UTC), which does not change regardless of DST.
For example, the Eastern Standard Time (EST) in the United States is five hours behind the UTC time when daylight saving time is not active. EST is four hours behind when daylight saving time is active. DST configuration is very specific to the time zone in which the device is deployed, and the NTP UTC is used as a reference when DST is calculated on each individual device.
You can change the DST configuration parameters for a system that runs the Cisco PIX or ASA OS with a single configuration command. You can run this command at any time and on any device in order to change the current default settings of the given device.
clock summer-time zone recurring [{week} {day} {month} {hh:mm} {week | day | month | hh:mm} [offset]]
In order to comply with the 2007 DST time change, use this command on any device that runs the Cisco PIX or ASA OS:
clock summer-time EDT recurring 2 Sun Mar 2:00 1 Sun Nov 2:00
Note: If you do not use the summer-time option, you are not affected by this issue. To verify that you do not use the summer-time option, run this command:
Note: show run | include summer-time
If you do not receive output from this command, your device is not affected by this issue. If you receive output and your device is affected by this issue, contact the Cisco Technical Assistance Center (TAC) in order to obtain the 6.3(5.123) interim image.
You can change the DST configuration parameters for a Cisco Application and Content Networking System (ACNS) or Content Engine with a single configuration command. You can run this command at any time and on any device in order to change the current default settings of the given device.
clock summertime zone recurring [{week} {day} {month} {hh:mm} {week | day | month | hh:mm} [offset]]
In order to comply with the 2007 DST time change, use this command on any ACNS device:
clock summertime EDT recurring 2 Sun Mar 2:00 1 Sun Nov 2:00
You can change the DST configuration parameters for a system that runs Cisco CatOS release 5.4 and later with a single configuration command. You can run this command at any time and on any device in order to change the current default settings of the given device.
set summertime recurring [{week} {day} {month} {hh:mm} {week | day | month | hh:mm} [offset]]
In order to comply with the 2007 DST time change, use this command on any device that runs Cisco CatOS release 5.4 and later:
set summertime enable EDT set summertime recurring second Sunday March 02:00 first Sunday November 02:00 60
Management applications, such as CiscoWorks and Cisco Secure ACS, use the time provided by the operating system. Therefore, in order to resolve the DST issue, you must install the operating system patch that contains the fix for your operating system (Windows, Solaris, etc.).
If the platform includes an operating system that is maintained by Cisco, such as Unified CallManager or the ACS appliance, Cisco will provide a patch. See the affected products list in the Network Management section in order to determine when a patch will be available for your product.
You can change the DST configuration parameters for a Content Services Switch (CSS) that runs WebNS with a single configuration command. You can run this command at any time in SuperUser mode on a CSS in order to change the current default settings of the given device.
clock summer-time zone recurring [{week} {day} {month} {hh:mm} {week | day | month | hh:mm} [offset]]
In order to comply with the 2007 DST time change, use this command on a CSS that runs WebNS:
clock summer-time EDT recurring 2 Sun Mar 2:00 1 Sun Nov 2:00
Note: The CSS clock summer-time command first appeared in version 7.50.
In order to change the summertime settings on Cisco Intrusion Detection and Prevention devices, use the setup option from the CLI:
Modify summer time settings? [no]:yes Recurring, Date or Disable[recurring]: Start Month[mar]: Start Week[2]: Start Day[sun]: Start Time[02:00:00]: End Month[nov]: End Week[1]: End Day[sun]: End Time[02:00:00]: DST Zone[]: EDT Offset[60]:
Note: GUI-based management packages might include a time-based setup screen that you can use to make the necessary changes.
Note: [Return to Top]
The Cisco IOS DST configuration parameters can be changed with a single configuration command. You may run this command at any time and on any device in order to change the current default settings of the device.
clock summer-time zone recurring [{week} {day} {month} {hh:mm} {week | day | month | hh:mm} [offset]]
For detailed information about the clock summer-time command, refer to the Cisco IOS Network Management Command Reference.
In order to comply with the 2007 NZ DST time change, use the clock summer-time command on any device that runs Cisco IOS. This example is for the NZST/NZDT time zone:
clock summer-time NZDT recurring last Sun Sep 2:00 1 Sun Apr 3:00
You can change the DST configuration parameters for a system that runs Cisco IOS XR with a single configuration command. You can run this command at any time and on any device in order to change the current default settings of the given device.
clock summer-time zone recurring [{week} {day} {month} {hh:mm} {week | day | month | hh:mm} [offset]]
In order to comply with the 2007 DST time change, use this command on any Cisco IOS XR device:
clock summer-time EDT recurring 2 Sun Mar 2:00 1 Sun Nov 2:00
By default, the MDS SAN-OS does not adjust for daylight saving time, and the software provides no default values for DST settings. Therefore, any configuration for daylight saving must include the parameters for the start and end dates.
clock summer-time zone start_week start_day start_month start_time end_week end_day end_month end_time daylight_offset
In order to comply with the 2007 DST time change, use this command:
clock summer-time Eastern 2 Sun Mar 2:00 1 Sun Nov 2:00
Note: The time zone “Eastern” is a user-defined value and can be determined with this command: show running | clock.
Since the MDS SAN-OS offers no default values for the setting of summertime, no code changes are required. The DST setting for SAN-OS must be configured through the CLI for these reasons:
The Fabric Manager cannot be used to configure multiple switches with this setting as it does not support DST configuration.
Cisco Fabric Services does not support daylight saving time configuration as a single fabric can span multiple time zones.
The DST Configuration parameters for a system that runs Altiga OS cannot be changed. Currently, in both the 4.1 and 4.7 releases of Altiga OS, you can enable the summertime feature in order to use daylight saving time default settings, as previously set. In order to work around this issue, you must set the time ahead one hour when the new daylight saving time occurs on the 2nd Sunday in March. DST should be disabled on these devices so the device does not attempt to set ahead its clock on the 1st Sunday in April.
Note: The information provided in this section is a workaround for those who choose not to upgrade to the fixed code once it is available.
You can disable daylight saving time and set the clock forward as shown in this image:
The information in this section was copied from the New Zealand Department of Internal Affairs (http://www.dia.govt.nz/diawebsite.nsf/wpg_URL/Resource-material-Information-We-Provide-About-Daylight-Saving?OpenDocument ).
Daylight saving to be extended
Hon Rick Barker
Minister of Internal Affairs
30 April 2007
New Zealanders will have three weeks more daylight saving from 30 September this year following the decision by the Labour-led Government to extend the period to 27 weeks, Internal Affairs Minister Rick Barker announced today.
Clocks will go forward an hour a week earlier than usual - on the last Sunday in September- and back an hour on the first Sunday in April, instead of the third Sunday in March. This is the first change in daylight saving since 1990.
“The decision means people will have an extra hour of daylight in the evenings from late September to early April to enjoy the outdoors. This builds upon the extra half an hour already built into New Zealand’s time throughout the year,” Rick Barker said.
Document ID: 98600