Guest

Cisco Unified MeetingPlace Express

Field Notice: FN - 62661 - US Daylight Savings Time Policy Change Effective March 2007 - for MeetingPlace Express (MPE)


Revised February 06, 2007

January 30, 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

Comments

MPE - 1.2 MPE

Versions 1.2 and earlier are affected.

Problem Description

New U.S. Daylight Savings Time rules go into effect in March 2007. Consequently, certain instances of recurring meetings on MeetingPlace Express may occur and appear one hour off than their intended scheduled time. Timestamps for MPE system logs will also be off by an hour.

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 and beyond, DST will begin on the second Sunday of March at 2:00 AM and end the first Sunday of November at 2:00 AM.

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

The old DST policy dictated the start of DST was the first Sunday of April and ended on the last Sunday of October.

Problem Symptoms

Recurring meetings with some, but not all, instances occurring during the below timeframes may have start times that are off by one hour from the original, intended start time:

-March 11 to April 1 in 2007

-October 28 to November 4 in 2007

System logs may also show up as one-hour off during the above time frames.

Workaround/Solution

There are two possible solutions for fixing this problem:

  1. Wait for and upgrade to the next software release. Problematic meetings scheduled prior to the upgrade will still need to be manually re-scheduled. Until the next software version is released, meeting owners will need to manually fix the problem by rescheduling the meetings which are scheduled for the transition time period. You can find detailed instructions on how to do that in the DSTManualFix.doc document, which is included in the US_Daylight_Savings_Time_Fix.zip file posted on the following URL:

    http://www.cisco.com/cgi-bin/tablebuild.pl/meetingplace-exp1.1 (registered customers only)

  2. Run the script fix_timezone_data.sh. All meetings scheduled after running the script will have the correct start time. The script will also provide a list of meetings which have to be manually rescheduled. You will still have to manually reschedule all meetings that were scheduled for the problematic time periods before the script was applied. The provided list may contain duplicate incidents without specifying the date of occurrence, this is expected behavior. You can find detailed instructions on how to manually reschedule meetings in the DSTManualFix.doc document, which is included in the US_Daylight_Savings_Time_Fix.zip file posted on the following URL:

    http://www.cisco.com/cgi-bin/tablebuild.pl/meetingplace-exp1.1 (registered customers only)

How to run the scripts:

Both of the below scripts are included in US_Daylight_Savings_Time_Fix.zip file posted on the following URL:

http://www.cisco.com/cgi-bin/tablebuild.pl/meetingplace-exp1.1 (registered customers only)

* fix_timezone_data.sh - Updates the timezone data, which fixes the problem for any newly scheduled meetings after the timezone data is updated. Also, this script displays a list of meetings which need to be manually rescheduled.

Script: fix_timezone_data.sh 
Usage: ./fix_timezone_data.sh 

Permission: The script should be run as root. That is, su to root and copy both scripts to a folder and then make them executable:

chmod +x fix_timezone_data.sh

chmod +x list_meetings.sh

The script updates the timezone and localtime data which fixes the problem for any newly scheduled meetings after the timezone data is updated. It will also display a list of meetings which still need to be manually rescheduled. This script can be safely run any number of times whether it is needed or not.

* list_meetings.sh - Displays a list of meetings which need to be manually rescheduled. The provided list may contain duplicate incidents without specifying the date of occurrence, this is expected behavior. Make sure to run fix_timezone_data.sh prior to manually rescheduling problematic meetings. This will insure meetings are scheduled for their proper start time.

Script: list_meetings.sh
Usage: ./list_meetings.sh

Permission: The script should be run as root. That is, su to root and copy the script to a folder and then make it executable - chmod +x list_meetings.sh .

The script displays a list of meetings which may need to be manually rescheduled.

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

CSCsh14773 (registered customers only)

Timezone file for new DST policy is copied to system, but not applied.

Revision History

Revision

Date

Comment

1.1

06-FEB-2007

Changes made to workaround section

1.0

30-JAN-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.