03-05-2019 05:51 PM
Most of the time people are using the wired network. Works fine. Lately (last 2 months+) people are having more and more issues connecting to the wifi and are getting dropped when moving around the office. The vendor who installed the AP's came in to do some diag and has more information, I can put you in touch with him if that helps.
03-05-2019 08:22 PM
Thank you for those logs. I've sent you some screen shots so you can exactly what I'm referencing in your data.
The first screen shots labeled show acsp neighbor wifi0/1 shows the output for the command "show acsp neighbor" for wifi0 and wifi1 respectively. In this output, the RSSI values we want to see would be -75 or lower. The closer to 0 this value is, the louder that AP is, and the more interference you will be experiencing. In your case you can see we have several neighbors in the -50s and -40s, which are much too loud. I would recommend lowering the power on your APs (I usually lower by 2dBm per test to avoid drastic shifts in coverage).
The next two screen shots labeled show interface wifi0/1 show some deeper stats on how the radios are doing. You can see that both are in a state of high collision (we want that to be Good or Fair), and that your CRC rates are very high (42% and 69% respectively). CRC errors are usually related to environmental interference factors. These factors include mainly metal, glass, water, or large amounts of people. All of these factors tend to reflect, refract, or generally damage your signal, leading to more retries, which leads to slower WiFi speeds. If you'd like to send some pictures of a couple typically placed APs with as much of the surrounding environment showing as possible, I can let you know if I see any environmental factors that may be causing issues for you.
03-05-2019 07:43 PM
03-05-2019 07:37 PM
03-05-2019 07:13 PM
It should give you a file that you would either attach to this post or email over to me. When you choose to download tech data, you should see a small new window pop up saying "Get Tech Data" and something along the lines of processing your request. Then it should give you a file with the tech data included. If that isn't working for you, could you try the CLI approach with the guide I linked?
03-05-2019 06:57 PM