Scribd Logo
Upload

Welcome to Scribd!

  • Update Time on OmniPCX Enterprise Safely

    Uploaded by

    Humberto Ochoa Mendez
    11 views2 pages
    This technical document outlines the risks of updating time on an OmniPCX Enterprise system without restarting. It notes that if the current date is over a year or under 3 years from the correct date, a restart is mandatory. Failing to restart after a time update can cause a loop that consumes all CPU resources, causing the system to crash. The document provides examples of backtraces and incidents that may occur during such a loop, such as flickering displays and aborted phone tasks. The only solution is to restart the CPU after any time update.

    Original Description:

    UPDATE

    Original Title

    TC1279en_Ed02

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    This technical document outlines the risks of updating time on an OmniPCX Enterprise system without restarting. It notes that if the current date is over a year or under 3 years from the correct date, a restart is mandatory. Failing to restart after a time update can cause a loop that consumes all CPU resources, causing the system to crash. The document provides examples of backtraces and incidents that may occur during such a loop, such as flickering displays and aborted phone tasks. The only solution is to restart the CPU after any time update.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    11 views2 pages

    Update Time on OmniPCX Enterprise Safely

    Uploaded by

    Humberto Ochoa Mendez
    This technical document outlines the risks of updating time on an OmniPCX Enterprise system without restarting. It notes that if the current date is over a year or under 3 years from the correct date, a restart is mandatory. Failing to restart after a time update can cause a loop that consumes all CPU resources, causing the system to crash. The document provides examples of backtraces and incidents that may occur during such a loop, such as flickering displays and aborted phone tasks. The only solution is to restart the CPU after any time update.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 2

    TECHNICAL COMMUNICATION No. TC1279 Ed.

    02

    OmniPCX Enterprise Nb of pages : 2 Date : 28 January 2010

    URGENT

    NOT URGENT TEMPORARY PERMANENT

    SUBJECT: UPDATE OF TIME ON OmniPCX Enterprise: RISK OF SYSTEM CRASH

    1. INTRODUCTION
    There are several ways to update time on OmniPCX Enterprise:
    − With external NTP server.
    − With swinst menu.
    − With network call through ABC-F inter node link.
    − With Daylight Saving Time.

    2. RESTRICTIONS AND LIMITATIONS


    Due to a memory limitation, it is always mandatory to restart the system after updating time if:
    − current date on OmniPCX Enterprise is less than one year as correct date,
    − current date on OmniPCX Enterprise is higher than 3 years as correct date.
    In case of duplication, both CPU must be restarted.

    3. CONSEQUENCES
    If the time was updated without restarting the system, a message on UA protocol can lead to a loop.
    This loop will take all resources on CPU and CPU will crash.
    During this loop, display on set will flicker. Some backtraces with incidents should occur on the system
    involving digital sets equipments.
    Backtraces:
    * Backtrace: 0x083c501a:138170394 EBP 0x01806df0 --> send_pn_ua(void) (+18) 90%
    * Backtrace: 0x08491611:139007505 EBP 0x01806df8 --> send_pn(void) (+161) 75%
    * Backtrace: 0x08307b10:137394960 EBP 0x01806e04 --> lib_demi(void) (+780) 29%
    * Backtrace: 0x083076c5:137393861 EBP 0x01806e88 --> li_demi(void) (+425) 98%
    * Backtrace: 0x08e48c7f:149195903 EBP 0x01806e9c -->
    updateTermTimeZoneIdleState(void) (+931) 95%
    * Backtrace: 0x092b6d3a:153840954 EBP 0x01806ec0 --> real_main (+2586) 85%

    * Backtrace: 0x084fface:139459278 EBP 0x01826d60 --> SendCxTonaMsg(tPhyAddr *,


    tPhyAddr *, aux_ton, aux_ton) (+818) 98%
    * Backtrace: 0x084f3340:139408192 EBP 0x01826d94 --> CH_CxTona(tPhyAddr *,
    * Backtrace: 0x0836ab39:137800505 EBP 0x01826dd0 --> lib_representation(int)
    (+3105) 99%
    * Backtrace: 0x08307a7b:137394811 EBP 0x01826e18 --> lib_demi(void) (+631) 23%
    * Backtrace: 0x08e48ca1:149195937 EBP 0x01826ea0 -->
    updateTermTimeZoneIdleState(void) (+965) 99%
    * Backtrace: 0x092b6d3a:153840954 EBP 0x01826ec0 --> real_main (+2586) 85%

    1
    TECHNICAL COMMUNICATION No. TC1279 Ed. 02

    OmniPCX Enterprise Nb of pages : 2 Date : 28 January 2010

    URGENT

    NOT URGENT TEMPORARY PERMANENT

    SUBJECT: UPDATE OF TIME ON OmniPCX Enterprise: RISK OF SYSTEM CRASH

    Incidents:
    1722=Aborted telephone task, PC 0x0934417b exc -10 neqt 1123
    1602=IO1 driver error, full output link 25

    Based of the number of sets impacted, theses messages can do saturation of IO1 virtual board
    resulting by crash of the CPU.

    4. SOLUTION
    A restart of the CPU put back the system in normal situation.

    You might also like