Stadiums and Venues are expecting MAC hash topology grouping to work like NAC when multiple controllers are not in a mobility pair (basically static mac to VLAN assignments).
When roaming between two High Availability paired Wireless appliances not in a Mobility Domain, with Topology Groups created, the end client is not getting assigned to the correct Policy/Topology after the roam.
All Access Points
Firmware 10.21.xx, 10.31.xx
Topology Group Selection Algorithm MAC-Based
The current Topology Group MAC Hash algorithm will correctly place the user into the Topology determined through the algorithm.
However, there is no check to ensure that the user's previous Topology matches the new Topology after the roam.
This feature will be updated in a future release.
Delete all topologies currently configured.
Reconfigure the topologies in the same logical order so they have the same index.
One way to accomplish this is to use CLI commands:
Copy the Topology creation commands (before removing) to a Notepad or Wordpad document.
Order the Topologies as desired.
Copy the CLI commands to all sets of High Availability Paired Wireless appliances to ensure the indexing remains the same across all appliances.
The use of the Topology Groups is for networks that are not using NAC as the RADIUS server for MAC authentication. For deployments using NAC, the MAC authentication process is handled off the Wireless appliance, and the User MAC will be tagged to the correct Topology across all appliances based on a Policy Name received by the controller.