Avaya 11-300244 사용자 설명서

Avaya Modular Messaging Concepts and Planning Guide

5-12

 November 2004

Avaya Modular Messaging Concepts and 

Planning Guide

Since a messaging application server (MAS) runs on a standard Microsoft 
Windows operating system, a variety of Microsoft Windows tools can be 
used for monitoring the MAS services. These tools include:

!

The Windows Performance Monitor to generate statistics and 
performance information. 

!

The Windows Event Log to record and trace significant events or 
alarms.

The MAS and the Avaya Message Storage Server (MSS) generate system 
alarm and error logs that can be accessed using a command line interface 
tool. This command line interface tool is called displog on the MAS. 

Notifications that alarms generate can be sent to any one of the following:

!

Avaya Services

!

A network management station (NMS)

!

A Business Partner. Business Partners need access to the Modular 
Messaging system to receive these notifications

!

Avaya Fault and Performance Manager with use of either Secure 
Services Gateway (SSG) or Avaya Proxy Agent

Systems can be configured such that these alarm notifications are sent to a 
service organization either using a dial-up modem to the Avaya 
Initialization and Administration System (INADS) or by means of Simple 
Network Management Protocol (SNMP) traps. The MSS can also use the 
SNMP protocol to send these notifications to a customer NMS. For 
details of SNMP traps, see 

 on page 5-15.

If the system is configured for INADS alarms, MAS uses its built-in 
dial-up modem, whereas the MSS uses the Remote Maintenance Board 
(RMB) to send notifications to INADS.

Using the command line interface tools supplied with each MAS, 
administrators can view the following logs:

!

The event log, which contains events and errors generally of 
interest to only technical services and development personnel.

Note: The event log is not the same as the Windows Event 

Log.