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.

MAS Alarms<br />

MAS Alarm - MT ALARM_ORIG 1<br />

Level<br />

Warning.<br />

System Descriptor<br />

Too many call attempts.<br />

Description<br />

This alarm indicates that the system has been trying unsuccessfully to send alarm<br />

notifications for an extended period of time. When trying to send alarm notifications, if<br />

the first attempt is unsuccessful, then the system tries again at five-minute intervals. If<br />

still unsuccessful after 16 tries, then the system stops trying and generates this<br />

warning alarm.<br />

Repair Procedure<br />

The repair action <strong>Avaya</strong> recommends for this alarm depends on which method you are<br />

using to send alarm notifications:<br />

! If you are using INADS, verify that your modem is connected, powered up,<br />

and running properly, and verify that your system is properly configured for<br />

INADS.<br />

For information about INADS configuration, see MAS - Serviceability<br />

Dialog Box on page 4-59.<br />

! If you are using SNMP, verify that your MAS can communicate with your<br />

SNMP network management station, and verify that your system is properly<br />

configured for SNMP notifications.<br />

For information about SNMP configuration, see Serviceability - SNMP<br />

Tab on page 3-140.<br />

If you have completed these steps and the problem still exists, then run the testaom<br />

command in a Command Prompt window. This command provides more detailed<br />

diagnostic information, which may help you resolve the problem.<br />

Once you have resolved the problem, to clear this warning alarm from the system and<br />

verify that the problem no longer exists, run the testaom command again.<br />

If you have tried all this, and the problem still exists, then you should contact your<br />

<strong>Avaya</strong> technical support representative for assistance.<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–19

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

Saved successfully!

Ooh no, something went wrong!