-
Troubleshooting Guide
-
Preface
-
Chapter 1 - Troubleshooting Overview
-
Chapter 2 - Audit Troubleshooting
-
Chapter 3 - Billing Troubleshooting
-
Chapter 4 - Call Processing Troubleshooting
-
Chapter 5 - Configuration Troubleshooting
-
Chapter 6 - Database Troubleshooting
-
Chapter 7 - Maintenance Troubleshooting
-
Chapter 8 - Operations Support System Troubleshooting
-
Chapter 9 - Security Troubleshooting
-
Chapter 10 - Signaling Troubleshooting
-
Chapter 11 - Statistics Troubleshooting
-
Chapter 12 - System Troubleshooting
-
Chapter 13 - Network Troubleshooting
-
Chapter 14 - General Troubleshooting
-
Chapter 15 - Diagnostic Tests
-
Chapter 16 - Disaster Recovery Procedures
-
Chapter 17 - Disk Replacement
-
Appendix A - Recoverable and Nonrecoverable Error Codes
-
Appendix B - System Usage of MGW Keepalive Parameters
-
Appendix C - Overload Control
-
Glossary
-
Table Of Contents
Configuration Events and Alarms
Monitoring Configuration Events
Signaling Media Gateway Adapter Wrongly Configured Domain Name—Configuration (2)
Mate Configuration Error—Configuration (3)
Configuration Error—Configuration (4)
Feature-Server Database and Command Line Host Mismatch—Configuration (5)
FIMXML Parse Error—Configuration (6)
Application Server Provisioning Error—Configuration (7)
BTS 10200 Provisioning for External Applications is not Complete—Configuration (8)
Troubleshooting Configuration Alarms
Mate Configuration Error—Configuration (3)
Configuration Error—Configuration (4)
Feature-Server Database and Command Line Host Mismatch—Configuration (5)
Configuration Troubleshooting
Revised: July 22, 2009, OL-8723-19Introduction
This chapter provides the information needed to monitor and troubleshoot configuration events and alarms. This chapter is divided into the following sections:
•
Configuration Events and Alarms—Provides a brief overview of each configuration event and alarm.
•
•
Configuration Events and Alarms
This section provides a brief overview of the configuration events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 5-1 lists all of the configuration events and alarms by severity.
Note
CONFIG (1)
For additional information, refer to the "Test Report—Configuration (1)" section.
CONFIG (2)
For additional information, refer to the "Signaling Media Gateway Adapter Wrongly Configured Domain Name—Configuration (2)" section.
CONFIG (3)
To troubleshoot and correct the cause of the alarm, refer to the "Mate Configuration Error—Configuration (3)" section.
CONFIG (4)
To troubleshoot and correct the cause of the alarm, refer to the "Configuration Error—Configuration (4)" section.
CONFIG (5)
To troubleshoot and correct the cause of the alarm, refer to the "Feature-Server Database and Command Line Host Mismatch—Configuration (5)" section.
CONFIG (6)
To monitor and correct the cause of the event, refer to "FIMXML Parse Error—Configuration (6)" section.
CONFIG (7)
To monitor and correct the cause of the event, refer to "Application Server Provisioning Error—Configuration (7)" section.
CONFIG (8)
To monitor and correct the cause of the event, refer to "BTS 10200 Provisioning for External Applications is not Complete—Configuration (8)" section.
Monitoring Configuration Events
This section provides the information needed to monitor and correct configuration events. Table 5-2 lists all of the configuration events in numerical order and provides cross reference to each subsection in this section.
Table 5-2 BTS 10200 Configuration Events
CONFIG(1)
INFO
CONFIG(2)
Signaling Media Gateway Adapter Wrongly Configured Domain Name—Configuration (2)
INFO
CONFIG(3)
MAJOR
CONFIG(4)
CRITICAL
CONFIG(5)
Feature-Server Database and Command Line Host Mismatch—Configuration (5)
MINOR
CONFIG(6)
WARNING
CONFIG(7)
WARNING
CONFIG(8)
BTS 10200 Provisioning for External Applications is not Complete—Configuration (8)
WARNING
Test Report—Configuration (1)
The Test Report event is used for testing the configuration event category. The event is informational and no further action is required.
Signaling Media Gateway Adapter Wrongly Configured Domain Name—Configuration (2)
The Signaling Media Gateway Adapter Wrongly Configured Domain Name event functions as an informational alert that that signaling media gateway adapter (MGA) is configured with the wrong domain name. The primary cause of the event is that the domain name is invalid. To correct the primary cause of the event, check DNS server and correct domain name. The secondary cause of the event is that the at least half of the local machine address does not match the MGCP domain name. To correct secondary cause of the event, check the DNS server for the domain name to ensure that the IP address is correct.
Mate Configuration Error—Configuration (3)
The Mate Configuration Error alarm (major) indicates that the mate configuration is incorrect. To troubleshoot and correct the cause of the Mate Configuration Error alarm, refer to the "Mate Configuration Error—Configuration (3)" section.
Configuration Error—Configuration (4)
The Configuration Error alarm (critical) indicates that a critical configuration error has occurred. To troubleshoot and correct the cause of the Configuration Error alarm, refer to the "Configuration Error—Configuration (4)" section.
Feature-Server Database and Command Line Host Mismatch—Configuration (5)
The Feature-Server Database and Command Line Host Mismatch alarm (minor) indicates that a feature-server database (DB) and host command line mismatch configuration error has occurred. To troubleshoot and correct the cause of the Feature-Server Database and Command Line Host Mismatch alarm, refer to the "Feature-Server Database and Command Line Host Mismatch—Configuration (5)" section.
FIMXML Parse Error—Configuration (6)
The FIMXML Parse Error event serves as warning that the FIMXMLRules.xml file is missing or has been incorrectly modified. The BTS 10200 software is released with a file named FIMXMLRules.xml. This file is only read during system initialization. It defines how to handle certain features provided on an external application server. The file may be missing or the file has been incorrectly modified. To correct the primary cause of the FIMXML Parse Error event, install the FIMXMLRules.xml file in the appropriate directory. To correct the secondary cause of the event, install valid FIMXMLRules.xml file.
Application Server Provisioning Error—Configuration (7)
The Application Server Provisioning Error event serves as a warning that the external application server has returned a SIP response code that indicates a subscriber is not provisioned on the AS. To correct the cause of the Application Server Provisioning Error event, provision the application server to handle all subscribers which are provisioned on the BTS to use applications on that server.
BTS 10200 Provisioning for External Applications is not Complete—Configuration (8)
The BTS 10200 Provisioning for External Applications is not Complete event serves as warning that the BTS 10200 call agent is provisioned to send a trigger to the Feature Server for OHD or TAT feature. The subscriber is not provisioned to define the sip-trigger-profile ID. To correct the cause of the BTS 10200 Provisioning for External Applications is not Complete event, provision the sip-trigger-profile ID for each subscriber which has OHD or TAT provisioned.
Troubleshooting Configuration Alarms
This section provides the information needed to monitor and correct configuration alarms. Table 5-3 lists all of the configuration alarms in numerical order and provides cross reference to each subsection in this section.
Table 5-3 BTS 10200 Configuration Alarms
CONFIG(3)
MAJOR
CONFIG(4)
CRITICAL
CONFIG(5)
Feature-Server Database and Command Line Host Mismatch—Configuration (5)
MINOR
Mate Configuration Error—Configuration (3)
The Mate Configuration Error alarm (major) indicates that the mate configuration is incorrect. The primary cause of alarm is that the mate and local are configured to be of the same side. To correct the primary cause of the alarm, configure the side of the platform coming up to be the opposite of its mate. The secondary cause of the alarm is that the mate is configured with the wrong mate DNS name or the mate DNS name entries have been changed. To correct the secondary cause of the alarm, properly configure the mate DNS name.
Configuration Error—Configuration (4)
The Configuration Error alarm (critical) indicates that a critical configuration error has occurred. The primary cause of the alarm is that there is incorrect configuration information in the platform.cfg file. To correct the primary cause of the alarm, correct the appropriate configuration parameters in the platform.cfg file.
Feature-Server Database and Command Line Host Mismatch—Configuration (5)
The Feature-Server Database and Command Line Host Mismatch alarm (minor) indicates that a feature-server DB and host command line mismatch configuration error has occurred. The primary cause of the alarm is that the Feature-Server Table is mis-configured. To correct the primary cause of the alarm, reconfigure the Feature-Server table configuration to match command line -host and -port.
