Motorola Canopy Backhaul Module Podręcznik Użytkownika Strona 376

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
Przeglądanie stron 375
March 2005 Managing Your Canopy Network
Through Software Release 6.1
Page 376 of 425 Issue 1
Canopy System User Guide
31 TROUBLESHOOTING
31.1 GENERAL PLANNING FOR TROUBLESHOOTING
Effective troubleshooting depends in part on measures that you take before you
experience trouble in your network. Canopy 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 Test results
throughput data
Configuration screen captures
Status page 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.
31.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
Przeglądanie stron 375
1 2 ... 371 372 373 374 375 376 377 378 379 380 381 ... 424 425

Komentarze do niniejszej Instrukcji

Brak uwag