S87xx Series Media Servers running Communication Manager 2.x, 3.X and 4.0: DST Problems


Doc ID    SOLN139860
Version:    2.0
Status:    Published
Published date:    06 May 2012
Created Date:    06 Oct 2009
Author:   
Monique Cadena
 

Problem Clarification

The Following steps must be followed in the exact order specified for Daylight Saving Time problems on S87xx Series Media Servers running Communication Manager 2.x, 3.X and 4.0 releases that are located in the United States or Canada.

Solution

1. On the Active Server, verify correct Communication Manager daylight saving time rules on the daylight-savings-rules form via the SAT. Change them if necessary. The following is an example of a correct rule to support the new daylight saving time rule changes:

2. On the Active Server via the SAT, use the set time form to verify the correct daylight saving rule is being used in the Daylight Savings Rule field. Change if necessary. In the example screen capture above rule 1 should be used for time zones adhering to new daylight saving time rules.

3. Use the display locations form on the Active Server SAT to verify the correct rules are being used for all locations. This should be done regardless of whether the multi-location feature is being used because the main location must always be set correctly. Make changes if necessary.

4. From the Active Server SAT, run the save translation command.

5. From the Standby Server Maintenance Web Interface select Make Upgrade Permanent and click the Submit button to ensure rebooting into the correct partition.

6. From the Standby Server Maintenance Web Interface select Busy-out Server and click the Busy-Out button. Verify the standby server is busied out by selecting Status Summary.

7. From the Standby Server Maintenance Web Interface perform a Backup Now and select Full Backup or select all available backup sets.

8. Download the correct version of the Daylight Saving Time patch from support.avaya.com, if one is available and not already applied on the servers.

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

b. Enter the product name Communication Manager

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

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

e. Download the patch

9. Apply the appropriate Daylight Saving Time patch on the Standby server, if one is available and not already applied. Daylight Saving Time patches should be applied on top of currently activated patches and Service Packs. Instructions on installing/activating patches can be obtained from support.avaya.com:

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

b. Enter the product name Communication Manager

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

d. Click on Communication Manager 2.0 and Later Software Update Procedures to access patch application instructions.

e. Disregard text in the Software Update Procedures document that states “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.

10. From the Standby Server Maintenance Web Interface configure the time server as desired. Steps a through g directly below can be used to enable a network time server if it was previously disabled to support a manual DST workaround. If a network time server is not desired do not configure the time server as specified in steps a through g below.

a. Select Configure Server from the Maintenance Web Interface

b. Click the Continue button to proceed until a Configure individual services radio button is available

c. Select the Configure individual services radio button and click the Continue button

d. Select Configure Time Server

e. Select the Use these Network Time Servers radio button and provide the Network Time Server information.

f. Click the Change button and the message Successfully added NTP information should be displayed.

g. Click the Close window button.

11. Verify the Linux time is correct from the Maintenance Web Interface on the Standby Server by selecting Server Date/Time and checking that the time and time zone are correct. Correct them if necessary.

12. From the Standby Server Maintenance Web Interface select Shutdown Server. Make sure the Delayed Shutdown radio button is selected and the Restart server after shutdown check box is selected. Then click the Shutdown button.

13. Wait for the Standby Server to reboot (about 5 minutes) and then select Release Server from the Standby Server Maintenance Web Interface and click the Release button.

14. From the Standby Server Maintenance Web Interface select Status Summary and verify the Mode is Standby, Duplication Link is up, Standby Shadowing is on, and Standby Refreshed is yes.

15. From the Standby Server Maintenance Web Interface select Interchange Servers, DO NOT SELECT the Force interchange regardless of server status check box. If the Force interchange regardless of server status check box is selected, UNCHECK IT! Then click on the Interchange button.

16. From the new Active Server (used to be the Standby Server) Maintenance Web Interface select Status Summary and verify the Mode now shows Active.

17. Repeat steps 5 through 14 on the new Standby Server (used to be the Active Server). This must be done to ensure both servers in a server pair have been fixed!

18. On the Active Server check that the time is valid.

a. Verify the Linux time is correct from the Maintenance Web Interface by selecting Server Date/Time and checking that the time and time zone are correct.

b. Verify the time stamps are correct on the display time, list measurement occupancy summary, list measurement occupancy last, list measurement sum and monitor bcms system SAT forms.

c. Verify the time on telephone displays is correct by pressing the Date/Time button on phones.

Legacy ID

KB01084333

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