Troubleshooting guide

Introduction
1-19
• Record any changes that occurred since the last time the BSR was operating
properly. Investigate any configuration changes that might be related to the
problem.
Viewing Symptoms
Perform the following tasks to view and compare symptoms that are related to a
problem:
• Repeat the conditions that led to the symptom. Consider any errors or failures that
can cause a particular symptom, and test them to see if they are causing the
symptom.
• Determine if any symptoms are related. Are there unexpected or undesired results
in more than one area? If so, find the areas in common and the variables that
affect them. The source of the problem is often found in similar areas.
• Focus on one symptom or a set of related symptoms of a problem. However, do
not completely disregard other symptoms, because what may appear to be an
unrelated problem may actually be related based on other symptoms.
Isolating the Problem
A problem can have one or more causes. To identify the cause of unwanted behavior,
use the following techniques:
• Isolate the problem. For example, isolate a problem to one part of the network or
to a specific access module.
• Find the functions that are working correctly.
• Retrace the steps that were taken, and return the network to its condition before
the problem first appeared. Once the network is in a known condition, take
incremental steps and observe the network to learn when and where the problems
occur.
• Determine if there have been any additions, changes, or upgrades to the network.
If so, consider any consequences the changes could have had on the network, and
whether they affect the current situation.