Guest

Cisco Unified Communications Manager (CallManager)

Field Notice: FN - 62883 - New Zealand Daylight Savings Time Policy Changes Effective September 2007 - for Cisco Unified CallManager


Revised September 18, 2007

September 4, 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

Cisco Phones - All Cisco Phones - For 7906, 7911, 7941, 7961, 7970, 7971, please note additional workaround

For 7906, 7911, 7941, 7961, 7970, 7971, please note additional workaround

Unified Windows OS - 4.2(x)

Includes SR's 4.2(3)SR2b and below 006.000(001.2000.003)

Unified CM Windows OS - 4.1(x)

Includes SR's 4.1(3)SR5b and below

Unified CM Windows OS - 3.3(3)

Includes SR's 3.3(5)SR2a and below

Unified CM Windows OS - 4.3(X)

Includes SR's 4.3(1)SR1 and below

Unified CM Windows OS - 5.0(4)

 

Unified CM Windows OS - 5.1(1)

005.001(002.3000.002)

Unified CM Windows OS - 6.0(x)

006.000(001.2000.003)

   

Problem Description

The operating systems of most Cisco products that support Daylight Saving Time (DST) have built in mechanisms to automatically change the times, based on current user-selected rules. Once the new DST is implemented, the time on devices that maintain time zone information will continue to change according to the old method, unless changes are made.

Impact to Networking Systems

Due to inconsistencies between time zones, New Zealand Daylight Saving Time changes may impact systems events as well as other management systems relating to problem escalation. Local time may be reflected in logs and on phone displays. Therefore, not having accurately represented local time is a very big concern for most organizations. This is especially true of systems that require accurate time and time stamping for proper operations.

Background

On April 30, 2007, the Minister of Internal Affairs issued a statement regarding a change in Daylight Saving Time policy for New Zealand. The change in policy has modified the start and end dates for Daylight Saving Time (DST). Beginning in 2007 and beyond, Daylight Saving Time in New Zealand will start on the last Sunday of September at 2:00 A.M. local time and end on the first Sunday of April at 3:00 A.M. local time.

Specifically for 2007-2008, Daylight Saving Time will begin at 2:00 A.M. local time on September 30, 2007, and end at 3:00 A.M. local time on April 6, 2008.

For more information, see the statement issued by the Minister of Internal Affairs: Daylight saving to be extended.

The old Daylight Saving Time policy dictated that DST started on the first Sunday in October and ended on the third Sunday in March.

Problem Symptoms

Impact to Networking Systems

Due to inconsistencies between time zones, NZ Daylight Saving Time changes may impact systems events as well as other management systems relating to problem escalation. Local time may be reflected in logs and on phone displays. Therefore, not having accurately represented local time is a very big concern for most organizations. This is especially true of systems that require accurate time and time stamping for proper operations.

Workaround/Solution

If implementing the patches is not an option, manual workarounds may be implemented. Follow the directions shown for the two dates. Once the appropriate patches are applied, the workaround must be undone to meet compliance with the new New Zealand DST dates.

September 30, 2007 recommendation (NZ):

- If the customer applied a Timezone Change workaround on September 30, 2007, such as required for Time of Day routing, that will need to be un-done on October 7, 2007.

- If the customer applied the Manual Clock Advance workaround on September 30, 2007, then:

For Cisco Unified Communication Manager 3.x or 4.x, sometime after 4:01 A.M. on October 7, 2007 it is necessary to re-check the "Automatically adjust clock for DST" box and manually set the server clock to the current local time on each Cisco Unified Communication Manager cluster node.

For Cisco Unified Communication Manager 5.x there is no customer access to the "Automatically adjust clock for DST" setting. The clock should have advanced ahead by one hour at 2:01 A.M. on September 30, 2007. To correct this, after 4:00 A.M. on October 7, 2007, the customer will need to manually set the server clock to the current local time on each Cisco Unified Communication Manager cluster node.

- If the customer fully patched the system for the September 30, 2007 DST start, there's no action required on October 7, 2007.

- If the customer did nothing in terms of patching or working around issues for the September 30, 2007 DST start, there's no action required on October 7, 2007. The clock would have been off by one hour starting at 2:00 A.M. on September 30, 2007, but this will automatically correct at 2:00 A.M. on October 7, 2007.

March 16, 2008 recommendation (NZ):

- If the customer applied a Timezone Change workaround on March 16, 2008, such as required for Time of Day routing, that will need to be un-done on April 6, 2008.

- If the customer applied the Manual Clock workaround on March 16, 2008, then:

For Cisco Unified Communication Manager 3.x or 4.x, sometime after 3:01 A.M. March 16, 2008 it is necessary to re-check the "Automatically adjust clock for DST" box and manually set the server clock to the current local time on each Cisco Unified Communication Manager cluster node.

For Cisco Unified Communication Manager 5.x there is no customer access to the "Automatically adjust clock for DST" setting. The clock should have fell back by one hour at 3:01 A.M. on March 16, 2008. To correct this, after 3:01 A.M. on April 6, 2008, the customer will need to manually set the server clock to the current local time on each Cisco Unified Communication Manager cluster node.

- If the customer fully patched the system for the September 30, 2007 DST start, there's no action required on March 16 or April 6, 2008

- If the customer did nothing in terms of patching or working around issues for the March 16, 2008 DST event (old end date) or after that date, there's no action required on April 6, 2008. The clock would have been off by one hour starting at 3:00 A.M. on March 16, 2008, but this will automatically correct at 3:00 A.M. on April 6, 2008, and would have been behind one hour between March 16 3:00 A.M. and April 6, 2008.

Daylight Saving Time Solution Overview

Depending on the configuration, there are up to three software items which may be required to make a Cisco Unified Communication Manager system Daylight Saving Time compliant.

  1. Cisco Unified Communication Manager Releases

  2. Cisco Unified IP Phone firmware loads

  3. Windows 200x SR Patch

Cisco Unified Communication Manager service release (SR) update:

If any of these service releases or Engineering Special releases (ESs) are installed, then it is required that all nodes in the cluster are upgraded to the same service release or ES version.

Release

Go to this Release

3.3(5)sr2b or lower

3.3(5)sr2c

3.3(5)es36 or lower

3.3(5)sr2c

3.3(5)es37 or higher

3.3(5)es66 or higher

4.1(3)sr5b and lower

4.1(3)sr5c

4.1(3)es106 and lower

4.1(3)sr5c

4.1(3)es107 and higher

4.1(3)es123

4.2(3)sr2b or lower

4.2(3)es43 or higher

4.2(3)es42 or lower

4.2(3)es43 or higher

4.3(1)sr1 or lower

4.3(1)sr1a or higher

4.3(1)es06 and lower

4.3(1)sr1a or higher

4.3(1)es07 or higher

4.3(1)es13 or higher

5.0(4) or lower

5.1(2b) or higher

5.1(1) or lower

5.1(2b) or higher

5.1(2a) or lower

5.1(2b) or higher

6.0(0)

No available fix at this time

   

NOTE:Cisco Unified CallManager Server version 4.1 customers with Unified IP Phone model CP-7940G or CP7960G deployed using SCCP should not use Engineering Special release4.1(3)sr5c. The Engineering Special software for these models phones was corrupted. See Cisco Field Notice FN - 62944 - Cisco Unified CallManager version 4.1.3sr5c fails to upgrade IP Phone modles CP-7940G / CP-7960G for more details.

Please go to the following link for Cisco Unified Communication Manager software downloads:

Voice Software download (registered customers only)

Cisco Unified IP Phone firmware loads:

The 7906, 7911, 7921, 7941, 7961, 7970, 7971 phones require a new phone load that incorporates the Daylight Saving Time changes. The necessary phone resolution for 2007 and higher New Zealand Daylight Saving Time is present in the following phone loads or Device Packages.

Cisco Unified IP Phone firmware load

8.3(2)sr1 standalone phone load or higher

Please go to the following link to download IP Phone loads: IP Phone Loads (registered customers only)

Device Packs

  1. 3.3(5)DevPack 83

  2. 4.1(3)DevPack 57.1

  3. 4.2(3)DevPack 31

  4. 4.3(1)DevPack 14

Windows Patch:

The Windows 2000 Daylight Saving Time patch is installed if any of these versions of MCS OSs are installed. All nodes are required to be on the same version. This patch affects Cisco Unified Communication Manager trace files timestamps and the time display on the server's console.

For more information on theWindows Patch, use the following link: Windows Patch (registered customers only)

Windows Release

Go to

2003.1.2a

2003.1.2a(sr2) or higher

2003.1.1

2003.1.1(sr7) or higher

2000.4.5a

2000.4.5a(sr2) or higher

2000.4.4 or 2000.4.4a

2000.4.4a(sr10) or higher

   

Note:

If you are on a lower OS version then what is listed above, please upgrade to 2000.4.5a or higher.

Cisco Unified Communication Manager OS Manual Workaround 3.x and 4.x

  1. On the new NZ Daylight Saving Time date, Logon with administrator privileges to Cisco Unified Communication Manager Windows Server (starting with Publisher).

  2. Click Start, Settings, Control Panel, Date and Time.

  3. Click on Time Zone tab.

  4. Uncheck the Automatically adjust clock for daylight savings changes check box.

  5. Click on Date and Time tab.

  6. Adjust (if needed) the time to the actual time.

  7. Click Apply or OK.

  8. Repeat steps for all servers in the cluster.

Note:

New Zealand

  1. On or before Sunday September 30, uncheck Automatically adjust clock for Daylight Saving changes.

  2. On September 30, 2007, on or after 3:01 A.M, move the clock forward one hour and then on October 7, after 3:01 A.M., check Automatically adjust clock for Daylight Saving changes.

  3. If OS has not been updated prior to Sunday March 16, uncheck Automatically adjust clock for Daylight Saving changes prior to that date.

  4. On April 4, after 03:01 A.M move the clock back one hour and after 03:01 A.M occurs again, check Automatically Adjust clock for Daylight Saving changes.

Please note, however, that manually adjusting the clock on Cisco Unified Communciation Manager servers could result in a conflict in time which may produce time synchronization issues. For instance, adjusting the clock during any active call would result in incorrect call duration records. Therefore, adjusting the clock is best to be done when fewest active calls are present.

Manual Workaround for Cisco Unified Communcation Manager 5.x or later

To manually configure the time, see The Cisco Unified CallManager Administraion Guide, Release 5.0(4).

Time of Day (TOD) Routing

The following workaround shall be applied for specific configurations of Time of Day Routing.

Notice:

  1. If you are using Time of Day routing that uses type Originating Device (found under the Class of Control menu), and no time zones selected, you DO NOT need to apply this workaround.

  2. If you are using Time of Day routing that uses partitions with specific time zones, YOU MUST IMPLEMENT THE manual workaround below.

Time of Day Workaround:

  1. Under the Class of Control menu, choose the Time of Day setting.

  2. Change the time zone setting to the next western-most time zone for an increment of one hour.

  3. You will need to keep this setting until October 7 for NZ where you will then be required to change the time zone back to the original settings.

For more information on Time of Daylight Routing, please go to the following link: Time of Day Routing.

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

CSCsj67059 (registered customers only)

MCS-OS Update needed for New Zealand DST changes in 2007 (CSCsj56317)

CSCsj56236 (registered customers only)

Callamanger Update needed for New Zealand DST changes in 2007

CSCsj58771 (registered customers only)

Callmanger TOD Routing Update needed for New Zealand DST changes in 2007

CSCsj56317 (registered customers only)

Cisco Unified OS Update needed for New Zealand DST changes in 2007

CSCsj56299 (registered customers only)

CDR Analysis and Reporting does not reflect DST changes for New Zealand

CSCsj58806 (registered customers only)

TNP Phone Update needed for New Zealand DST changes in 2007

   

Revision History

Revision

Date

Comment

1.2

18-SEP-2007

Workaround updated with corrected ES release version.

1.1

14-SEP-2007

Added link to FN - 62944 regarding IP Phone issues with ES.

1.0

04-SEP-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.