 |
Modular Messaging Help
|
|
|
MT (Maintenance) alarms
|
The following alarms are generated by the MT application and indicate a problem with the maintenance system on the affected MAS:
Level:
Major
Description:
This alarm indicates that the MM Messaging Application Server service is not running.
Repair Procedure:
When the MM Messaging Application Server service restarts successfully, then the system considers the alarm resolved and generates a resolved-alarm event.
If you see this alarm, you can do the following:
- Start the services Monitor application by doing one of the following:
- Double-click the Monitor.msc icon on your desktop.
- Click Start > Programs > Administrative Tools > Services.
- In the Tree pane, select Services (Local).
- In the services list pane, locate the service MM Messaging Application Server, and verify that:
- The Status column entry reads Started.
If the Status column does not indicate that the service is started, you can try to start it manually by double-clicking the service entry and then clicking Start.
- The Startup Type column reads Automatic.
If the system display does not meet these conditions, or if the system does not resolve the alarm automatically within a period of a few minutes, contact your Modular Messaging service or technical support representative for assistance.
Level:
Minor
Description:
This alarm indicates that the MM Tracing Server service is not running.
Repair Procedure:
When the MM Tracing Server service restarts successfully, then the system considers the alarm resolved and generates a resolved-alarm event.
If you see this alarm, you can do the following:
- Start the services Monitor application by doing one of the following:
- Double-click the Monitor.msc icon on your desktop.
- Click Start > Programs > Administrative Tools > Services.
- In the Tree pane, select Services (Local).
- In the services list pane, locate the service MM Tracing Server, and verify that:
- The Status column entry reads Started.
If the Status column does not indicate that the service is started, you can try to start it manually by double-clicking the service entry and then clicking Start.
- The Startup Type column reads Automatic.
If the system display does not meet these conditions, or if the system does not resolve the alarm automatically within a period of a few minutes, contact your Modular Messaging service or technical support representative for assistance.
Level:
Minor
Description:
This alarm indicates that the MM Messaging Waiting Indicator Server service is not running.
Repair Procedure:
When the MM Message Waiting Indicator Server service restarts successfully, then the system considers the alarm resolved and generates a resolved-alarm event.
If you see this alarm, you can do the following:
- Start the services Monitor application by doing one of the following:
- Double-click the Monitor.msc icon on your desktop.
- Click Start > Programs > Administrative Tools > Services.
- In the Tree pane, select Services (Local).
- In the services list pane, locate the service MM Message Waiting Indicator Server, and verify that:
- The Status column entry reads Started.
If the Status column does not indicate that the service is started, you can try to start it manually by double-clicking the service entry and then clicking Start.
- The Startup Type column reads Automatic.
If the system display does not meet these conditions, or if the system does not resolve the alarm automatically within a period of a few minutes, contact your Modular Messaging service or technical support representative for assistance.
Level:
Minor
Description:
This alarm indicates that the MM Mailbox Monitor Server service is not running.
Repair Procedure:
When the MM Mailbox Monitor Server service restarts successfully, then the system considers the alarm resolved and generates a resolved-alarm event.
If you see this alarm, you can do the following:
- Start the services Monitor application by doing one of the following:
- Double-click the Monitor.msc icon on your desktop.
- Click Start > Programs > Administrative Tools > Services.
- In the Tree pane, select Services (Local).
- In the services list pane, locate the service MM Mailbox Monitor Server, and verify that:
- The Status column entry reads Started.
If the Status column does not indicate that the service is started, you can try to start it manually by double-clicking the service entry and then clicking Start.
- The Startup Type column reads Automatic.
If the system display does not meet these conditions, or if the system does not resolve the alarm automatically within a period of a few minutes, contact your Modular Messaging service or technical support representative for assistance.
Level:
Minor
Description:
This alarm indicates that the MM Call Me Server service is not running.
Repair Procedure:
When the MM Call Me Server service restarts successfully, then the system considers the alarm resolved and generates a resolved-alarm event.
If you see this alarm, you can do the following:
- Start the services Monitor application by doing one of the following:
- Double-click the Monitor.msc icon on your desktop.
- Click Start > Programs > Administrative Tools > Services.
- In the Tree pane, select Services (Local).
- In the services list pane, locate the service MM Call Me Server, and verify that:
- The Status column entry reads Started.
If the Status column does not indicate that the service is started, you can try to start it manually by double-clicking the service entry and then clicking Start.
- The Startup Type column reads Automatic.
If the system display does not meet these conditions, or if the system does not resolve the alarm automatically within a period of a few minutes, contact your Modular Messaging service or technical support representative for assistance.
Level:
Major
Description:
This alarm indicates that the MMEventLogMonitor service is not running.
Repair Procedure:
When the MMEventLogMonitor service restarts successfully, then the system considers the alarm resolved and generates a resolved-alarm event.
If you see this alarm, you can do the following:
- Start the services Monitor application by doing one of the following:
- Double-click the Monitor.msc icon on your desktop.
- Click Start > Programs > Administrative Tools > Services.
- In the Tree pane, select Services (Local).
- In the services list pane, locate the service MMEventLogMonitor, and verify that:
- The Status column entry reads Started.
If the Status column does not indicate that the service is started, you can try to start it manually by double-clicking the service entry and then clicking Start.
- The Startup Type column reads Automatic.
If the system display does not meet these conditions, or if the system does not resolve the alarm automatically within a period of a few minutes, contact your Modular Messaging service or technical support representative for assistance.
Level:
Major
Description:
This alarm indicates that the MM Performance Counter Monitor service is not running.
Repair Procedure:
When the MM Performance Counter Monitor service restarts successfully, then the system considers the alarm resolved and generates a resolved-alarm event.
If you see this alarm, you can do the following:
- Start the services Monitor application by doing one of the following:
- Double-click the Monitor.msc icon on your desktop.
- Click Start > Programs > Administrative Tools > Services.
- In the Tree pane, select Services (Local).
- In the services list pane, locate the service MM Performance Counter Monitor, and verify that:
- The Status column entry reads Started.
If the Status column does not indicate that the service is started, you can try to start it manually by double-clicking the service entry and then clicking Start.
- The Startup Type column reads Automatic.
If the system display does not meet these conditions, or if the system does not resolve the alarm automatically within a period of a few minutes, contact your Modular Messaging service or technical support representative for assistance.
Level:
Minor
Description:
This alarm indicates that there was an event or module identified in the alarming service that is not defined in the alarming service’s rules file.
Repair Procedure:
When this alarm is generated, if you have a valid service contract, the system automatically sends a notification to Avaya technical services. No further action is required on your part.
If you do not have a valid service contract, then you should contact your Modular Messaging service or technical support representative for assistance.
Level:
Warning
Description:
This alarm indicates that the system has been trying unsuccessfully to send alarm notifications for an extended period of time. When trying to send alarm notifications, if the first attempt is unsuccessful, then the system tries again at five-minute intervals. If still unsuccessful after 16 tries, then the system stops trying and generates this warning alarm.
Repair Procedure:
The recommended repair action for this alarm depends on which method you are using to send alarm notifications:
- If you are using INADS:
- Verify that your modem is connected, powered up, and running properly.
- Verify that your system is properly configured for INADS.
For information about INADS configuration, see Configuring MAS serviceability.
- If you are using SNMP:
If you have completed these steps and the problem still exists, then run the testaom command in a Command Prompt window. This command provides more detailed diagnostic information, which may help you resolve the problem.
Once you have resolved the problem, to clear this warning alarm from the system and verify that the problem no longer exists, run the testaom command again.
If you have tried all this, and the problem still exists, then you should contact your Modular Messaging service or technical support representative for assistance.
Level:
Warning
Description:
This alarm indicates that too many callers are experiencing delays while interacting with the system. An internal monitor checks the system every 15 minutes, and if three of these checks within an hour indicate that more than 1% of calls have experienced delays, the system generates this warning.
Repair Procedure:
There is no repair procedure for this warning. This alarm could be generated simply as a result of heavier than normal system traffic. Once the system indicates that fewer than 1% of calls are experiencing delays again, then the problem is considered resolved and the system automatically generates a resolved-alarm event.
If you are seeing an excessive number of these warnings or they are not resolved within a reasonable amount of time, then you should contact your Modular Messaging service or technical support representative for assistance.
Level:
Warning
Description:
The system generates this alarm when an excessive number of logon attempts are being aborted because of system delays. If more than five logon attempts are aborted at an average rate of more than one every five minutes, then the system generates this warning alarm.
Repair Procedure:
There is no repair procedure for this warning. Once this alarm has been raised, if the system then detects no new aborted logon attempts for 15 minutes, then the problem is considered resolved and the system automatically generates a resolved-alarm event.
If you are seeing an excessive number of these warnings or they are not resolved within a reasonable amount of time, then you should contact your Modular Messaging service or technical support representative for assistance.
Level:
Warning
Description:
This warning alarm indicates that the spool queue length is greater than or equal to 200. This means that the message spooler has 200 or more messages waiting to be delivered.
Repair Procedure:
There is no repair procedure for this warning. This condition can be caused simply by an excessive amount of message traffic during heavy traffic periods.
Once this alarm has been raised, if the system then detects that the spool queue length drops below 150, then the problem is considered resolved and the system automatically generates a resolved-alarm event.
If you are seeing an excessive number of these warnings or they are not resolved within a reasonable amount of time, then you should contact your Modular Messaging service or technical support representative for assistance.
Level:
Warning
Description:
This warning alarm indicates that the demand for active TUI ports exceeds the number of ports for which you are licensed.
This alarm may indicate that one or more ports is stuck. A stuck port is one that:
- Is not available to take or make calls
- Has been in its current Busy state for a period of time longer than the maximum allowable message time
To view and manage port status for the system, use the Port Monitor tool (see
Using Port Monitor).
Repair Procedure:
When the system detects a stuck port, it automatically attempts to disable and re-enable the port. If it successfully does so, then the problem is considered resolved and the system automatically generates a resolved-alarm event.
If the system is not able to successfully disable and re-enable the stuck port, you can attempt to do so manually. For details on how to do this, see
Managing port states.
As soon as a port becomes available, then the problem is considered resolved and the system automatically generates a resolved-alarm event.
If you are seeing these warnings on a regular basis, and there appears to be no problem with ports being stuck, it may indicate a need to increase the number of ports in your system.
If you are consistently having problems with stuck ports, or these alarms are not resolved within a reasonable amount of time, then you should contact your Modular Messaging service or technical support representative for assistance.
Level:
Warning
Description:
This warning alarm indicates that the CPU of the MAS has run at greater than 90% of its capacity more than four times within an hour.
Repair Procedure:
Once this alarm has been raised, the system continues monitoring. If the occupancy rate subsequently falls below 70% and remains there for at least an hour, then the problem is considered resolved and the system automatically generates a resolved-alarm event.
If the system does not automatically resolve this alarm, you can open the Windows Task Manager and see what processes are putting significant demands on the CPU. If the processes are unrelated to Modular Messaging and you can safely stop them, then do so. If the processes are related to Modular Messaging, then it may indicate a more serious problem requiring in-depth attention. If that is the case, contact your Modular Messaging service or technical support representative for assistance.
Level:
Major
Description:
This alarm indicates that the MAS disk space is 90% or more full.
Repair Procedure:
Once this alarm has been raised, the system continues monitoring. If the disk space usage subsequently falls below 90%, then the problem is considered resolved and the system automatically generates a resolved-alarm event.
If you see this alarm, you can check your system for excessively large files. The log files can become excessively large if not managed properly, and you may need to reconfigure your system to limit the size of these files. For the procedure to do this, see the installation guide for your system.
Also, if you have other files which seem to be consuming a large amount of space, see if you can eliminate or compress them.
