The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
New Mobility enables Cisco WLCs to be compatible with converged access controllers with Wireless Control Module (WCM) such as the Cisco Catalyst 3850 Series Switches and the Cisco 5760 Series Wireless LAN Controllers. New Mobility provides the ability to run Mobility Controller (MC) functionality on a Cisco WLC in the Converged Access mode with a Catalyst 3850 mobility agent (MA)
The Mobility Controller is a part of a hierarchical architecture that consists of a Mobility Agent and Mobility Oracle.
A group of Cisco Catalyst 3850 Series Switches' Mobility Agents can form a switch peer group. The internal Mobility Agent of Cisco WLCs form an independent switch peer group. The Mobility Controller, Mobility Agent, and Mobility Oracle can be in a single Cisco WLC. Each Mobility Controller forms a subdomain that can have multiple switch peer groups. The Cisco WLCs are Mobility Agents by default. However, Cisco Catalyst 3850 Series Switch can function both as Mobility Agent and Mobility Controller, or only as a Mobility Agent.
By default, New Mobility is disabled. When you enable or disable new mobility, you must save the configuration and reboot the controller.
Note | With Release 8.1 in a New Mobility environment, Cisco WLCs running Cisco Wireless software cannot function as mobility controllers (MC). However, the Cisco WLCs can function as guest anchors. |
The keepalives between Mobility Controller and Mobility Oracle are not DTLS encrypted.
For seamless mobility, the controller should either use new mobility or old mobility (flat mobility).
Interoperability between two types of mobility is not supported. When you downgrade the controller from Release 7.5 to a controller software release that does not support new mobility, such as Releases 7.4.100.0, 7.3.101.0, 7.2, 7.0, or earlier (all releases prior to 7.3.112.0), the controller automatically transits to flat mobility (old mobility). This is due to the difference in mobility architecture and noninteroperability between flat mobility (EOIP tunnels) and new mobility(CAPWAP tunnels).
High availability for Mobility Oracle is not supported.
When a client associates for the very first time as local, then in the Cisco WLC, the MA sends a 'handoff complete' message to the MC to update the client database in the MC. However, the 'handoff complete' message is sent in a 'DHCP REQD' state because of which the IP address of the client is 0.0.0.0 for the very first time. This event is triggered by timer expiry.
IPv6 is not supported with new mobility.
Mutli-Session-ID, in which audit session ID is shared accross mobility peers, is not supported with New Mobility.
Enable or
disable new mobility on the controller by entering this command:
When you
enable or disable new mobility, you must save the configuration and reboot the
controller.
Note
Enable the Mobility Oracle or configure an external Mobility Oracle by entering this command:
config mobility oracle{enable| disable | ip ip_address}
Here, ip_address is the IP address of the Mobility Oracle. The Mobility Oracle maintains the client database under one complete mobility domain. It consists of a station database, an interface to the Mobility Controller, and an NTP/SNTP server. There can be only one Mobility Oracle in the entire mobility domain.
Configure the MAC address of the member switch for compatibility between the flat (old) and new mobility by entering this command:
config mobility group member add ip_address{[group-name] | mac-address | [public-ip-address]}
where ip_address is the IP address of the member.
group-name is the member switch group name, if it is different from the default group name.
mac-address is the MAC address of the member switch.
Note | If the controller has NAT configured, the public IP address will be the network address translated IP address. |
Note | New mobility does not support IPv6. |
View the details of the mobility controllers according to the Mobility Oracle by entering this command:
show mobility oracle summary
View the summary and details of the Mobility Oracle client database by entering this command:
show mobility oracle client {summary | detail}
Verify the mobility statistics by entering this command:
show mobility statistics
Verify the mobility configuration by entering this command:
show mobility summary
Save your changes by entering this command:
save config
Enable or disable debugging of mobility packets by entering this command:
debug mobility packet {enable | disable}
Enable or disable debugging of the Mobility Oracle events and errors by entering this command:
debug mobility oracle {events | errors} {enable| disable}