Communication Manager: Methods for updating Daylight Saving Time rules


Doc ID    SOLN139859
Version:    7.0
Status:    Published
Published date:    29 Jul 2020
Created Date:    06 Oct 2009
Author:   
Monique Cadena
 

Details

CM DST rules  

Problem Clarification

Several localities worldwide have already extended their Daylight Saving Time (DST) rules or will do so in the future. Avaya Communication Manager can automatically adjust for Daylight Saving Time, based on the built-in rules for Daylight Saving Time for each locality. If there is a change in these rules for a particular locality, Avaya Communication Manager may require software updates.

There are three methods for handling new Daylight Saving Time rules. The availability and appropriateness of each method for a given system depends on that system’s release and locality.

1. Recent releases of Communication Manager have new Daylight Saving Time rules built into the software.

2. Patches – Some older releases do not have the rules built into the software. In many of those cases, patches are available to handle the new rules. These patches may be applied in addition to a patch already on the system.

3. Manual procedures - In some cases, Communication Manager updates (i.e., patch or new release) may not be available soon enough to accommodate support of changing Daylight Saving Time start and end dates. In those cases, manual procedures must be followed.

Cause

n/a

Solution

 For up to date information please refer to http://support.avaya.com/DST/DST_update_methods_v4.pdf

 

Method 1: DST Rules Included in Launched Communication Manager Releases

Some releases of Communication Manager have recent DST changes already built into the software for certain countries. The following table shows which releases include a recent tzdata version:

Communication Manager Release

Software Load

Latest tzdata version*

3.1.4

642.1

2007d

3.1.5

642.3

2007d

4.0.1

731.2

2007d

4.0.3

737.4

2007k

4.0.4

739.0

2007k

5.0

825.4

2007h

5.1

414.3

2007k

5.1.1

415.1

2008b

* See “Tzdata Versions” section below for more information regarding this column.

Method 2: DST Patches

The following S8xx0 Server Communication Manager Daylight Saving Time patches are available:

Communication Manager Release

Software Load

DST Patch

Latest tzdata version*

2.0.1

221.1

00.1.221.1-12514.tar.gz

2006g

2.1

411.7

01.0.411.7-12514.tar.gz

2006g

2.1.1

414.1

01.1.414.1-12514.tar.gz

2006g

2.2

111.4

02.0.111.4-12514.tar.gz

2006g

2.2.2

122.0

02.2.122.0-12514.tar.gz

2006g

3.0

340.3

00.0.340.3-12514.tar.gz

2006g

3.0.1

346.0

00.1.346.0-12514.tar.gz

2006g

3.1

628.6

01.0.628.6-12514.tar.gz

2006g

3.1.1

628.7

01.1.628.7-12514.tar.gz

2006g

3.1.2

632.1

01.2.632.1-14809.tar.gz 1

2007h

3.1.3

640.2

01.3.640.2-12514.tar.gz

2006g

3.1.4

642.1

01.4.642.1-14809.tar.gz

2007h

3.1.5

642.3

01.5.642.3-14809.tar.gz

2007h

4.0

730.5

00.0.730.5-12514.tar.gz

2006g

4.0.1

731.2

00.1.731.2-14809.tar.gz

2007h

 

If the desired patch is not shown in the table above, the change may already be incorporated into a released version of Communication Manager (see Method 1). If the DST change is not available in a patch or in a released version, then the date/time change must be made manually (Method 3).

Special Note for CM 3.1.2 Patch

The original patch for CM 3.1.2, 01.2.632.1-12514.tar.gz, included the 2006g version of tzdata. This patch is now obsolete. The newest patch for CM 3.1.2, 01.2.632.1-14809.tar.gz, contains the 2007h version of tzdata. The 2007h version contains additional updates over and above what was in 2006g. Please refer to the “Tzdata Versions” section to determine if your locality needs the upgrade to 2007h.

For example, most US & Canada localities may continue to use the patches containing 2006g, as those patches contain the changes needed to accommodate the DST rules instituted in March 2007. As an exception, some counties in Indiana will want to use the newer patches containing 2007h, as those patches contain the DST rules that were instituted after March 2007.

To download the correct version of the Daylight Saving Time patch from support.avaya.com:

1. From http://support.avaya.com/ click on Downloads

2. Enter the product Communication Manager

3. Click on Latest TN Circuit Pack, Media Server, and Media Gateway Firmware and Software Updates

4. In the Daylight Saving Time Patches for Media Servers running Communication Manager table click on the appropriate load of Communication Manager (e.g., 632.1).

5. Download the appropriate patch for the specific release of Communication Manager

NOTE: With some web browsers the characters “[1]” are erroneously added to the file name of the download (e.g., 00[1].1.346.0-12514.tar.gz). If this occurs the file name must be renamed to remove the erroneous “[1]” characters. The rest of the file name must be retained. For example, rename the file in the example used above to 00.1.346.0-12514.tar.gz prior to unpacking and activating it on the Media Server.

To obtain patch installation instructions from support.avaya.com:

1. Go to http://support.avaya.com and click DOCUMENTATION

2. Click on Installation, Migrations, Upgrades and Configurations

3. Click on the S8xx0 Server of interest

4. Above the Date List, Click and select the appropriate release (e.g. 3.1.x)

5. Click on Upgrading, Migrating and Converting Media Servers and Gateways to open up document

6. Search for Installing Security and Communication Manager Service Pack Updates for detailed instructions on how to install the service pack on the Server.

7. Disregard any text that instructs you to “deactivate all previous updates when applying a new update”. Daylight Saving Time patches should be applied on top of currently activated patches and Service Packs.

8. After applying the appropriate Daylight Saving Time patch it is necessary to update any rules being used on the daylight-savings-rules SAT form, and then reboot the S8xx0 Media Servers – this is an essential additional step to synchronize all the Linux and Communication Manager processes.

Method 3: Manual Date/Time Changes

If an upgrade cannot be performed, or a DST patch cannot be applied, consult the Manual DST Procedure ADMN105570 for instructions on making date/time changes to your system.

TzdataVersions

Tzdata is a Linux component, or RPM, created and maintained by Red Hat, Inc. This archive file is used by Communication Manager as part of the operating system, and defines “time zone data” (e.g., DST rules) worldwide. As new versions of tzdata are released by Red Hat, they are incorporated into Communication Manager. This file is included in the new releases of Communication Manager, as well as included in patches for the most recent releases already being sold.

To get information about the contents of each version of tzdata, please refer to Red Hat’s web site. Here are references to several of the latest versions of tzdata. If the link below does not work properly, you may need to cut/paste the URL directly into your browser.

2008b - https://rhn.redhat.com/errata/RHEA-2008-0506.html
2007k - https://rhn.redhat.com/errata/RHEA-2008-0185.html

2007h - http://rhn.redhat.com/errata/RHEA-2007-0928.html

2007f - http://rhn.redhat.com/errata/RHEA-2007-0689.html

2007d - http://rhn.redhat.com/errata/RHEA-2007-0128.html

2007c - http://rhn.redhat.com/errata/RHEA-2007-0104.html

2006m - http://rhn.redhat.com/errata/RHEA-2006-0745.html

2006g - http://rhn.redhat.com/errata/RHEA-2006-0622.html

2006a - http://rhn.redhat.com/errata/RHEA-2006-0277.html

2005m - http://rhn.redhat.com/errata/RHEA-2005-656.html

Changes to the tzdata file are cumulative. Files are named chronologically, with the year and a letter designation. Any higher-numbered file is more recent than a lower-numbered file. Newer files contain the most up-to-date information, including any current or updated information from older files. For example, 2007h contains all of the changes in 2007f and all previous versions from 2007. 2007h also includes the current or updated information from any file created in 2006, 2005, etc.

Following are some examples of how different countries were handled with different tzdata versions:

United States The 2005m version has most of the DST changes that went into effect in March 2007. Most US locations are covered with 2005m or later. Isolated US changes have been made to tzdata since then. For example, changes were made in 2007h to handle recent updates for specific counties in Indiana.

Canada – The 2006a and 2006g versions have the main DST changes that went into effect in March 2007.

New Zealand – 2007f contains New Zealand’s DST updates.

Australia – 2007g contains Australia’s DST updates.

 

IMPORTANT - After activating the appropriate Daylight Saving Time patch it is necessary to:

a) re-enter any rules being used on the daylight-savings-rules SAT form

b) re-select the time zone from the System Management Interface (SMI) web pages (pick a different time zone and click submit, then select the desired time zone and submit again).

c) reboot the Server. These are essential additional steps to synchronize all the Linux and Communication Manager processes.

Legacy ID

KB01084331

Additional Relevant Phrases

Remote Servers did not update with the time change. CM 5.2.1

Avaya -- Proprietary. Use pursuant to the terms of your signed agreement or Avaya policy