|
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 working, but some software has
generated an alarm with an invalid module or event ID.
Repair procedure:
MT ALARM_ORIG 1
Description:
The system failed to contact the remote maintenance center after
24 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.
- From the MSS Messaging Administration menu, select Alarming > Alarming Configuration.
The system displays the Configure Alarms 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 4.
- Check that the telephone line into the remote maintenance board
(RMB) circuit card is in place.
If your system has an external modem for the RMB, check that
the modem has power and that all the cables are connected.
- Contact
your remote support center.
- After the alarm is resolved, you need to reactivate alarming.
See Resetting alarm origination.
MT BACKUP 1
Description:
An unattended backup failed.
Repair procedure:
- Check that the backup media is correctly inserted in the DVD-RAM
drive.
- If no media is present, insert a writable disk and try the
backup again.
- If media is present, insert a different writable disk into
the drive and try the backup again.
- If the backup still fails, check the backup log file for information
about any errors that occurred during the operation. See Backup
and restore.
- If the previous steps fail, contact your remote support center.
MT BACKUP 2
Description:
An attended backup failed.
Repair procedure:
- Check that the backup media is correctly inserted in the DVD-RAM
drive.
- If no media is present, insert a writable disc and try the
backup again.
- If media is present, insert a different writable disc into
the drive and try the backup again.
- If the backup still fails, check the backup log file for information
about any errors that occurred during the operation. See Backup
and restore.
- Check for any additional alarms associated with the backup process.
- If the previous steps fail, contact your remote support center.
MT BACKUP 3
Description:
The unattended backup did not complete within the expected finish time. This alarm is raised if an unattended backup does not complete within the time specified in the Expected Finish Time field on the Administer Remote Storage page.
Repair procedure:
- Perform an attended backup. This alarm is cleared when an unattended or attended backup completes successfully.
- If the backup is unsuccessful, reboot the system.
MT BKRST 32
Description:
A failure occurred accessing the FTP server.
Repair procedure:
- Check the connection from the Message Storage Server (MSS) to the FTP server.
- Verify that the credentials used to access the FTP server are valid.
- If the previous steps fail, contact your remote support center.
MT BKRST 33
Description:
Network failure (connection lost) during backup or restore.
Repair procedure:
MT BKRST 35
Description:
A failure occurred accessing the SFTP server.
Repair procedure:
- Check the connection from the Message Storage Server (MSS) to the SFTP server.
- Verify that the credentials used to access the SFTP server are valid.
- If the previous steps fail, contact your remote support center.
MT BKRST 36
Description:
Not enough space on the remote FTP/SFTP storage server.
Repair procedure:
Do one of the following:
- Remove unneeded backups from the FTP/SFTP server.
- Add more storage capacity to the FTP/SFTP server.
MT BKRST 37
Description:
The system encountered an error backing up files to the hard drive during an unattended or attended backup.
Repair procedure:
- Perform an attended backup. This alarm is cleared when an unattended or attended backup completes successfully.
- If the backup is unsuccessful, reboot the system.
MT DISK 0
Description:
A hard disk drive failed.
Repair procedure:
MT FAN
Description:
One of the fans in the MSS S3500 server has 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.
HTTPD 1
Description:
This alarm is raised if the httpd process stops. MSS Web administration is not available until the system successfully restarts the process.
Repair procedure:
- Reboot the MSS.
The alarm is automatically cleared when the system successfully restarts the process.
- If the previous step fails, contact your remote support center.
MT NETCONF 1
Description:
The network.conf file is a critical file that contains networking data.
If this file becomes corrupt, it causes serious problems on the system.
This major alarm is raised when the system finds a problem with the this file during an audit, which occurs at the following times:
- Each morning at 5:10 am.
- When you perform a restore from a backup.
- During a software update or upgrade.
- When you open the Network Addressing page. If the audit fails at this time, the system displays a warning at the top of the web page. When this occurs, an error message displays when you click Save indicating that the data cannot be saved because a critical data file is corrupt.
- When you save changes to the Network Addressing page. If the audit fails at this time, the system displays a warning on the bottom on the page
indicating that the file is corrupt.
Repair procedure:
The file must be repaired manually. Contact your remote support center.
MT REBOOT 1
Description:
Reboot warning. The system needs to be rebooted in 15 days. It is recommended that you reboot your system at least once every 180 days.
Repair procedure:
MT RESTORE 1
Description:
A restore failed. The system was unable to receive information
stored on the backup medium or is unable to access the restored
information.
Repair procedure:
- Check the restore log file for information about any errors
that occurred during the operation. See Backup
and restore.
- Check that the backup media was correctly inserted in the DVD-RAM
drive, then try the restore operation again.
- If the previous steps fail, contact your remote support center.
MT SOFTWARE 34
Description:
A system 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:
For a Major alarm, 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.
For a Warning alarm, this is a reminder that the time has been changed on the MSS and should also be changed on each MAS.
Repair procedure:
Do one of the following:
MT UNIX 2
Description:
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.
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:
Top of page
|
