Mate Changeover Timeout—Maintenance (8) - Cisco BTS 10200 Troubleshooting Manual

Chapter 7 Maintenance Troubleshooting
Mate Changeover Timeout—Maintenance (8)
The Mate Changeover Timeout alarm (major) indicates that the mate changeover timed out. The primary
cause of the alarm is that the mate is faulty. This alarm is usually caused by a software problem on the
specific mate platform identified in the alarm report. To correct the primary cause of the alarm, review
information from CLI log report concerning faulty mate. On the mate platform identified in this alarm
report, restart the platform. If mate platform restart is not successful, reinstall the application for this
mate platform, and then restart mate platform again. If necessary, reboot host machine this mate platform
is located on. Then reinstall and restart all applications on that machine.
Local Initialization Failure—Maintenance (9)
The Local Initialization Failure alarm (major) indicates that the local initialization has failed. The
primary cause of the alarm is that the local initialization has failed. When this alarm event report is
issued, the system has failed and the re-initialization process has failed. To correct the primary cause of
the alarm, check that the binary files are present for the unit (Call Agent, Feature Server, Element
Manager). If the files are not present, then re-install the files from the initial or the backup media. Then
restart the failed device.
Local Initialization Timeout—Maintenance (10)
The Local Initialization Timeout alarm (major) indicates that the local initialization has timed out. The
primary cause of this alarm is that the local initialization has timed out. When the event report is issued,
the system has failed and the re-initialization process has failed. To correct the primary cause of the
alarm, check that the binary files are present for the unit (Call Agent, Feature, Server, or Element
Manager). If the files are not present, then re-install the files from initial or backup media. Then restart
the failed device.
Process Manager: Process has Died—Maintenance (18)
The Process Manager: Process has Died alarm (minor) indicates that a process has died. The primary
cause of the alarm is that a software problem has occurred. If problem persists or is reoccurring, contact
Cisco TAC.
Note Refer to the
detailed instructions on contacting Cisco TAC and opening a service request.
OL-8723-19
"Obtaining Documentation and Submitting a Service Request" section on page lvi
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
Troubleshooting Maintenance Alarms
for
7-97