30.10.2014 Views

Administration Guide - Avaya Support

Administration Guide - Avaya Support

Administration Guide - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

A<br />

Appendix A: MAS Alarms<br />

This appendix gives a description and repair procedure for each alarm that can occur<br />

on the Messaging Application Server (MAS). An alarm indicates a hardware, software,<br />

or environmental problem that could affect system operation.<br />

Displaying Alarms<br />

The system displays MAS alarms in the MAS alarm logs. To display alarm and event<br />

IDs, use the command line interface and the following commands:<br />

! For active alarm IDs, enter displog -l act.<br />

! For resolved alarm IDs, enter displog -l res.<br />

! For maintenance event IDs, enter displog -l maint.<br />

For more information, see Chapter 10, “MAS Event, Error & Alarm Logs”.<br />

Alarm Application Types<br />

The Alarm Application Identifier is the two-letter code used to identify the application<br />

or subsystem for which an alarm is being generated. For example, CM for Call Me.<br />

! MAS Alarms - CM (Call Me) on page A-2.<br />

! MAS Alarms - MM (Mailbox Monitor) on page A-3.<br />

! MAS Alarms - MT (Maintenance) on page A-8.<br />

! MAS Alarms - MW (Message Waiting Indicator) on page A-32.<br />

! MAS Alarms - TS (Tracing Server) on page A-35.<br />

! MAS Alarms - VB (<strong>Avaya</strong> Voice Browser) on page A-40.<br />

! MAS Alarms - VS (Voice Server) on page A-50.<br />

<strong>Avaya</strong> Modular Messaging Release 3.1 with the <strong>Avaya</strong> MSS<br />

February 2007 MAS <strong>Administration</strong> <strong>Guide</strong><br />

A–1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!