Troubleshooting guide

2-12
Cisco Broadband Local Integrated Services Solution Troubleshooting Guide
OL-5169-01
Chapter 2 Troubleshooting Overview
Troubleshooting Tools
The results of call traces are signal flow diagrams that you can use for troubleshooting. Call traces are
typically used to capture system activity as part of a procedure to clear an alarm. You should have a trace
of all normal call functions to use as a baseline to compare to when problems arise.
System Logs
The Cisco BTS 10200 Softswitch software continuously generates log files of various system
information, including operational measurements (OMs) and alarm records. You can use these logs to
obtain statistical information about the calls processed by the system and network events such as delays
or service-affecting conditions. The Cisco BTS 10200 Softswitch generates the following types of logs:
Diagnostic Commands
The following integrated IOS command types are also provided to assist you in monitoring and
troubleshooting systems:
• Show
• Debug
• Ping
• Trace
Show Commands
The show commands are powerful monitoring and troubleshooting tools. You can use the show
commands to perform a variety of functions:
• Monitoring router behavior during initial installation
• Monitoring normal network operation
• Isolating problem interfaces, nodes, media, or applications
• Determining when a network is congested
• Determining the status of servers, clients, or other neighbors
Note It is a good idea to use the trace command when the network is functioning properly under normal
conditions so that you have something to compare against when troubleshooting.
Table 2-1 System Log Types
Log Type Description
Platform logs Contain information useful for tracking configuration errors and
signaling link and call instantiation problems.
Command/response logs Contain CLI command history.
Alarm logs Contain alarm information.
Measurement logs Contain system measurements data.
Call record logs Contain call-processing data.