Local Side Has Become Faulty—Maintenance (3) - Cisco BTS 10200 Troubleshooting Manual

Troubleshooting Maintenance Alarms
Table 7-3 BTS 10200 Maintenance Alarms (continued)
Alarm Type
MAINTENANCE(102)
MAINTENANCE(103)
MAINTENANCE(107)
MAINTENANCE(109)
MAINTENANCE(110)
MAINTENANCE(111)
MAINTENANCE(112)
MAINTENANCE(117)
MAINTENANCE(118)
MAINTENANCE(119)
Local Side has Become Faulty—Maintenance (3)
The Local Side has Become Faulty alarm (major) indicates that the local side has become faulty. The
alarm can result from maintenance reports 5, 6, 9, 10, 19, or 20. Review information from CLI log report.
The alarm is usually caused by a software problem. To correct the primary cause of the alarm, restart the
software using the Installation and Startup procedure. The alarm can also be caused by manually shutting
down the system using platform stop command. To correct the secondary cause of the alarm, reboot
host machine, reinstall all applications and restart all applications. If the alarm is reoccurring, the
operating system or the hardware may have a problem.
Mate Side has Become Faulty—Maintenance (4)
The Mate Side has Become Faulty alarm (major) indicates that the mate side has become faulty. The
primary cause of the alarm is that the local side has detected the mate side going into a faulty state. To
correct the primary cause of the alarm, display the event summary on the faulty mate side, using the
report event-summary command (see the CLI Guide for command details). Review information in the
event summary. The alarm is usually caused by a software problem. After confirming the active side is
processing traffic, restart software on the mate side. Log in to the mate platform as root user. Enter
platform stop command and then platform start command. If a software restart does not resolve the
problem or if the platform goes immediately to faulty again, or does not start, contact Cisco TAC. It may
be necessary to reinstall software. If the alarm is reoccurring, then the operating system or the hardware
may have a problem. Reboot host machine, then reinstall and restart all applications. The reboot will
bring down the other applications running on the machine. Contact Cisco TAC for assistance.
Note Refer to the
detailed instructions on contacting Cisco TAC and opening a service request.
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
7-92
Alarm Name
Thread Watchdog Counter Close to Expiry for a Thread—Maintenance (102)
Central Processing Unit is Offline—Maintenance (103)
No Heartbeat Messages Received Through Interface From Router—Maintenance
(107)
Five Successive Log Files Cannot be Transferred—Maintenance (109)
Access to Log Archive Facility Configuration File Failed or File
Corrupted—Maintenance (110)
Cannot Login to External Archive Server—Maintenance (111)
Congestion Status—Maintenance (112)
Side Automatically Restarting Due to Fault—Maintenance (117)
Domain Name Server Zone Database does not Match Between the Primary
Domain Name Server and the Internal Secondary Authoritative Domain Name
Server—Maintenance (118)
Periodic Shared Memory Database Backup Failure—Maintenance (119)
"Obtaining Documentation and Submitting a Service Request" section on page lvi
Chapter 7 Maintenance Troubleshooting
Alarm Severity
CRITICAL
CRITICAL
CRITICAL
MAJOR
MAJOR
CRITICAL
MAJOR
CRITICAL
CRITICAL
CRITICAL
OL-8723-19
for