![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 318](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550318.webp)
7-86
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 7 Maintenance Troubleshooting
Monitoring Maintenance Events
Inter-Process Communication Input Queue Depth at 75% of its
Hi-Watermark—Maintenance (100)
The Inter-Process Communication Input Queue Depth at 75% of its Hi-Watermark alarm (critical)
indicates that the IPC input queue depth has reached 75 percent of its hi-watermark. To troubleshoot and
correct the cause of the Inter-Process Communication Input Queue Depth at 75% of its Hi-Watermark
alarm, refer to the
“Inter-Process Communication Input Queue Depth at 75% of Its
Hi-Watermark—Maintenance (100)” section on page 7-109
Switchover in Progress—Maintenance (101)
The Switchover in Progress alarm (critical) indicates that a system switchover is progress. This alarm is
issued when a system switchover is in progress either due to manual switchover (via CLI command),
failover switchover, or automatic switchover. No action needs to be taken, the alarm is cleared when
switchover is complete. Service is temporarily suspended for a short period of time during this transition.
Thread Watchdog Counter Close to Expiry for a Thread—Maintenance (102)
The Thread Watchdog Counter Close to Expiry for a Thread alarm (critical) indicates that the thread
watchdog counter is close to expiry for a thread. The primary cause of the alarm is that a software error
has occurred. No further action is required, the BTS 10200 system will automatically recover or
shutdown.
Central Processing Unit is Offline—Maintenance (103)
The Central Processing Unit is Offline alarm (critical) indicates that the CPU is offline. To troubleshoot
and correct the cause of the Central Processing Unit is Offline alarm, refer to the
Unit is Offline—Maintenance (103)” section on page 7-109
.
Aggregration Device Address Successfully Resolved—Maintenance (104)
The Aggregration Device Address Successfully Resolved event functions as an informational alert that
the aggregration device address has been successfully resolved. The event is informational and no
further actions is required.
Unprovisioned Aggregration Device Detected—Maintenance (105)
The Unprovisioned Aggregration Device Detected event serves as a warning that an unprovisioned
aggregration device has been detected. The primary cause of the event is that the AGGR IP address is
not provisioned in AGGR table. To correct the cause of the event, provision the AGGR with the AGGR
IP address in the AGGR table.