Opening this topic up for some advise, and see what others may have done.
Its good practise to building networks without large broadcast domains, so typically keeping say a /24 subnet per stack for Data and Voice. Where I'm coming unstuck is if I have a large building, with multiple stacks I wouldn't therefore wont to have the same VLAN for wireless spanned across all those switches.
I would need this though, so that any APs configured for B@AP, wireless devices keep their IP address as they roams around the campus.
The fix for this is to B@EWC, and create a topology group - which would certainly address the problem.
The conundrum I have is that when creating large networks, and large wireless networks you would need to move into bridging all traffic back to the controller which works in reverse to the contrary of what you would want to do in this situation and bridge traffic directly out of the AP.
Perhaps bridging all traffic on large to very large networks is perfectly fine, so long as you have high availability controllers and distribute the load, maybe even add further controllers in a mobility group?
So just wanted to get peoples opinion on it, and hear about what others have done on large deployments like this.
Many thanks in advance