Chapter 7: Operation and Troubleshooting
General Planning for Troubleshooting
Page 7-62
General Planning for Troubleshooting
Effective troubleshooting depends in part on measures that you take before you experience
trouble in your network. Cambium recommends the following measures for each site:
Procedure:
1
Identify troubleshooting tools that are available at your site (such as a protocol analyzer).
2
Identify commands and other sources that can capture baseline data for the site. These may
include:
•
Ping
•
tracert or traceroute
•
Throughput Test results
•
Throughput data
•
Configure GUI page captures
•
Monitor GUI page captures
•
Session logs
3
Start a log for the site, including:
•
Operating procedures
•
Site-specific configuration records
•
Network topology
•
Software releases
•
Types of hardware deployed
•
Site-specific troubleshooting process
•
Escalation procedures
•
GPS latitude/longitude of each network element
General Fault Isolation Process
Effective troubleshooting also requires an effective fault isolation methodology that includes
•
Attempting to isolate the problem to the level of a system, subsystem, or link, such as
o
Master to Slave
o
Master to CMM
o
CMM to GPS
o
power
•
Researching System Logs of the involved equipment.
•
Answering the questions listed in the following section.
•
Reversing the last previous corrective attempt before proceeding to the next.
•
Performing only one corrective attempt at a time.
