Plan out the topology relationship between controllers so as to define the corresponding mobility domain.
Configuration Data | Description | Your Entry |
---|---|---|
Mobility manager information |
If more than one controller is being deployed, it is typically recommended that the inter-controller domain service be set up so as to facilitate ubiquitous roaming across the various APs on the infrastructure. Even when the domain is restricted to two controllers in an availability pair, inter-controller mobility between the two controllers should correspondingly be enabled, especially when deploying services that rely on routed topologies. A mobility domain is characterized by one of the controllers defined as the domain's manager and a set of mobility agents. The manager's role is to aggregate, consolidate and distribute the complete list of user-to-controller mapping so that any domain participant knows which controller may already own the session for a roaming user. The manager may be configured to automatically accept any membership domain requests from agents or may be configured in restricted mode so that the administrator must explicitly approve the registration of a new controller into the mobility domain.
|
|
Mobility agent information |
|