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
- AP to SM
- AP to CMM
- AP to GPS
- CMM to GPS
- 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.
Questions to Help Isolate the Problem
|
Step |
Action |
|
1 |
What is the history of the problem? · Have we changed something recently? · Have we seen other symptoms before this? |
|
2 |
How wide-spread is the symptom? · Is the problem on only a single SM? (If so, focus on that SM.) · Is the problem on multiple SMs? If so: o is the problem on one AP in the cluster? (If so, focus on that AP) o is the problem on multiple, but not all, APs in the cluster? (If so, focus on those APs) o is the problem on all APs in the cluster? (If so, focus on the CMM and the GPS signal.) |
|
3 |
Based on data in the System Log · Is intermittent connectivity indicated? (If so, verify your configuration, power level, CINR, cables and connections, and the speed duplex of both ends of the link). · Does the problem correlate to loss-of-sync events? |
|
4 |
Are connections made via shielded cables? |
|
5 |
Does the GPS antenna have an unobstructed view of the entire horizon? |