Server Alarms - Avaya Support

Server Alarms
Note: If
Note:
a user is logged into a server by an analog modem that is also the server’s only
alarm-reporting interface, enter almsuppress on the Linux command line to
suppress alarm reporting. Otherwise, the other server logs an occurrence of
SME Event ID #1 (see Table 28: SME Alarms).
Clearing Server Alarms
Unlike a Communication Manager alarm, which cannot be cleared unless it is also resolved, a
server alarm:
● Can be manually cleared from its log, with the almclear Linux command
● Should not be considered resolved until it is actually repaired
Displaying Server Alarms
In the following sections, each server alarm is described and its resolution procedure is
provided. Like traditional Communication Manager maintenance objects, the 3-column table for
each server MO shows an alarm’s:
1. Event ID
2. Severity
3. Definition, probable cause, and troubleshooting procedure
To help isolate a server problem, the 3rd column of these tables begins with quoted text for each
event (unlike traditional Communication Manager MOs). The text consists of the verbose (-v)
output of the almdisplay -v Linux command. For example, “interchange hand off failed” is
the quoted text for Arbiter’s Event ID #3.
If the almdisplay command returns a failure message, such as:
almdisplay: 4: Unable to connect to MultiVantage
enter the man almdisplay Linux command for command-related information.
Linux Server Alarms
Server-related alarms and their troubleshooting procedures are described in the following
sections:
● ARB (Arbiter)
38 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers