@charliepdean wrote:
Thanks for the answer. So it sounds like I don't want to see that message. This makes me think what I have configured is not ideal or correct. I don't have preserve VLAN checked but I do have VLAN mobility checked. Preserve VLAN is used with VLAN pooling correct?
The architecture I have is a two controller cluster stretched between two datacenters ( > 5 ms latency) with two VLANs for a single SSID. Datacenter 1 has VLAN 1 with the router as the HSRP primary and dataventer 2 has VLAN 2 with that router as the HSRP primary. The VAP profile VLAN is configured on each controller to reflect the primary VLAN in that datacenter. I've attached a diagram of what I'm trying to describe.
Is this a bad design or will not work with how I have it configured?
You could also possibly get that message if a device leaves one WLAN and attaches to another and is still in the switching table.
You should not stretch a cluster between datacenters. Clusters expect to be physically close to each other, have little latency and never expects to be split apart. If your datacenters lose connectivity between each other sporadically, you could have an issue that you cannot diagnose easily.
- Controllers do not fail often
- Establishing a cluster is supposed to be the redundancy you need with stateless failover
- Putting controllers in a cluster in separate datacenters is a recipe for uncontrollable issues, if there is a chance that those datacenters get disconnected. If you insist on having a separate datacenter, it should be a backup LMS cluster to an existing cluster so that everything is exactly where you expect it to be if there is an outage that separates datacenters.