Download Print this page
Avaya Aura Communication Manager Update Manual
Avaya Aura Communication Manager Update Manual

Avaya Aura Communication Manager Update Manual

Hide thumbs Also See for Aura Communication Manager:

Advertisement

Quick Links

Avaya Aura
Methods For Updating Daylight Saving Time Rules
Localities worldwide routinely adjust their Daylight Saving Time (DST) rules.
Communication Manager can automatically adjust for Daylight Saving Time based on
the built-in DST rules for each locality. The DST rules are defined by the version of
the "tzdata" Linux RPM included in the software.
for a particular locality, Communication Manager may require software updates.
There are three methods for handling new DST rules. The availability and
appropriateness of each method for a given system depends on that system's release
and locality.
1. Recent Communication Manager releases have DST rules that were current at
the time of release built into the software.
2. Patches – Some older releases do not have the rules built into the software.
In some cases, patches are available to handle the new rules. These patches
may be applied in addition to a patch already on the system, and supersede
the DST rules originally included in the software (if any).
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 DST start and end dates. In these
procedures
must be followed. The manual procedures may be the only option
for older Communication Manager releases which are beyond End Of
Manufacturer Support (EOMS) and do not have patches available.
Method 1: DST Rules Included in Launched Communication
Manager Releases
Recent releases of Communication Manager have DST rules that were current at the
time of release already built into the software. The following table shows the tzdata
version included in Communication Manager releases:
Communication Manager
Release
3.1.4
3.1.5
4.0.1
4.0.3
4.0.4
4.0.5
5.0
5.1
5.1.1
5.1.2
5.2
5.2.1
6.0
6.0.1
®
Communication Manager
If there is a change in these rules
Software Load
642.1
642.3
731.2
737.4
739.0
742.0
825.4
414.3
415.1
416.4
947.3
016.4
345.0
510.1
1
cases, manual
tzdata version*
2007d
2007d
2007d
2007k
2007k
2007k
2007h
2007k
2008b
2008f
2008i
2009k
2010i
2010l
October 2011, ver 5

Advertisement

loading
Need help?

Need help?

Do you have a question about the Aura Communication Manager and is the answer not in the manual?

Questions and answers

Summary of Contents for Avaya Aura Communication Manager

  • Page 1 ® Avaya Aura Communication Manager Methods For Updating Daylight Saving Time Rules Localities worldwide routinely adjust their Daylight Saving Time (DST) rules. Communication Manager can automatically adjust for Daylight Saving Time based on the built-in DST rules for each locality. The DST rules are defined by the version of the “tzdata”...
  • Page 2 † The patches for CM 5.2.1 and CM 6.0.1 are custom patches not available on the Avaya Support Site. Contact Avaya Global Support Services or your service provider to obtain these patches. 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).
  • Page 3 Manager 7. The patches for CM 5.2.1 and CM 6.0.1 are custom patches not available on the Avaya Support Site. Contact Avaya Global Support Services or your service provider to obtain these patches. To obtain patch installation instructions for releases through CM 5.2.1:...
  • Page 4 3. Select Avaya Aura Communication Manger from the A-Z List (under “A” for Avaya). 4. Select 6.0.x from the Release pull-down menu. 5. Click on the document titled Administering Avaya Aura Communication Manager (Doc ID 03-300509) in the Administration and System Programming section.
  • Page 5 2008f - https://rhn.redhat.com/errata/RHEA-2008-0941.html 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.
  • Page 6 manual procedures may be the only option for older Communication Manager releases which are beyond End Of Manufacturer Support (EOMS) and do not have patches available. This section provides instruction on how to manually make these changes. The two tables below show specific country examples of changes beginning in 2007. Example 1: US and Canada Changes –...
  • Page 7 Communication Manager server. Clock drift occurs when the time on the server slowly deviates or drifts from the correct time. If the clock drift becomes too great the server time should be set to the correct time manually (see below for instructions on setting the time manually).
  • Page 8 3. After the Daylight Saving Time start date using the old rules occurs, the time is automatically adjusted forward one hour on the Server. NOTE: It is very important to let this transition occur and let the Server make the automated time adjustment before taking additional steps! a.
  • Page 9 Manual Procedure to Change Time for End of Daylight Saving Time: 1. If Daylight Saving Time rules other than 0 (zero) are being used in the daylight- savings-rules SAT form, and the rules were not previously changed/adjusted to appropriately reflect the new rules, they must be updated via the SAT. 2.
  • Page 10 REPEAT THIS PROCEDURE ON THE SECOND SERVER OF DUPLICATED SERVER PAIRS!! REPEAT THIS PROCEDURE ON ANY ESS or LSP SERVERS ALSO AFFECTED BY THE DST EXTENSION. No further changes are required until after the Daylight Saving Time end date, using the new rules occurs.
  • Page 11 27 March 2011 as usual, but are not to change back the following October, effectively making Moscow Time UTC+4 permanently. For CM releases not under AVAYA Manufacturer Support (CM4.0.x and below) the following steps should be done to setup the correct time zone: a) Select the time zone from the System Management Interface (SMI) web pages.