Mobility Configuring on WLC

In this post we will learn how to configure WLC mobility on Cisco Controllers.

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

More Info about Mobility/Roamin please visit This Section : Mobility Basics

A mobility group is a set of controllers, identified by the same mobility group name that make seamless roaming for wireless clients. By creating a mobility group, we can enable multiple controllers in a network to dynamically share information and forward data traffic when inter-controller or inter-subnet roaming occurs. Controllers in the same mobility group can share the context and state of client devices as well as their list of access points so that they do not consider each other’s access points as rogue devices.

First of All we need to configure Mobility Group name on each controller while setting up (Initial Config) the controller.

Virtual Gateway IP Address:
Multicast IP Address: / 3
Mobility/RF Group Name: Test
Network Name (SSID): Test

Via GUI:

To add an entry to a controller mobility configuration using the GUI, go to CONTROLLER > Mobility Management > Mobility Groups and click on New.



Here we enter the MAC address and IP address of the controller management interface we are adding along with the mobility group name of that controller.

In WLC1 we will add WLC2 mac and IP address.
In WLC2 we will add WLC1 mac and IP address.

Here I will posts the screenshot from WLC1, we also need to add same in WLC2.



Once we add the WLC MAC & management interface IP address the status will shows us as UP (Be aware sometime it take 20-30 seconds):



Note: For controllers to be in the same mobility group, they need to meet the following criteria:

Identical mobility group names: The mobility group name is case sensitive. A mobility group name of ABC is not the same as abc from the controller perspective.

Same virtual interface IP address: If the virtual IPs are not the same between the controllers, the handoff of the client database entry will not take place and the client will be disconnected for a short period.

Same version of code: This is true for supporting normal client mobility. Starting with the 5.2 release, a 5.2 or 6.0 controller supports auto-anchoring with 4.2 and higher code running on the anchor controller.

Network connectivity between the controller in the mobility group: We should be able to mping and eping between the controllers. These special pings will be discussed in other post.

Remembering points in brief before configuring Mobility:

  • IP connectivity must exist between the management interfaces of all controllers.
  • All controllers must be configured with the same mobility group name.
  • All controllers must be configured with the same virtual interface IP address.
  • We must have gathered the MAC address and IP address of every controller that is to be included in the mobility group. This information is necessary because we will be configuring all controllers with the MAC address and IP address of all the other mobility group members.
  • When we configure mobility groups using a firewall, for example, Cisco ASA, we must open port 16666, and IP protocol 97.

We have only 2 WLC so we will not configure Multicast Group IP address in this post.

If we have multiple controllers in Mobility Group then we must configure Multicast Group IP address on each controller.


Via CLI:

config mobility group domain domain_name

(WLC1) > config mobility group domain Test

config mobility group member add mac_address ip_address

(WLC1) > config mobility group member add 00:21:d8:fa:fd:a0

config mobility multicast-mode {enable | disable} local_group_multicast_address

(WLC1) > config mobility multicast-mode enable

config mobility group multicast-address group_name IP_address

(WLC1) > config mobility group multicast-address Test

See the verification of Mobility Summary by using this command:

Show mobility Summary

(WLC1) >show mobility summary
 Symmetric Mobility Tunneling (current) .......... Enabled
 Symmetric Mobility Tunneling (after reboot) ..... Enabled
 Mobility Protocol Port........................... 16666
 Default Mobility Domain.......................... Test
 Multicast Mode .................................. Disabled
 Mobility Domain ID for 802.11r................... 0x840e
 Mobility Keepalive Interval...................... 10
 Mobility Keepalive Count......................... 3
 Mobility Group Members Configured................ 2
 Mobility Control Message DSCP Value.............. 0
 Controllers configured in the Mobility Group
 MAC Address        IP Address       Group Name                        Multicast IP     Status
 00:21:d8:fa:66:00       Test                              Up
 00:21:d8:fa:fd:a0       Test                              Up
 (WLC1) >


2 thoughts on “Mobility Configuring on WLC

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s