WAP4410N stops accepting wireless clients

scornelissenQ85 · ‎09-26-2011

I have two WAP4410N. One of he accesspoints is connected to our wired LAN, called by now AP1. The other accesspoint is connected to the first accesspoint by WDS (Client mode) called now by AP2. I have upgraded both accesspoints to firmware 2.0.4.2. Both accesspoints are set to the same SSID and channel (6) and are set to mixed mode (B/G/N). After I two weeks they started to fail. When I connect to AP1 I don't reveive an IP-address of our DHCP server from our LAN. I'm able to connect to AP1 from our LAN. When I SSH to the box and I do an dmesg command, I see the following messages:

ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)

...

ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)

I'm still testing these devices and I hope I can use these devices in our production environment,which is not possible with these errors and outages.

I can't connect to AP2 right now. I think the whole wireless interface isn't working anymore, unless I power off/power on the box. But it's hard testing when it works ok for two weeks and then stops.

Message was edited by: Sander Cornelissen

Eric Moyers · ‎09-30-2011

Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center. Thank you for using the Cisco Community Post Forums.

When you upgraded both of the APs, did you do a factory reset of the unit. If not please reset the unit back to factory defaults. Then manually reconfigure the unit not copy the config file back in.

Sometimes we have found with some devices and firmware that the configuration backup will keep some of the old code with it. Manually reconfiguring the unit will assure that we are totally using the newer fw.

Please let us know if you continue to have issues.

Thanks
Eric Moyers
Cisco Network Support Engineer
CCNA, CCNA-Wireless
1-866-606-1866

scornelissenQ85 · ‎10-21-2011

After your advice I did a factory reset of both AP's. From 17 october until today it worked fine. Today it crashed and the connection to the device isn't usable.

In the dmesg, from the SSH console to the AP, I did notice the following text:

ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)

Going to erase from sector 00000085 to 00000086..

erasing bf7e0000...

ath_bstuck_tasklet: stuck beacon; resetting (bmiss count 36)

I have to power off and power on again to make the device work.

Miguel Angel Tejo · ‎06-05-2014

I have the same problem, the only solution is reboot.

I did factory defaults but the problem still persists.

My APs are running release 2.0.7.4 and I have to reboot them every 2/3 weeks.

Please, are the any solution?

Thanks!!

Eric Moyers · ‎06-09-2014

Please call in and open a case. There is some information the engineer will have to collect and then they should be able to assist with getting this resolved.

Eric Moyers

scornelissenQ85 · ‎12-06-2011

Can we return the device? It's not working as it should be. It's give troubles as our production network was being flood while one of the accesspoints was connected to our LAN. Both other accesspoints were connected to each other with WDS. These devices won't work reliable. Is there a replacement alternative?