I'm testing out Cisco's Mobility Express on a 3802i and am running into "gotcha" moments that I wasn't expecting. I'm hoping some of you more experienced people on here can help guide me through and find solutions if they exist.
Goal: I'm considering replacing my WLC5508 with a 3802i running ME.
To start... getting MGMT up and running on a trunk port was fun (has to be native vlan). Not to mention you need DHCP enabled on mgmt so the underlying AP can actually join and the system to not just sit still.
I now have the 3802i up and running and have a couple AP's joined to it (few hours spent before I realized I have to configure a TFTP server on ME that has the software the slave AP's require).
I created vlan 2074 and trunked it to the ME AP, created a WLAN on that VLAN and everything worked.
Disabled the radios on the ME AP to see if I could connect through the Slave AP. But it looks like the slave doesn't send the traffic back through the CAPWAP tunnel to the Master as it does in the WLC. Is that something that's configurable or am I stuck trunking the vlan's to every AP I have configured (administration overhead).
That's as far as I've gotten so far, if anyone else has tips or tricks that might help me along the way, please let me know.
You do not mention how many and which APs you have. But I would not move from a legacy controller to a system that could also already be named legacy (Mobility Express).
I would look into two primary solutions (assuming your wireless deployment is not that big):
In both cases, the way you work with the WLAN will change as the configuration is very different. But these are the actual systems from Cisco.
Mobility Express uses FlexConnect Local Switching. You will need trunk on all APs to be able to place the clients on their correct VLANs.
The Master AP does not have the hardware needed to handle centralized traffic.
If that such a problem, just go with a 5508 WLC.