Mobility, or roaming, is the ability of a wireless client to maintain its association seamlessly, from one access point to another, securely and with as little latency as possible.

With converged access, data traffic generated by wireless endpoints can be controlled and optimized at the network edge (based on networking and security policies), instead of having to go through a central wireless controller or switch first.

The following mobility components constitute the primary components of the converged access mode:

Mobility Agent is a function to manage a wireless client database that includes client association or authentication status. Each device switch stack produces one mobility agent that can manage up to 50 access points and up to 2000 wireless clients. The mobility agent is also responsible for providing access point connectivity and CAPWAP termination.

Mobility Controller provides mobility management tasks including inter-switch peer group roaming, RRM, and guest access. One mobility controller is required for each mobility subdomain. Your device can serve as a mobility controller for small to medium-sized deployments.

1. In the Global Configuration tab, enter a name for the mobility group.
2. Enter the multicast IPv4 and IPv6 address for the mobility group.
3. In the Keep Alive Interval field, specify the number of times a ping request is sent to a mobility list member before the member is considered to be unreachable. The valid range is 3 to 20, and the default value is 3.
4. Specify the Mobility Keep Alive Count amount of time (in seconds) between each ping request sent to a mobility list member. The valid range is 1 to 30 seconds.
5. Enter the DSCP value for the mobility group.
6. Specify the mobility MAC address.
7. Click Apply.

1. In the Mobility Peer Configuration section in the Peer Configuration tab, click Add.
2. In the Add Mobility Peer window that is displayed, enter the IP address for the mobility peer.
3. Additionally, when NAT is used, enter the optional public IP address to enter the mobility peer's NATed address. When NAT is not used, the public IP address is not used and the device displays the mobility peer's direct IP address.
4. Enter the mobility group to which you want to add the mobility peer.
5. Select the required status for Data Link Encryption.
6. Specify the SSC Hash as required.
7. Click Apply to Device.
8. In the Non-Local Mobility Group Multicast Configuration section, click Add.
9. Enter the mobility group name.
10. Enter the multicast IPv4 and IPv6 address for the mobility group.
11. Click Save.