User's Manual Part 4

Release8OperationsGuide


Issue2,November2007 Draft5forRegulatoryReview 469
32 TROUBLESHOOTING
32.1 GENERALPLANNINGFORTROUBLESHOOTING
Effective troubleshooting depends in part on measures that you take before you
experience trouble in your network. Cyclone recommends the following measures for
each site:
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
• Link Capacity Test results
• throughput data
• Configuration tab captures
• Status tab captures
• session logs
3. Start a log for the site.
4. Include the following information in the log:
• operating procedures
• site-specific configuration records
• network topology
• software releases, boot versions, and FPGA firmware versions
• types of hardware deployed
• site-specific troubleshooting processes
• escalation procedures
5. Capture baseline data into the log from the sources listed in Step 2.
32.2 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
• AP to SM
• AP to CMM
• AP to GPS
• CMM to GPS
• BHM to BHS
• BHM to CMM
• power