How to troubleshoot network backend with Aerohive. Should clients be authenticating on the AP or the hivemanager cloud with a simple WPA2-PSK SSID?

[matt_nissen]

I am going crazy trying to troubleshoot a problem we have at our site with Hivemanager cloud and about 20 AP250's..... it all started in our warehouse/production area and Intermec scan guns.

I have taken over the wireless since our network guy has not been replaced and what i have found out from our production/warehouse users is that the wireless never worked - constant dropouts and no roaming ever happening.

After some research i have found configurations perfect for our site. The result is that 3 out of 4 of our SSID clients have much faster connections and no roaming issues.

The SSID for our production scan guns is still having issues roaming. there are specific spots but i have found most the time, they seem to struggle with Authentication response time.

I'm trying to figure out where they authenticate from, the AP itself or the hivemanager cloud....

Radius is configured onsite so our corporate ssid works fine... i added our DNS server so the response is fine...but Gateway ARP and authentication seems to really take a long time.

Any suggestions would be great!

[samantha_lynn]

Thank you for letting me know. Would you be able to run a remote sniffer packet capture? I'd like to get a better look at the traffic this AP is seeing. This guide walks through how to set up a remote sniffer packet capture, for reference: https://thehivecommunity.aerohive.com/s/article/Packet-Capture-in-NG

[matt_nissen]

​its wifi1? everything i'm testing is on wifi0.....

[matt_nissen]

​here is the picture...as you can see...brick walls everywhere.... and big metal racks.... but just inside that room it takes forever to re-associate .

About 12 other AP's in production are surrounded by brick walls and metal cages and everything works fine in there...its this one AP.

[samantha_lynn]

Sure thing:

Setting the power to 2 might help if the issue is overlapping signals, but I took a look at your neighboring devices and none of them seem to be overlapping significantly.

You are getting background scans through, so we can be sure the data we're looking at is current.

I checked your client devices signal strength and they all had good signals, so that's good news.

Your wifi0 retry rate is a bit above where we'd like to see it (anything below 10% is fine, anything above that might be an issue, and the AP had around a 19% retry rate, which again means that 19% of the traffic is damaged and had to be resent), but not nearly as bad as the wifi1 CRC failure rate.

It would make sense that swapping the AP out with a different one didn't help if the issue is environmental, so we're back to those pictures to rule out environmental issues.

Your CPU looks good, the airtime percentages look balanced, and we aren't flooding the AP with traffic (you're getting about 18 packets per second and we don't typically see problems until we reach 30 packets per second or more, so that all looks good).

I checked your buffered log but most of it is about the interference alerts that 71% CRC failure rate is going to be causing, so I think that is where we need to focus at the moment.

[matt_nissen]

​I will provide you a picture, no problem....but...is there anything else you can look at that might tell us something else?

should I try setting the transmission to 2?