CISCO WAP571 dropping clients.

[jasons6930]

Hi guys,

Just realised i might have posted in the wrong forum so i've posted here as the other will probably get deleted.

Noticed recently that our WAP571 keeps deauth ing clients for some reason.

One of the problems is our Sky Q box keeps failing due to connectivity problems, and whilst looking at the logs, most of the clients are doing the same and then joining again.

These clients are within a few meters of the AP.

Part of log attached.

Any help much appreciated.


Apr 3 2019 20:16:24 info dman[1339] The AP startup configuration was updated successfully.
Apr 3 2019 20:10:54 debug hostapd[2287] station: fe:f6:6d:21:06:df deauthenticated
Apr 3 2019 20:10:54 info hostapd[2287] STA fe:f6:6d:21:06:df disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:10:54 debug hostapd[2287] station: fe:f6:6d:21:06:df deauthenticated
Apr 3 2019 20:10:54 info hostapd[2287] STA fe:f6:6d:21:06:df deauthed from BSSID 70:d3:79:93:c6:10 reason 4: Disassociated due to inactivity
Apr 3 2019 20:10:28 debug hostapd[2287] station: 0e:fc:e0:5a:d8:02 deauthenticated
Apr 3 2019 20:10:28 info hostapd[2287] STA 0e:fc:e0:5a:d8:02 disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:10:28 debug hostapd[2287] station: 0e:fc:e0:5a:d8:02 deauthenticated
Apr 3 2019 20:10:28 info hostapd[2287] STA 0e:fc:e0:5a:d8:02 deauthed from BSSID 70:d3:79:93:c6:10 reason 4: Disassociated due to inactivity
Apr 3 2019 20:09:57 info hostapd[2287] STA 78:3e:53:72:80:9e associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:09:57 info hostapd[2287] Assoc request from 78:3e:53:72:80:9e BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:09:57 debug hostapd[2287] station: 78:3e:53:72:80:9e deauthenticated
Apr 3 2019 20:09:57 info hostapd[2287] STA 78:3e:53:72:80:9e deauthed from BSSID 70:d3:79:93:c6:10 reason 3: STA is leaving IBSS or ESS
Apr 3 2019 20:09:56 debug hostapd[2287] station: 78:3e:53:72:80:9e deauthenticated
Apr 3 2019 20:09:56 info hostapd[2287] STA 78:3e:53:72:80:9e disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:09:56 debug hostapd[2287] station: 78:3e:53:72:80:9e deauthenticated
Apr 3 2019 20:09:56 info hostapd[2287] STA 78:3e:53:72:80:9e disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:09:18 debug hostapd[2287] station: 0c:f9:c0:b5:d8:06 deauthenticated
Apr 3 2019 20:09:18 info hostapd[2287] STA 0c:f9:c0:b5:d8:06 disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:09:18 debug hostapd[2287] station: 0c:f9:c0:b5:d8:06 deauthenticated
Apr 3 2019 20:09:18 info hostapd[2287] STA 0c:f9:c0:b5:d8:06 disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:08:10 info hostapd[2287] STA 0e:fc:e0:5a:d8:02 associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:08:10 info hostapd[2287] Assoc request from 0e:fc:e0:5a:d8:02 BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:07:41 info hostapd[2287] STA 0c:f9:c0:b5:d8:06 associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:07:41 info hostapd[2287] Assoc request from 0c:f9:c0:b5:d8:06 BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:07:19 info hostapd[2287] STA d4:a3:3d:b5:eb:04 associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:07:19 info hostapd[2287] Assoc request from d4:a3:3d:b5:eb:04 BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:06:52 debug hostapd[2287] station: 7e:32:2b:2b:c9:45 deauthenticated
Apr 3 2019 20:06:52 info hostapd[2287] STA 7e:32:2b:2b:c9:45 disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:06:52 debug hostapd[2287] station: 7e:32:2b:2b:c9:45 deauthenticated
Apr 3 2019 20:06:52 info hostapd[2287] STA 7e:32:2b:2b:c9:45 deauthed from BSSID 70:d3:79:93:c6:10 reason 4: Disassociated due to inactivity
Apr 3 2019 20:05:42 info hostapd[2287] STA fe:f6:6d:21:06:df associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:05:42 info hostapd[2287] Assoc request from fe:f6:6d:21:06:df BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:05:42 info hostapd[2287] STA 7e:32:2b:2b:c9:45 associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:05:42 info hostapd[2287] Assoc request from 7e:32:2b:2b:c9:45 BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:05:42 debug hostapd[2287] station: 7e:32:2b:2b:c9:45 deauthenticated
Apr 3 2019 20:05:42 info hostapd[2287] STA 7e:32:2b:2b:c9:45 disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:05:42 debug hostapd[2287] station: 7e:32:2b:2b:c9:45 deauthenticated
Apr 3 2019 20:05:42 info hostapd[2287] STA 7e:32:2b:2b:c9:45 deauthed from BSSID 70:d3:79:93:c6:10 reason 3: STA is leaving IBSS or ESS
Apr 3 2019 20:05:41 info hostapd[2287] STA 7e:32:2b:2b:c9:45 associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:05:41 info hostapd[2287] Assoc request from 7e:32:2b:2b:c9:45 BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:05:38 info hostapd[2287] STA 78:3e:53:72:80:9e associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:05:38 info hostapd[2287] Assoc request from 78:3e:53:72:80:9e BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:05:38 err hostapd[2287] trying to deauthenticate to station 78:3e:53:72:80:9e, but not authenticated
Apr 3 2019 20:05:38 err hostapd[2287] trying to update accounting statistics, station 78:3e:53:72:80:9e not found
Apr 3 2019 20:05:38 info hostapd[2287] STA 78:3e:53:72:80:9e deauthed from BSSID 70:d3:79:93:c6:10 reason 3: STA is leaving IBSS or ESS
Apr 3 2019 20:05:18 debug hostapd[2287] station: 78:3e:53:72:80:9e deauthenticated
Apr 3 2019 20:05:18 info hostapd[2287] STA 78:3e:53:72:80:9e disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:05:18 debug hostapd[2287] station: 78:3e:53:72:80:9e deauthenticated
Apr 3 2019 20:05:18 info hostapd[2287] STA 78:3e:53:72:80:9e disassociated from BSSID 70:d3:79:93:c6:10 reason 8: Sending STA is leaving BSS
Apr 3 2019 20:05:18 info hostapd[2287] STA 78:3e:53:72:80:9e associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:05:18 info hostapd[2287] Assoc request from 78:3e:53:72:80:9e BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:05:18 err hostapd[2287] trying to deauthenticate to station 78:3e:53:72:80:9e, but not authenticated
Apr 3 2019 20:05:18 err hostapd[2287] trying to update accounting statistics, station 78:3e:53:72:80:9e not found
Apr 3 2019 20:05:18 info hostapd[2287] STA 78:3e:53:72:80:9e deauthed from BSSID 70:d3:79:93:c6:10 reason 3: STA is leaving IBSS or ESS
Apr 3 2019 20:05:13 info hostapd[2287] STA 7c:64:56:56:c9:45 associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:05:13 info hostapd[2287] Assoc request from 7c:64:56:56:c9:45 BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:05:12 info hostapd[2287] STA 18:b4:30:2b:a9:54 associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:05:12 info hostapd[2287] Assoc request from 18:b4:30:2b:a9:54 BSSID 70:d3:79:93:c6:10 SSID Cisco
Apr 3 2019 20:05:11 info hostapd[2287] STA 4c:32:75:63:bf:9d associated with BSSID 70:d3:79:93:c6:10
Apr 3 2019 20:05:11 info hostapd[2287] Assoc request from 4c:32:75:63:bf:9d BSSID 70:d3:79:93:c6:10 SSID Cisco

 

[CrystalLattice]

why do people post twice?

 

[jasons6930]

Because it states that where i posted originally (in the wrong forum), it would be deleted as it doesn't relate to any articles being discussed.

 

[L&LD]

Because it states that where i posted originally (in the wrong forum), it would be deleted as it doesn't relate to any articles being discussed.

Actually, you should have asked an admin to move it to the right forum instead.

 

[coxhaus]

The best place to post would be in the Cisco small business forums. Cisco will help you there.

It looks like it is dropping due to inactivity. I assume you are running the latest firmware. Are you running in a cluster or standalone? What model do you have? You can not mix models in a cluster. Are you in the US or Europe?

What is a Sky Q box?

 

[coxhaus]

Is this the active thread for this? I don't see a thread on Cisco's small business site.

Maybe he figured it out and wasn't a problem after all.

 

[sfx2000]

Just realised i might have posted in the wrong forum so i've posted here as the other will probably get deleted.

Noticed recently that our WAP571 keeps deauth ing clients for some reason.

One of the problems is our Sky Q box keeps failing due to connectivity problems, and whilst looking at the logs, most of the clients are doing the same and then joining again.

These clients are within a few meters of the AP.

Sounds like it's load shedding... cap'ed out due to current settings in the WAP.

 

[coxhaus]

I looked back on his posts and he seems to be having modem/router disconnects. Maybe this could be effecting his wireless.

 

[sfx2000]

I looked back on his posts and he seems to be having modem/router disconnects. Maybe this could be effecting his wireless.

In the WLC, one can set a cap limit, that's why I was suggesting load shedding, so if the cap limit is low...

 

[sfx2000]

The other would be...

perhaps just normal - clients are going to try to associate, but if credentials are wrong, they're going to be kicked out...

If one is running a WLC managing multiple AP's with WPA2-PSK, make sure things are pushed out, if WPA/WPA2-enterprise, look at performance issues with the Auth Center/Radius Server...

 

[jasons6930]

Hi guys,

Thanks.

Only running one AP at the moment and no WLC involved.

I have rebooted the WAP, but this has made no difference.

To be honest, the only things i have done since getting it, is set up the networks with network name and password, with WPA Personal / WPA2 AES security and updated the firmware.

Just noticed the broadcast key refresh rate is set at 86400.

Should i reduce this?

 

[jasons6930]

As an experiment, i set up the other AP.

Working as stand alone units, one is set up for 2.4g only, and the other 5g.

I have setup up a different SSID on each and using a selection of clients across each.

Both have the same settings, and both are exhibiting the same behaviour with clients.

Would it be worth rolling back to the previous f/w that is stored on each ap?

Thanks.

 

[L&LD]

As an experiment, i set up the other AP.

Working as stand alone units, one is set up for 2.4g only, and the other 5g.

I have setup up a different SSID on each and using a selection of clients across each.

Both have the same settings, and both are exhibiting the same behaviour with clients.

Would it be worth rolling back to the previous f/w that is stored on each ap?

Thanks.

There is no previous firmware stored on the AP's. The firmware that is now installed is what you have.

If you haven't haven't done it already, or previously, you may want to perform an M&M Config on your network equipment. That should at least get you to a good/known state and proper troubleshooting can begin then.

Please see the links in my signature below for further details. Each step may not be directly applicable to your situation, but if you can follow the overview of what is suggested, you should be able to get to that good/known state with your equipment too.

 

[jasons6930]

Ah ok.

It was only what was shown in the manage firmware section, i assumed it held onto the previous version for problem solving etc.

 

[jasons6930]

not sure what happened with the image...

https://thumbsnap.com/0DpCnERJ

 

[jasons6930]

ok, as a quick update, i rebooted to factory default on the AP that was running 5ghz network, and so far seems to have settled down.

I can't do anything with the AP on 2.4 as i have a number of clients actively using it.

I should be able to try this evening.

 

[L&LD]

not sure what happened with the image...

https://thumbsnap.com/0DpCnERJ

You seem to have the capabilities on your hardware to have two firmware versions available (one being active). And, it also seems like you were using (maybe still are?) the older version.

I would 'switch' to the newer firmware and leave the old one there as a backup. But, since you're at this point, continue on with your testing and see if this gives you as good results too.

 

[coxhaus]

When you load a new firmware version on a Cisco product it does not become active. You have to turn it on. This allows you to schedule a whole network of devices at the same time. The PRO gear is the same way.

Are you using a radius server?

Are you in Europe? You are running a European version.

 

[jasons6930]

Hi guys,

Yes, in the UK.

The picture was taken after i swapped back to the original firmware that was shipped installed on the WAP.

And no, no radius server.

Came back a while ago and my phone would not connect for some reason.

I went into the security settings and disabled MFP as it was set by default as 'capable' and i read on the Cisco forum somewhere about setting it to 'not required'.

Also, i cleared the log after that and so far, over the last 40 minutes or so, it has been completely clear.

(Yes, i had been having severe internet disconnections which are (hopefully!) now resolved.

 

[coxhaus]

I was looking in my 3 WAP371 wireless APs and I am not sure what MFP is? What is it? I see nothing under security.