We are running M3 controllers on 5.0.4.1.
We have two local controllers where all of the APs are terminated. We installed one of them and the first round of APs. Then, when we expanded, we brought up the second local controller and added the new APs to the second one. This meant that each area of our campus has an AP from both controllers. I designed it this way (even though we have a backup controller) so that if one controller failed, there were other APs still up in the same area.
However, what this has caused is a mobility issue. When devices move between APs, our arp table on our switch network shows them getting a new IP address. This may not be every time. But, when they move around, it seems it causes the arp table to have multiple entries with different IP addresses and the same mac address.
Is there something I can do to alleviate this besides moving each area to one controller or the other? Should the clients even be getting a new IP address just for moving to a new AP?
Thanks!
Jodie