IP Application Services

Document ID: 81675

Version 3.9

Last Updated 2008 March 07 2200 UTC (GMT)

For Public Release 2007 January 23 1800 UTC (GMT)

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Scope and Impact
Affected Cisco Platforms
      Application Networking Services
      Interfaces and Modules
      Cisco IOS Software
      Network Management
      Optical Networking
      Routers and Switches
      Security and VPN
      Storage Networking
      Tools and Resources
      Video, Cable, and Content Delivery
      Voice and Unified Communications
      Wireless
Configurations and Workarounds
      Adaptive Security Appliances (ASA) and PIX Platforms
      CatOS Platforms
      CiscoWorks
      Content Services Switch (CSS)
      Intrusion Detection and Prevention
      Cisco IOS Software Platforms
      Cisco IOS XR
      Network Time Protocol Implications
      ONS 15000 Series Products
      Storage Switches (SAN-OS) - Storage MDS 9500 Series
      VPN 3000 Concentrators (Altiga OS)
Background Information
Related Information

Introduction

Cisco is proactive in its approach to comply with the new daylight saving time (DST) changes and wants to ensure that Cisco products in our customer's networks continue to operate without impact through the DST date transition. As such, Cisco has undertaken a company-wide initiative to supply documentation that describes how to update each product.

The purpose of this document is to describe the methods that can be used to address the change in daylight saving time, initiated on August 8, 2005, when President George W. Bush signed the Energy Policy Act of 2005. This document helps guide you through the Cisco product lines that require intervention in order to prepare them for the US-DST date changes.

Additional product information will be provided as soon as it is available. Check back frequently for updates.

This Energy Policy Act changes the dates for daylight saving time in the United States. In 2007, DST begins on the second Sunday in March and ends the first Sunday in November. The Secretary of Energy will report the impact of this change to Congress. Congress retains the right to resume the 2005 daylight saving time schedule once the Department of Energy study is complete. This law takes effect March 1, 2007.

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.

[Return to Top]

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Scope and Impact

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 Energy Policy Act.

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 three weeks earlier and ends one week later than in past years. This change takes effect for the first time in March 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 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 effect call detail reporting and billing information or inaccurate campaign dialing times that result in dialing customers outside FTC allotted time periods, which is a violation of FTC 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, etc.) that has been configured to use U.S. DST rules would be impacted during the time period when the new U.S. DST rules go into effect, but the old U.S. DST rules are still applied.

[Return to Top]

Affected Cisco Platforms

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 2006 dates, which are invalid for 2007.

Refer to these categories for more information about your product:

• Application Networking Services

• Interfaces and Modules

• Cisco IOS Software

• Network Management

• Optical Networking

• Routers and Switches

• Security and VPN

• Storage Networking

• Tools and Resources

• Video, Cable, and Content Delivery

• Voice and Unified Communications

• Wireless

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: This page will be updated as more products are addressed.

[Return to Top]

Application Networking Services

[Return to Top]

Interfaces and Modules

[Return to Top]

Cisco IOS Software

[Return to Top]

Network Management

[Return to Top]

Optical Networking

[Return to Top]

Routers and Switches

[Return to Top]

Security and VPN

[Return to Top]

Storage Networking

[Return to Top]

Tools and Resources

[Return to Top]

Video, Cable, and Content Delivery

[Return to Top]

Voice and Unified Communications

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:

1. Go to http://www.cisco.com/univercd/cc/td/doc/product/voice/ip_tele/gblink/ipcmtrix.htm.

2. 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.)

3. 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:

1. Go to http:///www.cisco.com/go/unified-techinfo.

2. 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.)

3. 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.

[Return to Top]

Wireless

Refer to FN - 62646 - US Daylight Savings Time Policy Change Effective March 2007 - for Wireless Products for more information about all wireless products.

[Return to Top]

Configurations and Workarounds

This section contains workarounds or manual configurations for the more common Cisco platforms that support daylight saving time.

Note: If you apply workarounds, these workarounds might be temporary and might require additional actions before the next DST start or end date transition. Depending on the Cisco device or application, these settings might not be persistently saved. For example, if the Cisco device or application is reset, the DST settings might revert back to the original settings.

[Return to Top]

Adaptive Security Appliances (ASA) and PIX Platforms

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.

[Return to Top]

CatOS Platforms

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 

[Return to Top]

CiscoWorks

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.

[Return to Top]

Content Services Switch (CSS)

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.

[Return to Top]

Intrusion Detection and Prevention

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.

[Return to Top]

Cisco IOS Software Platforms

You can change the DST configuration parameters for a system that runs Cisco IOS 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 Cisco IOS:

clock summer-time EDT recurring 2 Sun Mar 2:00 1 Sun Nov 2:00

[Return to Top]

Cisco IOS XR

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 

[Return to Top]

Network Time Protocol Implications

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.

[Return to Top]

ONS 15000 Series Products

Cisco has made changes to the ONS 15600, 15454, 15327, and 15310 products CTC and TL1 software so that the new DST implementation correctly changes with the second Sunday of March and the first Sunday of November in 2007.

Any systems that have not updated the system software will automatically follow the rules set for the previous Daylight Savings Time. In other words, the system automatically modifies the clock and reflects the incorrect time because, on March 11 2007, the system will not automatically presume that the DST has taken effect.

In order to comply with the 2007 DST time change, these options are available:

• Obtain a new version of your software.

  Cisco has implemented (or is implementing) the new DST changes into this software:

  • Release 4.1.82

  • Release 5.0.8

  • Release 7.0.2 or higher

  • Release 7.2.2 or higher

  • Release 8.0.x or higher

  Other versions of this software will continue to operate with the previous DST rules.

• Use CTC in order to manually change the time.

  If customers do not want to upgrade to any of the above software releases. CTC provides you with the ability to enable or disable DST and also to change the time on your nodes. Customers must assume manual control over the system time and force the system clock to reflect the correct time.

  From the 2nd Sunday of March to the 1st Sunday of April, use this solution in order to solve the problem:

  • Disable manually Daylight Savings Time on the 2nd Sunday of March (March 11 for 2007).

  • Reset the system clock to reflect the correct time.

  • Enable Daylight Savings Time once again on the 1st Sunday of April 2007 (April 1 for 2007) and ensure that the time is correct.

  From the last Sunday of October to the 1st Sunday of November, use this solution in order to solve the problem:

  • Manually disable Daylight Savings Time on the last Sunday of October (October 28 for 2007).

  • Reset the system clock to reflect the correct time.

  • Enable Daylight Savings Time once again on the 1st Sunday of November 2007 (November 4 for 2007) and ensure that the time is correct.

• Use the TL1 CLI in order to manually change the time.

  You can change the time-of-day parameters for a system that runs the Optical Operating System (ONS) with a single configuration command. Here is the format of the command:

  SET-TOD:[<TID>]::<CTAG>::<YEAR>,<MONTH>,<DAY>,
       <HOUR>,<MINUTE>,<SECOND>,[<DIFF>][:DST=<DST>];
  

  This command changes the time on an optical product that runs ONS. However, the daylight saving start and stop time will not change, and the product uses the defaults coded into the operational code.

If you do not fall into one of these listed categories, you should direct your inquires to your respective Account Manager.

Note: For more information on time zone configurations and how to reset the time, refer to the relevant procedure guide for the Cisco ONS release that you use. For example, if you use Cisco ONS 15454, refer to Cisco ONS 15454 Procedure Guide, Release 7.0.

[Return to Top]

Storage Switches (SAN-OS) - Storage MDS 9500 Series

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.

[Return to Top]

VPN 3000 Concentrators (Altiga OS)

The DST Configuration parameters f