Wi Lan Inc EB03 Benutzerhandbuch
JUL 2001 Rev 03
107
Troubleshooting
Administrative Best Practices
By performing some administrative best practices and preventative maintenance, you can prevent many
problems with your system, or become aware of minor problems before they become serious ones.
problems with your system, or become aware of minor problems before they become serious ones.
Wi-LAN recommends the following practices.
•
Maintain the integrity of the system design when adding or changing a system. The introduction of
new elements to a system can cause problems unless the network plan is revised to take into account
the changes. For example, improper installation of a co-located antenna can add unwanted system
interference.
new elements to a system can cause problems unless the network plan is revised to take into account
the changes. For example, improper installation of a co-located antenna can add unwanted system
interference.
•
Measure and document system performance at the time of the original installation.
•
Monitor system performance regularly. Environmental change as well as normal wear and tear on
components can affect system performance.
components can affect system performance.
•
Perform preventative maintenance every 6 months. See
28 for information.
•
After periods of extreme weather, perform link monitor tests to verify the system; inspect towers,
antennas, cables and connectors for damage.
antennas, cables and connectors for damage.
•
Change menu passwords so that only key personnel can reconfigure the system. See
•
Keep records of recent changes. Especially document the addition of units, hardware and software
changes and changes to configuration settings. Configuration errors often cause other problems.
Current records can be compared with original installation records and function as a benchmark to
help you troubleshoot.
changes and changes to configuration settings. Configuration errors often cause other problems.
Current records can be compared with original installation records and function as a benchmark to
help you troubleshoot.
•
Keep a log of past and present problems and solutions. Store the log on-site, if possible. The log
identifies common failure points and fixes.
identifies common failure points and fixes.
•
Before contacting Wi-LAN for customer support, document the symptoms of the problem and the
steps taken to diagnose and fix the problem. Record the current configuration of the system.
steps taken to diagnose and fix the problem. Record the current configuration of the system.