![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 331](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550331.webp)
7-99
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 7 Maintenance Troubleshooting
Troubleshooting Maintenance Alarms
Process Manager: Restarting Process—Maintenance (24)
The Process Manager: Restarting Process alarm (minor) indicates the a PMG process is being restarted.
The primary cause of the alarm is that a software problem process has exited abnormally and had to be
restarted. If problem is recurrent, contact Cisco TAC.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
detailed instructions on contacting Cisco TAC and opening a service request.
Process Manager: Going Faulty—Maintenance (26)
The Process Manager: Going Faulty alarm (major) indicates that a PMG process is going faulty. The
primary cause of the alarm is that the system has been brought down or the system has detected a fault.
If the alarm is not due to the operator intentionally bringing down the system, then the platform has
detected a fault and has shut down. This is typically followed by the Maintenance (3) alarm event. To
correct the primary cause of the alarm, use the corrective action procedures provided for the
Maintenance (3) alarm event. Refer to the
“Local Side has Become Faulty—Maintenance (3)” section
Process Manager: Binary Does not Exist for Process—Maintenance (40)
The Process Manager: Binary Does not Exist for Process alarm (critical) indicates that the platform was
not installed correctly. The primary cause of the alarm is that the platform was not installed correctly.
To correct the primary cause of the alarm, reinstall the platform.
Number of Heartbeat Messages Received is Less Than 50% of
Expected—Maintenance (42)
The Number of Heartbeat Messages Received is Less Than 50% of Expected alarm (major) indicates
that number of HB messages being received is less than 50% of expected number. The primary cause of
the alarm is that a network problem has occurred. To correct the primary cause of the alarm, fix the
network problem.
Process Manager: Process Failed to Come Up in Active Mode—Maintenance
(43)
The Process Manager: Process Failed to Come Up in Active Mode alarm (critical) indicates that the
process has failed to come up in active mode. The primary cause of the alarm is a software or
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
detailed instructions on contacting Cisco TAC and opening a service request.