|
This topic provides information about the alarms generated by the
MT application. These alarms indicate a problem with the maintenance
system.
Customer-resolvable alarms
The following alarms can be resolved by the system administrator:
MT ALARM_ORIG 1
Description:
The system failed to contact the remote maintenance center on
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 inform them that your system has been unable
to contact the center with active alarms.
- Start at the Administration main menu and select Basic System
Administration > Alarming Administration.
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 support center.
If these fields appear to have valid entries, continue with Step
4.
- 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 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 support center.
- Insert a different CD-RW medium into the CD-RW drive and try
the backup again.
Note: You must use CD-RW media that can support a 10x
backup.
- If Step 2 fails, contact your remote support center.
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:
Alarms requiring remote support center contact
If you receive one of the following alarms, contact
your remote support center.
| ID |
Description |
| MT ALARM_ORIG 0 |
The alarm generation process is not working because
of a software problem. |
| MT BACKUP 1 |
An unattended backup failed. |
| MT DISK 0 |
A hard disk drive failed. |
| MT RESTORE 1 |
A restore failed. The system was unable to receive
information stored on the backup medium or is unable to access
the restored information. |
| MT SOFTWARE 34 |
A Message Networking process failed to restart.
|
| MT UNIX 0 |
A file system is close to becoming full. Unless
this alarm is resolved, the system might not be able to record
new messages. |
| MT UNIX 1 |
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. |
| MT UNIX 2 |
The system's memory is low because one of the
processes is using too much memory. Unless this alarm is resolved,
the system can fail. |
| MT UNIX 3 |
The system has too many internal message queues.
The number of message queues is greater than 90 percent of the
system limit. |
| MT UNIX 4 |
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. |
| MT UNIX 5 |
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. |
| MT UNIX 6 |
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. |
| MT UNIX 7 |
The system is operating too many requests for
one login type. |
Top of page
|
