The following alarms are generated by the MT application and indicate
a problem with the maintenance system:
MT ALARM_ORIG
0
Description:
The alarm generation process is not
working because of a software problem.
Repair Procedure:
MT ALARM_ORIG
1
Description:
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.
Repair Procedure:
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.
Access the Messaging Administration main menu
and select:
The system displays the Alarm
Management page.
- Verify that the
Product ID: and Alarm Destination: fields
have valid entries.
If these fields are blank
or do not have valid entries, contact your remote maintenance center.
If these fields appear to
have valid entries, continue with the Step
3.
- Check that the telephone
line into the remote maintenance circuit card is in place.
If your system has a modem
instead of a remote maintenance circuit card, check that the modem has
power and that all the cables are connected.
- Contact
your remote support center.
MT BACKUP
1
Description:
An unattended backup failed.
Repair Procedure:
MT BACKUP
2
Description:
An attended backup failed.
Repair Procedure:
To repair the alarm:
- Check for any additional
alarms associated with the backup process.
If additional alarms are
found, contact your remote maintenance center.
- Insert a different
cartridge into the cartridge drive and try the backup again.
- If Step
2 fails, contact your remote support center.
MT DISK 0
Description:
A hard disk drive failed.
Repair Procedure:
MT FS 0
Description:
This alarm indicates that the file
system is fragmented. Currently, this is only an informational message.
Repair Procedure:
No corrective action is necessary.
MT REBOOT
1
Description:
Reboot warning. The system needs to
be rebooted in 15 days. Avaya recommends that you reboot your system at
least once every 90 days.
Repair Procedure:
MT RESTORE
1
Description:
A restore failed. The system was unable
to receive information stored on the backup tape or is unable to access
the restored information.
Repair Procedure:
MT SOFTWARE
34
Description:
An INTUITY AUDIX LX process
failed to restart.
Repair Procedure:
MT UNIX 0
Description:
A file system is close to becoming
full. Unless this alarm is resolved, the system might not be able to record
new messages.
Repair Procedure:
MT UNIX 1
Description:
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.
Repair Procedure:
MT UNIX 2
Description:
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.
Repair Procedure:
MT UNIX 3
Description:
The system has too many internal message
queues. The number of message queues is greater than 90 percent of the
system limit.
Repair Procedure:
MT UNIX 4
Description:
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.
Repair Procedure:
MT UNIX 5
Description:
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.
Repair Procedure:
MT UNIX 6
Description:
The system has too many processes
operating and has nearly reached the limit allowed. The system could stop
processing calls or operating at any time.
Repair Procedure:
MT UNIX 7
Description:
The system is operating too many requests
for one login type.
Repair Procedure:
