WAP561 - After 2-3 days the AP will not allow clients to fully authenticate (628911547)
Have a total of 5 APs and every 2-3 days these devices seem to not allow clients to connect. Clients appear to associate but never authenticate. I have opened a case with Cisco (Case number in title) but want to see if anyone else is having this issue and how you may have resolved this.
I received an email from an engineer and one of the options he asked me to change was not even an option on the screen. I have UNTAGGED VLAN selected however MANAGEMENT VLAN is not an option. Below is his email.
Making a bit of reasearch i discovered that maybe you have fallen into a firmware bug.
It should be related to VLAN.
If you go on VLAn and IPv4 setting you should see somewhere the MANAGEMENT VLAN and UNTAGGED VLAN settings.
Both of them should be ENABLED.
On the next fw release this should be fixed because it’s normal to have both disabled, but just to workaround the problem you could try with this settings enabled and see if the “freeze” is not happening again.
Please update me so i can close this case or go on with the process.
I have tried all of the setting changes you have recommended but nothing is doing the trick in this case. I have 3 access points and all 3 access points are having the exact same issue as what is described in this article.
I can add that if you change any setting and receive the pop up message stating that you may be disconnected from the access point during the setting change process. Then when the access point comes back up you are able to connect with no problem.
So it adds a layer of difficulty when making these changes as each setting change will immediately allow you to connect to the internet and no longer be "not authenticated" or on an "unidentified network"
Is there any real fix from Cisco regarding the issue with these access points?
With the latest release of firmware for the WAP 561, 551, 371, 351 a new
feature was added that would allow customers to upgrade the firmware for
their clustered access points from the main access point.The basic steps
to accomplish this is:1) Download th...
Special thanks to Alex McDonald for sharing his favorite tip:My favorite
tip is the ‘write default’ command on autonomous wireless access points,
it simplifies manual conversion of a WAP with a static ip address to a
LAP with a DHCP address.This saved a l...