Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Register or Sign in
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
About Bri_Bri
Community Record
13
Posts
2
Kudos
0
Solutions
Badges
To answer some of the questions that other people posted after I posted my solution, our SSIDs were configured only to accept 802.11g and later connections, meaning the minimum bitrate was 54 Mbps, not 12. It could be that setting it to 12 Mbps would work fine for us, but I haven't changed it since I set the minimum back to 11. We have no reason to forbid 802.11b devices (and no one is using one anyway) so I'm not inclined to change it. Both our router and AP are running the latest firmware and were at the time we were having a problem. The AP's channel width is set to auto. We are not using meshing.
... View more
So I think I figured out the issue: I had set up my SSIDs to only accept 802.11g connections and later. Apparently that causes a lot of devices to become sporadically unable to connect, even though they're not 802.11b devices. Once our SSIDs accepted all connections including 802.11b the issue magically disappeared. I thought I'd post about it here for posterity.
... View more
I've been looking for some kind of client-related explanation too, but as I've mentioned there's no connection or commonality among the clients this happens to. These are all devices that have no trouble connecting to other wi-fi networks. I'm starting to think our AP is defective. I'll probably contact Cisco support directly at some point in the not too distant future.
... View more
@NolanHerring I've attached two screen shots. The problem was reported to me around 16:00 on January 10, and the screen shot I took of the event log is from around that time.
... View more
After a few days of no incidents, today we had several devices suddenly become unable to see any of our SSIDs. After about half an hour one of the devices started to be able to see one of the SSIDs again, but the others still couldn't. Someone at the office rebooted both the MR53E and the MX84 and it cleared up the problem. I'm starting to get quite concerned about this. So far this equipment is working worse than the consumer grade wireless router we were using previously! Does anyone have any other ideas as to what could be going wrong? While this was happening, there were more "Failed connections" entries in the wireless health page for the MR53E: Thu Jan 10, 2019, 16:28:33 client1 Wireless Access Point SSID1 Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='0'
Thu Jan 10, 2019, 16:21:03 desktop-client2 Wireless Access Point SSID2 Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='2'
Thu Jan 10, 2019, 16:20:23 desktop-client3 Wireless Access Point SSID1 Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='0'
Thu Jan 10, 2019, 16:20:13 android-client4 Wireless Access Point SSID1 Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='0'
Thu Jan 10, 2019, 16:16:43 client5 Wireless Access Point SSID1 Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='0'
Thu Jan 10, 2019, 16:11:23 desktop-client6 Wireless Access Point SSID1 Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='0'
Thu Jan 10, 2019, 09:29:42 client5 Wireless Access Point SSID1 Association type='Association attempts' num='3' associated='true' radio='1' vap='0'
Thu Jan 10, 2019, 09:29:22 client5 Wireless Access Point SSID1 Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='0'
Thu Jan 10, 2019, 09:28:52 client5 Wireless Access Point SSID1 Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='0' (I've changed the device names, MAC addresses, and SSID names for privacy reasons.) I'm afraid I do not understand what those error entries mean, aside from there being some kind of authentication issue. Is there anything else we can do to address this?
... View more
@PhilipDAth Another bit of info: the two devices that couldn't connect at all were a cheap $40 Android prepaid phone and an old iPod Touch 3. When I created an SSID that used either no encryption or WEP they were both able to connect to that, so I'm guessing that they don't use a modern enough version of WPA2 to be able to connect to our other SSIDs. Does that sound right? (For those that might be concerned about the security of my wireless network, don't worry, I'm not going to keep an unencrypted or WEP SSID up. That was just for testing.)
... View more
On the MR53E it says it's firmware is up-to-date, version MR 25.13. The MX84 has a firmware update available that I haven't installed yet. There are no other APs running in this office. However we used to have a consumer grade AP (not sure what model) that was providing a Wi-Fi network using the same SSID as the MR53E is now. I've since created a few other SSIDs on the MR53E just in case that was causing issues, but on any device that experiences this problem, all of the SSIDs provided by the MR53E disappear, not just the one that used to come from the older AP.
... View more
@PhilipDAth I don't believe we're using a RADIUS server or WPA2 Enterprise. We've just got the SSIDs association requirements set to "Pre-shared key with WPA2".
... View more
@PhilipDAth The issue is that a single client won't be able to connect (temporarily) but the others still can. Wireless Health does mention some connection failures. I'm not sure how to interpret the logs, though. Most of them seem to be Association and Authentication failures. here's a small selection of them: Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='1' Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='3' Association type='Association attempts' num='3' associated='false' radio='1' vap='3' Authentication type='WPA-PSK auth fail' associated='false' radio='1' vap='2' Association type='Association attempts' num='4' associated='false' radio='1' vap='2'
... View more
@NolanHerring to answer your questions: The MR53E is connected directly to a port on the MX84. I'll check the logs about port flapping when I have the chance, but that's probably not it since when this problem occurs it only affects one device at a time rather than all of them. The antenna are Cisco brand dipole Antenna (MA-ANT-3-B6). I believe the AP is in a good location. All the devices report strong to very strong signal strength. I don't believe any of the devices that can't connect are 802.11b only. Not sure about DFS -- will look into that. I haven't had a chance to really dig into the AP logs so far, but I agree that's a good place to look for issues. Thanks for all the suggestions so far.
... View more
I'm trying to help administrate an office that has a single MR53E in it providing its Wi-Fi network. The various SSIDs use WPA2, are dual band 2.4 / 5 GHz, are setup to allow 802.11g connections or later, and are configured to be in bridge mode so that our MX84 can manage the network. Most of the time client devices are able to connect to this network without issue. However, every now and then a client will lose their connectivity, and when checking available Wi-Fi networks will see that our Wi-Fi network is not available. Then some minutes later it will come back and their device will reconnect. There doesn't seem to be any rhyme or reason as to which devices experience this problem: it has happened to smart phones of various makes and models as well as several different laptops. I've also found no pattern as to when it happens -- it seems to be fairly random. There is also a few devices that cannot see the Wi-Fi network at all. I'm fairly certain that these devices possess the necessary capabilities to connect to our network (802.11g or newer, WPA2, etc.) and yet they can't connect. While there are a lot of competing Wi-Fi networks in the area, the MR53E is set to automatically select a channel to avoid interference so I'm not sure what I can do there to improve things. In case it's a clue, whenever I turn Wi-Fi off and back on again on any of my devices, these other Wi-Fi networks are displayed almost immediately, while the ones created by our MR53E take 5-10 seconds to show up. I'm quite new to all of this so I'm not sure what I should do to try and get to the bottom of this issue. Any suggestions would be much appreciated!
... View more
Jan 6 2019
8:55 AM
Is there a particular reason I should disable "Load balancing"? I'd prefer to keep it on if possible.
... View more
Jan 6 2019
6:29 AM
I'm helping to set up a network using an MX84 and an MR53E. We have two internet connections -- WAN1 and WAN2 -- and I'd like to set up the network to use load balancing. Further I'd like there to be one subnet so that all clients are able to communicate with each other over the local network. However WAN1 has a static IP address, and sometimes clients need to use it specifically to connect to sites that have the static IP whitelisted. So what I need is either a) a way of setting things up so that all traffic for specific websites is routed through WAN1, or b) a way for a client to be able to manually opt in to using only WAN1 when connecting to these sites and then be able to opt out of that once they're done so that their traffic is load balanced again. The first thing I tried was creating a second Wi-Fi SSID with the MR53E and then setting it up so that all traffic on it goes to WAN2. However, I wasn't able to figure out how to do that without having both SSIDs using a different VLAN which prevents clients on different VLANs from being able to communicate with each other locally. I also tried adding a "Flow preferences" in the "SD-WAN & traffic shaping" section of the MX84's configuration so that traffic of any protocol, coming from any IP address, and with a destination IP address of particular website would go through WAN1. However I have not been able to get it to work -- traffic will continue to sometimes go through WAN2. Is there any way for me to accomplish what I'm after? I'll mention that I'm relatively new to networking situations like this so there may be something basic I'm not understanding.
... View more
My Top Kudoed Posts
| Subject | Kudos | Views |
|---|---|---|
| 2 | 36002 |
© 2024 Cisco Systems, Inc.
