Had seen this once, so asumed it may have been a client issue so left the PC guys looking at it, however, Ive now seen this on 2 other occasions.
The SSID is broadcast out of all groups across site, the client seems to connect fine apart from in one area. The AP is in the same group as others that the client will connect to fine. So if the device goes to an adjacent area, it will connect, return it to the problematic area, it wont connect. My laptop connects to the AP and SSID fine, but this other device wont.
The only thing that I can think of that may be a link or just conincidence, is that these APs were converted 315 IAPs. The recent batch of 315's we have received have all been instants, unlitke the previuos 100+ we had. But having said that, the AP is in a main group with other APs that doent seem to have issues.
So far this problem is apparant in two seperate areas on site across APs in two different groups. But seems very localised to certain APs.
We have 7220 controllers, running 220.127.116.11 code.
Does anything obvious spring to mind, before I start looking at AP/Cleint debug logs? Any commands in particular I should be looking at, as not overly familiar with debugging.
Make sure the client VLAN is trunked to that IAP with the problem.
ts no longer an IAP, its been converted into a controller managed AP that is in a group with APs without issues.
Per my experience, the first thing is to make sure all vlans work fine if you are using vlan pool. Second you could check the channels of those APs which are located in the problem area. And then the last thing you could do is reboot those problem APs. I met such issue several times and rebooting could fixed the problem.
Thanks for all of your advice...
We think the cause may have been down to another vendors wifi within the same area. Unfortunatley, in some areas we have another wifi network, and once I got them to turn their wifi off, the devices connected!
This then brings me to similar issues in another department, who on the floor above and below have both ours and another suppliers wifi, so essentially 3 different wifi networks. Above and below are Open networks, and I have real difficulty connecting to any of our ssid's, but can connect to theirs fine.
Other than this connectivity issues, what would be the best logs to look at to prove that the presence of these other wifi networks is the cause of our issues?
@$k3l3t0r wrote: Other than this connectivity issues, what would be the best logs to look at to prove that the presence of these other wifi networks is the cause of our issues?
Packet capture(s) on the channel(s) being used by your AP so that you can see exactly what is happening during the association attempt.
We had aruba TAC look at this and they concluded it to be down to an AOS bug, so we upgraded to 18.104.22.168 which resolved all of the connectivity issues!
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.