![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 332](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550332.webp)
7-100
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 7 Maintenance Troubleshooting
Troubleshooting Maintenance Alarms
Process Manager: Process Failed to Come Up in Standby Mode—Maintenance
(44)
The Process Manager: Process Failed to Come Up in Standby Mode alarm (critical) indicates that the
process has failed to come up in standby mode. The primary cause of the alarm is a software or a
configuration problem. To correct the primary cause of the alarm, restart the platform. If problem
persists or is recurrent, 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.
Application Instance State Change Failure—Maintenance (45)
The Application Instance State Change Failure alarm (major) indicates that an application instance state
change failed. The primary cause of the alarm is that a switchover of an application instance failed
because of a platform fault. To correct the primary cause of the alarm, retry the switchover and if
condition continues, 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.
Thread Watchdog Counter Expired for a Thread—Maintenance (47)
The Thread Watchdog Counter Expired for a Thread alarm (critical) indicates that a thread watchdog
counter has expired for a thread. The primary cause of the alarm is a software error. No action is
required, the system will automatically recover or shutdown.
Index Table Usage Exceeded Minor Usage Threshold Level—Maintenance (48)
The Index Table Usage Exceeded Minor Usage Threshold Level alarm (minor) indicates that the IDX
table usage has exceeded the minor threshold crossing usage level. The primary cause of the alarm is
that call traffic has exceeded design limits. To correct the primary cause of the alarm, verify that traffic
is within the rated capacity. The secondary cause of the alarm is that a software problem requiring
additional analysis has occurred. To correct the secondary cause of the alarm, 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.