02-18-2019 03:42 AM - edited 07-05-2021 09:53 AM
Hi,
I was wondering if anyone had encountered any problems with Cisco 18xx series access points dropping wireless clients unexpectedly?
The background is that I wanted to move away from a Ubiquiti Wireless setup at home and head back to a Cisco based wireless system - mainly as we use these things at work and gaining a bit more familiarity with them couldn't hurt. I went for a AIR-AP1815i-x-K9C (the Mobility Express bundle) and having upgraded to the latest software (8.8), things seemed to be working fine in most cases. However, I have a bunch of wireless plugs (TuyaSmart) which allow lamps and things to be turned on and off remotely, drop off after about 12 hours. Admittedly, these aren't the most expensive things in the world but they have been 100% reliable on the old Ubiquiti setup. They operate at 2.4Ghz only.
I'm finding on the 1815i, these devices are dropping off the wireless and I can't see any obvious reason why. They all go at the same time and the only way to get them back is to reboot the AP. I apperciate I need to delve into the controller logs (which I haven't had time to do yet) but wondered if anyone else had experienced similar problems or knew of any settings/bugs that might be causing this? I'm confident the problem is related to the new Cisco AP - given the reboot brings things back and the reliable history with the old setup.
Any ideas and thoughts welcome!
Thanks
Solved! Go to Solution.
03-11-2019 04:34 AM
So after bashing my head against a brick wall with this for ages, I finally lost my mind when I rebooted the AP running ME and it went into a reboot loop with "waiting for preferred uplink" messages. I tore my router's ZBF policies to pieces to make sure that there weren't any issues there but that was all good so it had to be something to do with Mobility Express or the AP.
As a final "hail Mary", I factory reset the AP running ME and ran through the setup again. This time, everything worked immediately and I've had no issues with DHCP since.
I can only assume that having received the AP running 8.4 out of the box, applying some config and upgrading to 8.8.111.0 - some legacy config not compatible with 8.8 caused problems. I guess in future I should read the upgrade steps before proceeding! =)
Either way, the problem appears to have been resolved and I'm now a lot more comfortable with the 18xx series.
Thanks to all who took time out to pose thoughts and ideas, your input was very much appreciated.
02-18-2019 04:08 AM
02-18-2019 04:14 AM
02-18-2019 07:15 AM
02-18-2019 07:31 AM
02-18-2019 07:52 AM
02-18-2019 10:21 AM
OK - I think I've resolved this and it comes down to DHCP and probably a misunderstanding on how this is supposed to work. I assumed that DHCP requests would be passed out into the wider VLAN and the router which is responsible for DHCP would respond. When I configured a DHCP pool on Mobility Express, the devices that were missing immediately came online so my guess is that they were working until the lease issued to them by the old wireless system expired.
I'm happy to use Mobility Express as a DHCP server but I'm interested to know if there is a way to bypass this and go back to using the scope already defined on the router instead?
02-18-2019 02:22 PM
you could use DHCP Proxy to send the DHCP requests to the routers DHCP server.
02-19-2019 12:36 AM
Normally you don't configure a DHCP server on the ME at all. Then the DHCP packets from your clients will be broadcasted automatically into the VLAN the WLAN is assigned to.
There are also some advanced features, which might be hidden in the default GUI (I haven't an ME here to test atm).
In the case of a WLC based Wi-Fi, if you have DHCP Proxy enabled, you also need to configure the DHCP Server IP Address on the virtual interface.
You find some commands for this here:
03-11-2019 04:34 AM
So after bashing my head against a brick wall with this for ages, I finally lost my mind when I rebooted the AP running ME and it went into a reboot loop with "waiting for preferred uplink" messages. I tore my router's ZBF policies to pieces to make sure that there weren't any issues there but that was all good so it had to be something to do with Mobility Express or the AP.
As a final "hail Mary", I factory reset the AP running ME and ran through the setup again. This time, everything worked immediately and I've had no issues with DHCP since.
I can only assume that having received the AP running 8.4 out of the box, applying some config and upgrading to 8.8.111.0 - some legacy config not compatible with 8.8 caused problems. I guess in future I should read the upgrade steps before proceeding! =)
Either way, the problem appears to have been resolved and I'm now a lot more comfortable with the 18xx series.
Thanks to all who took time out to pose thoughts and ideas, your input was very much appreciated.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide