User's Manual Part 4
Release8OperationsGuide
Issue2,November2007 Draft5forRegulatoryReview 470
• researching Event Logs of the involved equipment. (See
Interpreting Messages
in the Event Log
on Page 416.)
• 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.
32.3 QUESTIONSTOHELPISOLATETHEPROBLEM
When a problem occurs, attempt to answer the following questions:
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
• is the problem on one AP in the cluster? (If so, focus on that AP)
• is the problem on multiple, but not all, APs in the cluster? (If so, focus on
those APs)
• 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 Event Log (described in
Interpreting Messages in the Event
Log
on Page 416)
• does the problem correlate to External Hard Resets with no WatchDog timers?
(If so, this indicates a loss of power. Correct your power problem.)
• is intermittent connectivity indicated? (If so, verify your configuration, power
level, jitter, 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?
32.4 SECONDARYSTEPS
After preliminary fault isolation through the above steps
1. check the Cyclone knowledge base (
http://Last Mile
Gear.Cyclonewireless.com/support/knowledge) to find whether other network
operators have encountered a similar problem.
2. proceed to any appropriate set of diagnostic steps. These are organized as
follows:
• Module Has Lost or Does Not Establish Connectivity
• NAT/DHCP-configured SM Has Lost or Does Not Establish Connectivity on
Page
472
•
SM Does Not Register to an AP on Page 474
•
BHS Does Not Register to the BHM on Page 475
•
Module Has Lost or Does Not Gain Sync on Page 476