Troubleshooting problems with Linux time and Communication Manager time

Last Updated : Jan 08, 2024 |

Procedure

  1. Check the Server Date/Time web page or run the Linux date command. Verify that the Linux time is correct. If the Linux time is correct, go to step 2. Otherwise,
    1. If the incorrect time seems to be related to daylight saving time, check the Release String on the Software Version web page, then check http://support.avaya.com to see if the release needs a patch for daylight saving time.

      If a patch for daylight saving time is required, follow the remedial steps provided on the web site.

    2. If the system is configured to use a Network Timing Protocol (NTP) time server, verify that the Time Zone setting is correct on the Server Date/Time maintenance web page and refer to Troubleshooting Network Time Server.
    3. If the server is not configured to use an NTP time server, set the system time and Time Zone using the Server Date/Time maintenance web page.
  2. Enter the display daylight-savings rule SAT command and verify that the start and stop times for Daylight Saving Rule 1 are set correctly.
  3. Enter the display time SAT command to verify that Daylight Saving Rule is set to 1.

    The default is Daylight Saving Rule 0, but the best practice is to use Daylight Saving Rule 1 so that the Communication Manager daylight saving rule is consistent with the rule used by Linux for the system clock. If the Daylight Saving Rule is set to 0, use the set time SAT command to set the Daylight Saving Rule to 1.

  4. Enter the display time SAT command and verify that the Type is correct (Daylight Saving or Standard).

    If the Type is not correct:

    • Submit the change daylight-savings-rules SAT command without changing anything to try to force Communication Manager to think there was a change.

    • You can also change the setting on the daylight-savings-rules screen without changing the Linux time to try to force Communication Manager into the right state. For instance, to change the Type to Daylight Saving when it is still set incorrectly to Standard in April, set the stop time to May and the start time to April. Check the display time screen to see it the Type gets set correctly, then change the daylight saving rule information back to the correct values.

  5. Enter the display locations SAT command and verify that the offset and daylight saving rule are correct for the Main location, and, if the multilocation feature is used, verify that the offsets and daylight saving rules are correct for all other locations.

    Daylight Saving Rule 0 should not be used if the multilocation feature is used. (Check for Multi Locations on the system-parameters customer-options screen to see if the feature is used.) The default is Daylight Saving Rule 0, but the best practice is to use Daylight Saving Rule 1, even if the multilocation feature is not used so that the Communication Manager daylight saving rule is consistent with the rule used by Linux for the system clock.

  6. Check the Location Codes for cabinets, media-gateways, and ip-network-regions. Check the IP network region assigned on the ip-interface form for the processor interface (procr) for embedded servers in gateways
  7. The system must be rebooted if a change was made to the Linux Time Zone setting or if a Daylight Saving Time (DST) patch was applied