The following alarms are generated by the MT application and indicate a problem with the maintenance system:
The system failed to contact the remote maintenance center during six consecutive attempts. The system has active alarms that the remote maintenance center is not receiving.
If any active alarms are severely affecting service, contact your remote support center to report that your system has been unable to contact the center with active alarms.
To repair the alarm:
Check for any additional alarms associated with the backup process.
If additional alarms are found, contact your remote maintenance center.
Check the backup logs for Messaging and Communication Manager to see if a cause for the alarm is displayed.
Check LAN connectivity and the path to the backup server.
If none of the previous steps resolves the issue , contact your remote support center.
This alarm indicates that the file system is fragmented. Currently, this is only an informational message.
Reboot warning. The system needs to be rebooted in 15 days. Avaya recommends that you reboot your system at least once every 90 days.
A file system is close to becoming full. Unless this alarm is resolved, the system might not be able to record new messages.
The system has used up almost all of the inodes. If all of the inodes are in use, the system will not be able to start new processes and could behave as if it were out of space.
The system's memory is low because one of the process is using too much memory. Unless this alarm is resolved, the system can fail.
The system has too many internal message queues. The number of message queues is greater than 90 percent of the system limit.
The system is under an unusually heavy load, and processes are getting behind in answering messages. Unless this alarm is resolved, the system could stop processing calls.
The system has too much information in internal communications. The total amount of information is within 60 percent of the limit. Unless this alarm is resolved, the system could stop processing calls.