![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 330](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550330.webp)
7-98
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 7 Maintenance Troubleshooting
Troubleshooting Maintenance Alarms
Process Manager: Process Exceeded Restart Rate—Maintenance (19)
The Process Manager: Process Exceeded Restart Rate alarm (major) indicates that a process has
exceeded the restart rate. This alarm is usually caused by a software problem on the specific platform
identified in the alarm report. Soon after this event is issued, one platform will go to faulty state. To
correct the primary cause of the alarm, review the information from CLI log report. On the platform
identified in this alarm report, restart the platform. If platform restart is not successful, reinstall the
application for this platform, and then restart platform again. If necessary, reboot host machine this
platform is located on. Then reinstall and restart all applications on this machine.
If faulty state is a commonly occurring event, then OS or hardware may be a problem. Contact Cisco
TAC for assistance. It may also be helpful to gather information event/alarm reports that were issued
before and after this alarm report.
Lost Connection to Mate—Maintenance (20)
The Lost Connection to Mate alarm (major) indicates that the keepalive module connection to the mate
has been lost. The primary cause of the alarm is that a network interface hardware problem was occurred.
Soon after this event is issued, one platform may go to faulty state. To correct the primary cause of this
alarm, check whether the network interface is down. If so, restore network interface and restart the
software. The secondary cause of the alarm is a router problem. If secondary cause of the alarm is a
router problem, then repair router and reinstall.
Network Interface Down—Maintenance (21)
The Network Interface Down alarm (major) indicates that the network interface has gone down. The
primary cause of the alarm is a network interface hardware problem. Soon after this alarm event is
issued, one platform may go to faulty state. Subsequently system goes faulty. To correct the primary
cause of the alarm, check whether the network interface is down. If so, restore network interface and
restart the software.
Process Manager: Process Failed to Complete Initialization—Maintenance
(23)
The Process Manager: Process Failed to Complete Initialization alarm (major) indicates that a PMG
process failed to complete initialization. The primary cause of the this alarm is that the specified process
failed to complete initialization during the restoral process. To correct the primary cause of the alarm,
verify that the specified process’s binary image is installed. If not, install it and restart the platform.