AP541 - deauthed from BSSID xx:xx:xx:xx:xx:xx reason 3

Unanswered Question
Feb 27th, 2012

Hi,

unexpectedly yesterday, none was able to connect on an AP541 (Fw 2.0.1), so the customer has made a hardware reboot by unplugging the network cable (PoE device) but all attempts to access were still logged in the syslog as "deauthed from BSSID xx:xx:xx:xx:xx:xx reason 3" until this morning when I joined the AP via ssh and I requested a reboot via software.

After boot, the problem did not appear anymore but I have not been able to identify why! Can there be any problem with the PoE and yesterday it was blocked due to a reboot of the PoE source (ASA5505)? I tried to determine what that 'reason 3' and I found a couple of threads where you had similar problems but refer to earlier versions of the firmware or other AP/Software so I was wondering if anyone can shed some light on these sudden blocks and provide some tips on checks to be made....

Thanks,

Arturo.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
emoyers Mon, 02/27/2012 - 10:43

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.

The code "deauthed from BSSID xx:xx:xx:xx:xx:xx reason 3" has no special meaning behind it other that that the client has deauthenticated from the AP541N.

It is hard to pin down a cause for issues that show up kind of haphazard. If you begin having more issues I would call in and work with one of our answering agents to further explore this issue.

Thanks

Eric Moyers

Cisco Network Support Engineer

SBSC Wireless and Surveillance SME

CCNA, CCNA-Wireless

1-866-606-1866



Arturo Bianchi Tue, 02/28/2012 - 09:34

Eric Moyers ha scritto:

The code "deauthed from BSSID xx:xx:xx:xx:xx:xx reason 3" has no special meaning behind it other that that the client has deauthenticated from the AP541N.


Hi Eric,

well, thanks for the answer!

Eric Moyers ha scritto:

It is hard to pin down a cause for issues that show up kind of haphazard. If you begin having more issues I would call in and work with one of our answering agents to further explore this issue.

I imagined that a single case was not enough, but I wanted to expose the problem, because monday morning that AP did not want to go back to work until I did a reset via software! Will agree with me that this is very strange ... previous hardware reset had not produced effects! Well, all I have noticed some other event but before the reboot was a burst of "deauthed from BSSID xx:xx:xx:xx:xx:xx reason 3" like this:

Feb 27 09:03:27 wap1 hostapd: wlan0: IEEE 802.11 STA 00:21:00:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:06:57 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:06:57 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:06:57 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:06:58 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:06:58 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:06:59 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:06:59 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:07:00 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:07:01 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:12 wap1 hostapd: wlan0: IEEE 802.11 STA 00:21:00:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:16 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:16 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:17 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:17 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:17 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:18 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:18 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:18 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:19 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:19 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:20 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Feb 27 09:08:20 wap1 hostapd: wlan0: IEEE 802.11 STA 08:11:96:XX:XX:XX deauthed from BSSID 64:ae:0c:XX:XX:XX reason 3

Well,

let's see if it was an isolated case and tied to a coincidence (maybe it was a disorder that has disappeared at the same time when I ran the reset!) and if come back again some similar event, I wish  to update the thread and / or open a support request (the equipment is under SMARTnet).

Eric,

thanks for your attention!!!

73,

Arturo.

emoyers Tue, 02/28/2012 - 10:52

That is very strange.

If it does come back please call into our Closest Support Center and one of the answering engineers can assist you with opening a ticket.

Thanks

Eric Moyers

Cisco Network Support Engineer

SBSC Wireless and Surveillance SME

CCNA, CCNA-Wireless

1-866-606-1866

Cisco Small Business Support contacts:

http://www.cisco.com/en/US/partner/support/tsd_cisco_small_business_support_center_contacts.html

nippertje Tue, 05/15/2012 - 16:04

Hi,

did you find a solution to this? I have exactly the same problem. My client phones me as says that they cannot connect in the area that is covered one AP541N. Another area covered by a different AP541N is OK. I log in and issue a reboot and its all ok again, but then the problem returns.

Today we had an engineer go to site and even though they could associate to the AP, a 7925G could not register on the voice ssid nor could he ping any hosts from a laptop on the data vlan. He powered the device off and on several times from poe source and by removing the cable, but the problem still occurred.

I have issue reboot from software so I am interested if this has fixed it, but nobody is on site.

I checked the logs and get the same' deauthed from BSSID xxxxx reason 3' over and again whilst the problem occurs.

James

Arturo Bianchi Fri, 05/18/2012 - 02:37

James Naylor ha scritto:

did you find a solution to this? I have exactly the same problem. My client phones me as says that they cannot connect in the area that is covered one AP541N.

Hi James,

no I'm sorry, I personally have not found a solution :-( In fact, the problem happened a few times and there are no wireless ip phones so the discomfort is contained. The customer did not report more events, but perhaps because he restarts the AP independently.

73,

Arturo.

Arturo Bianchi Thu, 05/31/2012 - 01:59

Hi,

Arturo Bianchi ha scritto:

The customer did not report more events, but perhaps because he restarts the AP independently.

In fact, as soon as it presents itself, away with the reboot...

DeauthenSinceReboot.png

Well, while I update the firmware to the latest version (2.0.2), but evidently there is something wrong.

73,

Arturo.

Actions

Login or Register to take actions

This Discussion

Posted February 27, 2012 at 3:52 AM
Stats:
Replies:6 Avg. Rating:
Views:4066 Votes:0
Shares:0
Tags: ap, wireless, ap541n
+

Related Content