General Approach to Troubleshooting WiFi Disconnects

Post a reply


In an effort to prevent automatic submissions, we require that you complete the following challenge.
Smilies
:D :) ;) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :!: :?: :idea: :arrow: :| :mrgreen: :geek: :ugeek:

BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON

Topic review
   

Expand view Topic review: General Approach to Troubleshooting WiFi Disconnects

Re:General Approach to Troubleshooting WiFi Disconnects

by Guest » Mon Nov 15, 2010 12:18 am

Hi, Is this a LWAPP setup or Autonomous AP setup? If it is LWAP, you can get the mac address of a client PC and enable the debugs on the WLC for that specific client with the command "debug client xx:xx:xx:xx:xx:xx". If it is Autonomous AP, you can enable the follwoing debugs: "debug dot11 dot11Radio x trace print"  With the outputs, you will be able to see exactly on which part of the connection it is failing and why the client is dropping, then you can go deep if needed on a specific feature.Also, you have always the question mark on the IOS APs, so you can go deep on the debugs... HTH,Tiago <div class="

General Approach to Troubleshooting WiFi Disconnects

by Guest » Mon Nov 15, 2010 12:10 am

For years I have received occasional complaints about users being dropped from WiF and then reconnecting like a minute or two later.  I wondered what tools people on the Forum used to troubleshoot this transient problem.  Cisco APs like the 1200 don seem to inform aboutwhy someone left.   One thing that has been very helpful over time is using Network Sumbler to see what WAPs are in a vicinity and make sure there is not channel overlap.   What else do folks on the forum use to troubleshoot transient wireless network drops?   Thanks.

Top