Guest

Cisco Unity Express

Field Notice: FN - 62682 - U.S. Daylight Saving Time (DST) Policy Changes Effective March 2007 - for All Cisco Unity Express (CUE) Releases Prior to 2.3.4


February 19, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Products Affected

CUE - Prior to release 2.3.4

Problem Description

New U.S. Daylight Saving Time rules go into effect in March 2007.

If Cisco Unity Express is not upgraded to CUE 2.3.4 with the new U.S. DST policy changes, timestamps will exhibit a one hour time clock offset lasting three weeks beginning at 2 A.M. on the second Sunday in March of 2007. They will also exhibit a one hour time clock offset lasting one week beginning at 2 A.M. on the first Sunday in November.

Background

On August 8, 2005, the Energy Policy Act of 2005 (H.R.6.ENR), was signed into law. Section 110 of this Act modified the time change dates for Daylight Saving Time (DST) in the U.S.

Beginning in March of 2007, DST will begin on the second Sunday of March and end the first Sunday of November.

For 2007 and beyond, the daylight saving time period will be:

2:00 A.M. on the second Sunday in March

to

2:00 A.M. on the first Sunday in November

For more information on the Energy Policy Act of 2005 please see H.R. 6. (See Section 110)

Problem Symptoms

Impact to Networking Systems

Networking systems often make use of local time to mark logs, as well as to schedule certain events, such as IP SLA schedule starts, or the beginning or end of a time-based access-list.

In addition, inconsistencies between time zone definitions may impact event correlation systems as well as other management systems relating to problem escalation. Having accurately represented local time is a very big concern for most organizations. Local time may be reflected in logs and on phone displays. This is especially true of systems that require accurate time and time stamping for proper operations.

For networking systems, the clock or clock source is often derived from a trusted chronological source such as a private or public Atomic clock, often through Network Time Protocol (NTP). NTP communicates time in Coordinated Universal Time (UTC), colloquially known as GMT, and thus is not impacted, nor is a workaround for statutory time zone changes. Local time definitions, including summertime settings are part of the configuration of most Cisco products.

Workaround/Solution

Solution:

Cisco Unity Express sets daylight savings time automatically on the basis of the time zone, which is selected during the installation procedure or with the Administration > Network Time and Time Zone Settings GUI screen. CUE release 2.3.4 will include the fix for the required US DST changes (CSCsh30313). The estimated date for posting 2.3.4 to CCO is around February 15, 2007.

Customers are encouraged to update CUE to 2.3.4 by downloading the software from here http://www.cisco.com/cgi-bin/tablebuild.pl?topic=278535672 as soon as it becomes available.

Workaround:

CUE may also be manually updated as follows:

On March 11, 2007 change to a time zone that is one hour ahead by using the clock time zone cli and then save, reload to make changes take effect. For example if we are in the Pacific time zone you need to move the time zone one hour ahead i.e., change to MT from CLI or GUI.

Changing time zone from CLI:

 
se-10-50-40-125(config)> clock timezone ? 

name time zone 
se-10-50-40-125(config)> clock timezone 
Please identify a location so that time zone rules can be set correctly. 
Please select a continent or ocean. 
1) Africa 4) Arctic Ocean 7) Australia 10) Pacific 
Ocean 
2) Americas 5) Asia 8) Europe 
3) Antarctica 6) Atlantic Ocean 9) Indian Ocean

The wizard walks you through making time-zone changes. Follow the wizard, save configs and then reload the module for changes to take effect.

Configuring time zone from the GUI:

This can be done by going to Administration > Network Time & Time Zone Settings . Please note that you need to reload after making these changes.

For example, if your are in Pacific time zone then you need to move the time zone to MT on March 11.

On April 1 you have to set the time zone back to PT by using the same CLI .

On October 28, 2007 you have to move ahead by changing the time zone to MT.

On November 4, 2007 change back to your original time zone which is PT.

The above dates are for 2007. These dates will change each year to be the second Sunday of March and the first Sunday of November. The same process would need to be followed each succeeding year on the appropriate dates.

DDTS

To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.

DDTS

Description

CSCsh30313 (registered customers only)

Update DST for US on Service Engines such as AIM-CUE NM-CUE NM-NAM NM-CE

Revision History

Revision

Date

Comment

1.0

19-FEB-2007

Initial Public Release

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.