|
Logs record events that are useful for preventive maintenance,
for diagnosing problems and troubleshooting the server, and for
spotting trends or estimating future needs. Dynamic pages allow
you to view real-time traffic.
Logs
Modular Messaging uses a series of logs as the central collection point for information flowing from the messaging features and feature packages in a Modular Messaging system. These logs provide a system-wide view of activities, errors, and alarms. Reviewing the logs allows a system administrator to reach a quick understanding of overall system status, leading to efficient and effective maintenance and troubleshooting.
Alarms
The MSS supports two types of alarming:
- The Avaya Initialization and Administration System (INADS). This type of alarming requires a modem connection to a remote service center.
- A corporate Simple Network Management Protocol (SNMP) system. If SNMP alarming is used, it is the responsibility of the customer to provide and provision the corporate SNMP network management system (NMS) that will monitor the Modular Messaging system for alarm notifications (traps), and to configure it to receive (and optionally acknowledge) the traps generated by the Modular Messaging system. See SNMP overview for more information on SNMP.
For each type of alarming, the customer can specify:
- The conditions for sending an alarm notification
- The alarm level at which notification will be sent (minor or major)
- The system behavior for stopping Modular Messaging service
Alarm operation
The MSS records problems it detects in the maintenance log. The system then attempts to diagnose and isolate those problems and can send an alarm to the Alarm log if it cannot correct the error automatically.
The contents of the Alarm log represent all of the significant problems the system detects. Therefore, it is the starting point for troubleshooting the system. The Alarm log contains two types of entries:
- Active alarms: Indicate a current problem in the system.
- Resolved alarms: Show alarms that have been corrected either automatically or through a repair procedure.
Three alarm levels indicate the severity of an alarm:
- Major alarms: Indicate problems that could affect key system components or features. For example, if more than 25% of the voice ports are out of service, a major alarm is generated. Major alarms are repairable by technicians.
- Minor alarms: Indicate problems that could affect full service but are not critical to system operation. For example, VM MSGING_FS 0 is a minor alarm. This alarm is logged by the system when the voice storage space is at 90% capacity or greater. Minor alarms are repairable by technicians.
- Warning alarms: Indicate problems that could potentially affect system service if not resolved. For example, if the customer system administrator does not create a trusted server password and a trusted server tries to log in, a warning alarm is generated. Warning alarms are repairable by the customer.
When an active alarm is corrected, its status changes from "active" to "resolved."
Alarm notification
Viewing the Server Events log and the Alarm log on a daily basis is the best way to be informed of new entries. Active alarms (alarms that have not been resolved) and new entries to the Server Events log are noted on the Status Web page.
The Status Web page shows multiple levels of alarms. The alarm level is important because it classifies problems within the system so that the most severe are worked on first. In most cases, the alarm level also marks the area between the responsibility of the system administrator (warning alarms) and the responsibility of the remote service center (major and minor alarms).
Alarm resolution (INADS only)
If the customer purchases a maintenance service contract and activates the alarm origination feature for INADS service, the system automatically sends major and minor alarms to a remote service center for correction. Warning alarms are not sent to a remote service center. Warning alarms must be corrected by the system administrator by using the procedures detailed in Alarms.
Remote service center (INADS only)
The Remote Maintenance Board (RMB) on the Message Storage Server uses a modem to establish a point-to-point protocol (PPP) connection between the messaging system and an Avaya remote service center, or an alternative services support agency. The modem is internal for domestic (United States) systems, or external in other countries. The RMB modem requires an external, direct telephone line or a direct inward dialing (DID) line through the telephony system. The RMB uses this line to report alarms to the services support agency. The remote service center establishes a dial-up connection to the RMB over this same line to help maintain and troubleshoot the system.
Caution!
The only dial-up access to the message server is through the same line that is used for alarm notification. The server cannot report any new alarms while this line is in use. The dial-up connection should be used only for services support of the server, not for routine administration.
See Overview of system logs for a brief description of the logs available on the MSS and MAS.
Log information is organized as follows:
Top of page
|
