 |
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
System descriptor:
vserver process not running
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:
Warning
System descriptor:
Tracing server not running
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
System descriptor:
MWI server not running
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
System descriptor:
mailbox monitor process not running
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
System descriptor:
call me server not running
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:
Minor
System descriptor:
Event monitor server not running
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:
Minor
System descriptor:
Performace Counter server not running
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
System descriptor:
Event/Module ID not in module's rules file
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
System descriptor:
Too many call attempts
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
System descriptor:
MAS CPU occupancy > 90%
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
System descriptor:
MAS disk space > 90%
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.
Level:
Major
System descriptor:
UMROOT\Serviceability\StopServiceMP.exe":"MAS disk space < 250MB
Description:
This alarm indicates that the available disk space on the MAS is less than 250 MB. When this happens, the system runs a maintenance procedure (MP) that stops the primary MAS. If the option to shut down gracefully is selected, then it does so according to the rules of a graceful shutdown.
Repair Procedure:
To correct the condition that causes this alarm, you must free some disk space or add more disk space to the system. To free up disk space, you can
- Use the Windows system Disk Cleanup tool.
- Run the Window system Disk Defragmenter tool.
- Run the chkdsk command.
If the alarm persists after these actions have been taken, then contact your Avaya technical support representative for assistance.
Top of page
