![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 558](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550558.webp)
12-12
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 12 System Troubleshooting
Monitoring System Events
Inter-Process Communication Message Send Failure—System (4)
The Inter-Process Communication Message Send Failure alarm (minor) indicates that the IPC message
send has failed. To troubleshoot and correct the cause of the Inter-Process Communication Message
Send Failure alarm, refer to the
“Inter-Process Communication Message Send Failure—System (4)”
Unexpected Inter-Process Communication Message Received—System (5)
The Unexpected Inter-Process Communication Message Received event serves as a warning that an
unexpected IPC message was received. The primary cause of the event is that the IPC process is
receiving messages it is not expecting. To correct the primary cause of the event, contact Cisco TAC.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.
Index List Insert Error—System (6)
The Index List Insert Error alarm (minor) indicates that an error has been inserted in the index list. To
troubleshoot and correct the cause of the Index List Insert Error alarm, refer to the
Error—System (6)” section on page 12-15
Index List Remove Error—System (7)
The Index List Remove Error alarm (minor) indicates that an index list remove error has occurred. To
troubleshoot and correct the cause of the Index List Remove Error alarm, refer to the
Error—System (7)” section on page 12-16
Thread Creation Failure—System (8)
The Thread Creation Failure alarm (major) indicates that a thread creation has failed. To troubleshoot
and correct the cause of the Thread Creation Failure alarm, refer to the
Failure—System (8)” section on page 12-16
Timer Start Failure—System (9)
The Timer Start Failure event serves as a warning that a timer start failure has occurred. The primary
cause of the event is that the process was unable to start a platform timer. To correct the primary cause
of the event, check and see if the problem persists. If the problem persists, call Cisco TAC.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.