Troubleshooting guide

BSR Troubleshooting Guide
1-18
4. Document the changes and effects of changes as you perform troubleshooting
procedures, and note any new troubleshooting procedures that you use. This
simple precaution helps to avoid repeating steps, allows for future reference in
case the problem reoccurs, and is especially useful for troubleshooting
intermittent problems.
5. Determine if the problem is solved. Ensure that the troubleshooting procedure did
not cause new problems.
6. If the problem is not solved, try to identify problem causes more clearly, isolate
any additional causes, and perform additional troubleshooting procedures to
correct the problem.
Discovering Problems
Ensure that you thoroughly understand the network so that you can establish a
baseline from which to work, and distinguish the differences between normal and
abnormal activity on the network.
Perform the following steps to determine the source of problems:
• Review release notes and technical bulletins to determine if there are any
incompatibilities or known problems.
• Gather information for all the possible causes or symptoms to more quickly
isolate the problem.
• Discover if the problem relates to another problem that you must solve first.
• Record all configuration parameters that relate to the problem.
• Determine if the network configuration has changed recently, such as the addition
or removal of components, upgrading, or reconfiguration.
• Identify aspects that causes or symptoms have in common to determine if they are
related.
• Look for network patterns in the causes. What time of day did these problems
occur? What events were logged? What network thresholds were transgressed?
• Record any changes that occurred since the network was last functioning
correctly. Changes in network activity may relate to a configuration change.