Avaya WLAN Security Switch 2300 Series, Руководство по устранению неполадок и отладке, Страница: 7 / 74

7
Avaya WLAN Security Switch 2300 Series Troubleshooting and Debug Guide
General troubleshooting tips
Rules of troubleshooting
1 Read the Release Notes!
Release Notes contain important feature functionality information but they also include the “Best
Practices” section which has recommendations for everything from Web-base AAA to 802.1X clients, as
well as documentation on existing issues and known behaviors.
2 Try to reproduce the problem.
If you can create a recipe for recreating the problem it will be fixed quickly. Try to write down what you
were doing prior to the problem and then retracing your steps to make it happen again.
Reproducing the
issue is vital to quick turnaround of fixes.
3 Try to isolate the location of the problem .
Obvious demarcation points are from the WSS to the network, and from the AP to the client. If this is a
packet-related problem you can place sniffers at these points to verify that the packets are entering and
leaving the Avaya gear correctly. This depends on being able to reproduce the problem of course. If
possible, you should also load Ethereal onto the client and/or servers involved in the problem area (i.e. the
DHCP server if client’s aren’t getting IP addresses). In 4.0 the remote sniffing capability will help greatly
with client problems on DAPs.
4 Characterize the problem as specifically as possible and look for patterns.
Is the problem occurring on all clients, or just some? Do the problem clients have any OS, NIC, or
software similarities? Does the problem occur in the same portion of the building? Does the problem
occur only on APs tuned to specific channels? How frequently does the problem occur? Is there any
regularity to the frequency of occurrence?
Useful CLI commands
You can disable the CLI’s press any key to continue prompt by setting the screen length to “0”. You can re-
enable it by setting it back to 24. This makes a text log from terminal programs MUCH easier to read.
set length 0
To transfer the tracefile’s contents off of the switch via TFTP:
save trace tftp://10.1.1.107/trace.txt
Save a backup of the current configuration
save config <filename>
Copying just the configuration via tftp: