SME Event ID 1

Last Updated : Oct 07, 2020 |
Alarm level

MAJ

Alarm text

Far end alarm service is down

Cause

No remote alarm service is available. The other server is unable to report alarms due to a failure of either the GMM or its administered reporting mechanisms (SNMP).

Proposed Solution

Procedure

  1. Look for any GMM failures on the other server, either using the:
    1. From the Web interface, select Diagnostics > View System Logs > Watchdog Logs.
    2. From the Linux command line, enter logv -w or by examining the /var/log/ecs/wdlog log file.
  2. If a GMM failure was found:
    1. Check if the GMM application is active:

      • From the Web interface, select View Process Status.

      • From the Linux command line, enter statapp.

    2. If the GMM application is active, continue with Step 3.

      If the GMM application is not active, try to restart this application by entering start -s GMM on the Linux command line.

    3. If the GMM application restarts successfully, continue with Step 4.

    If the GMM application fails to restart, go to the Avaya Support website at http://support.avaya.com to open a service request.

  3. If a GMM failure was not found, check if alarm reporting failed by searching for the string snd2Inads in the trace log:
    1. From the Web interface:

      1. Select View System Logs diagnostic and Logmanager Debug trace.

      2. Specify the event range for the appropriate time frame.

      3. Match the snd2Inads pattern.

    2. From the Linux command line, enter logv -t ts.
  4. Test the administered reporting mechanisms by entering testinads on the Linux command line.
  5. Once the alarm is resolved, manually clear the alarm:
    1. From the Web interface, select Current Alarms and the appropriate alarm, and click Clear.
    2. From the Linux command line, enter almclear -n #id.