Table of Contents
Advertisement
Symptoms, Problems, and Solutions
Symptoms, Problems, and Solutions
Failures in networks are often characterized by certain symptoms. These symptoms might be general
(such as clients being incapable of accessing specific numbers) or more specific (routes not existing in
a routing table). In most cases symptoms can be traced to one or more problems or causes by using
specific troubleshooting tools and techniques. After being identified, problems can usually be remedied
by implementing a solution consisting of a series of specific actions.
This guide describes how to define symptoms, identify problems, and implement solutions in those
environments employing a BTS 10200. You should always apply the specific context in which you are
troubleshooting to determine how to detect symptoms and diagnose problems for your specific
environment.
If you are having difficulty installing or starting your BTS 10200, it could be caused by provisioning
problems, or by problems with initial status or control settings. If this is the case, your system should
display one or more status or error messages. These messages are described in detail in the following
chapters along with the probable cause and recommended action(s). General information about the
managing the alarm and error messages is provided in the
page
General Problem-Solving Model
When you are troubleshooting in a telephony environment, a systematic approach always works best.
An unsystematic approach to troubleshooting can result in a "quick fix" but it is usually a waste of
valuable time and resources and often makes the situation worse.
A systematic approach employs the following steps:
•
•
•
Figure 1-1
a rigid outline for troubleshooting a network; it is simply a foundation from which you can build a
problem-solving process to suit your particular environment.
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
1-2
1-9.
Define the specific symptoms
Identify all potential problems that could be causing the symptoms
Systematically eliminate each potential problem (from the most likely to the least likely) until the
symptoms disappear
illustrates the process flow for the general problem-solving model. This process flow is not
Chapter 1
Troubleshooting Overview
"Managing Events and Alarms" section on
OL-8723-19
Advertisement
Chapters
Table of Contents
Troubleshooting
