Avaya 03-300430 User Manual

on page 78 describes the SME alarm (for RALM-SVC 

(Remote Alarm Service) and its troubleshooting procedures.

Back to:              

             

1

MAJ

“Far-end alarm service is down” — No remote alarm service is available 
since the other server is unable to report alarms — due to a failure of either 
the GMM or administered reporting mechanisms (SNMP and/or modem).

1. Look for any GMM failures on the other server, either using the:

- Web interface, by selecting Diagnostics > View System Logs and 

- Linux command line, by entering logv -w or, directly, by examining 

/var/log/ecs/wdlog.

2. If a GMM failure was found:

a. See if the GMM application is up, either from the:

- Web interface, by selecting View Process Status
- Linux command line, by entering statapp

b. If so, continue with Step 

If not, try to restart this application by entering start -s GMM on the 

Linux command line.

c. If the GMM application successfully restarts, continue with Step 

If not, escalate the problem to the next higher tier.

3. If a GMM failure was not found, see if alarm reporting failed by looking in 

the trace log for a string that includes “snd2Inads”, either from the:

- Web interface, by:

a. Selecting the View System Logs diagnostic and Logmanager 

Debug trace

b. Specifying the “Event Range” for the appropriate time frame

c. Matching the “snd2Inads” pattern

- Linux command line, by entering 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, either from the:

- Web interface, by selecting Alarms and Notification, the appropriate 

alarm, and Clear

- Linux command line, by entering almclear -n #id