Feedback
Contents
Mobility Commands
mobility anchor
To configure and enable mobility sticky anchoring, use the mobility anchor sticky command. To disable the sticky anchoring, use the no form of the command.
To configure guest anchoring, use mobility anchor ip
. To delete the guest anchor, use the no form of the command.Syntax Description
sticky
Note This command is by default enabled and ensures low roaming latency. This ensures that the point of presence for the client does not change when the client joins the mobility domain and roams within the domain. ip-addr Configures the IP address for guest anchor controller.
Command History
Usage Guidelines
- The wlan_id or guest_lan_id must exist and be disabled.
- Auto-anchor mobility is enabled for the WLAN or wired guest LAN when you configure the first mobility anchor.
- Deleting the last anchor disables the auto-anchor mobility feature and resumes normal mobility for new associations.
- Mobility uses the following ports, that are allowed through the firewall:
wireless mobility controller
To configure mobility controller settings, use the wireless mobility controller command. To remove a mobility controller settings, use the no form of the command.
wireless mobility controller peer-group peer-group-name [ bidge-domain-id id | member ip ip-address [ public-ip | public-ip-address ] | multicast ip multicast-address ]
nowireless mobility controller peer-group peer-group-name [ bidge-domain-id id | member ip ip-address [ public-ip | public-ip-address ] | multicast ip multicast-address ]
Syntax Description
peer-group peer-group-name Creates a mobility peer group.
bidge-domain-id id Configures bridge domain ID for the mobility peer group.
member ip ip-address public-ip public-ip-address Adds or deletes a peer group member.
Note The public-ip public-ip-address is optional and is only when the mobility peer is NATed. multicast ip multicast-address Configures multicast settings of a peer group.
Command History
Usage Guidelines
In the Converged Access solution, WLANs are mapped to VLANs, and VLANs are usually mapped to subnets. For seamless roaming, the same VLAN configured on two controllers is expected to be mapped to the same subnet. This identical mapping from one controller to the next is important for roaming, because the controllers taking care of the roaming event need to determine if they need:This determination is made by comparing the WLAN SSID string and the VLAN ID between controllers. In cases where the WLAN SSID and VLAN ID are identical, the expectation is that the subnet associated to the VLAN is identical as well.
There may be cases where this mapping is not identical. For example, suppose that WLAN1 on controller 1 is mapped to VLAN 14, and that VLAN 14 on controller1 is mapped to the subnet 10.10.14.0/24. Also suppose that WLAN 1 on controller 2 is mapped to VLAN 14, but that VLAN 14 on controller 2 is mapped to this subnet 172.31.24.0/24. Controllers 1 and 2 will compare WLAN1 and the associated VLAN and conclude that they are addressing a Layer 2 roaming event, whereas the roaming even is Layer 3, as VLAN 14 does not have the same Layer 3 significance on both controllers.
When this disconnect between VLANs and their associated subnet occurs, you may want to configure your Converged Access controllers for different bridge domain IDs. Two controllers in the same bridge domain ID are expected to have the same VLAN to subnet mapping. Cisco recommends that you configure the same bridge domain ID on all controllers that share the same VLAN to subnet mapping, and between which roaming is expected.
Examples
This example shows how to configure a controller bridge domain ID.Switch (config)# wireless mobility controller peer-group SPG1 bridge-domain-id 111Examples
This example shows how to create and configure a controller peer group with a bridge ID of 111:
Switch(config)# controller peer-group TestDocPeerGroup bridge-domain-id 111Examples
This example shows how to disable a controller peer group with a bridge ID of 111:Switch(config)# no controller peer-group TestDocPeerGroup bridge-domain-id 111wireless mobility controller (ip_address)
To configure the mobility controller, use the wireless mobility controller command.
To convert the switch from MC to MA, use the no wireless mobility controllerform of the command.
To delete the mobility controllers IP address, use the no wirelessmobility controller ip-address
wireless mobility controller [ ip ip-address [ public-ip public-ip-address ] ]
no wireless mobility controller
no wireless mobility controller ip ip-address
Syntax Description
Command History
Usage Guidelines
This command is valid only for the converged access switch.
The NAted address is used to establish communication, and the configured Wireless Management interface is used to identify the peer controller during the CAPWAP exchanges.
wireless mobility group keepalive
To configure the mobility group parameter and keep alive its ping parameters, use the wireless mobility group keepalive command. To remove a mobility group parameter, use the no form of the command.
wireless mobility group keepalive { count number | interval interval }
no wireless mobility group keepalive { count numbe r | interval interval }
Syntax Description
count number Number of times that a ping request is sent to a mobility group member before the member is considered unreachable. The range is from 3 to 20. The default is 3.
interval interval Interval of time between each ping request sent to a mobility group member. The range is from 1 to 30 seconds. The default value is 10 seconds.
Command History
wireless mobility group member ip
To add or delete users from mobility group member list, use the wireless mobility group member ip command. To remove a member from the mobility group, use the no form of the command.
wireless mobility group member ip ip-address [ public-ip public-ip-address ] [ group group-name ]
no wireless mobility group member ip ip-address
Syntax Description
ip-address The IP address of the member controller.
public-ip public-ip-address
Note This command is used only when the member is behind a NAT. Only static IP NAT is supported. group group-name
Note This command is used only when the member added in not in the same group as the local mobility controller. Command History
Usage Guidelines
The mobility group is used when there is more than one Mobility Controller (MC) in a given deployment. The mobility group can be assigned with a name or it can use the default group name. The mobility group members need to be configured on all the members of the group to roam within the group.
wireless mobility group name
To configure hte mobility domain name, use the wireless mobility group name command. To remove the mobility domain name, use the no form of the command.
Note
If you are configuring the mobility group in a network where network address translation (NAT) is enabled, enter the IP address that is sent to the controller from the NAT device rather than the controller’s management interface IP address. Otherwise, mobility will fail among controllers in the mobility group.Syntax Description
domain-name Creates a mobility group by entering this command. The domain name can be up to 31 case-sensitive characters.
Command History
wireless mobility load-balance
This command is used to load-balance the mobile clients on a mobility anchor (MA) from a switch peer group (SPG) that is least loaded and is chosen to act as the point of presence for the mobile client.
To configure the mobility load-balance status, use the wireless mobility load-balance command.
To disable the mobility load-balance, use the no wirelessmobility load-balanceform of the command.
To configure the client load on the switch where mobility load-balance is turned on, use the no wirelessmobility load-balance threshold form of the command.
wireless mobility load-balance [ threshold threshold ]
[ no ] wireless mobility load-balance [threshold]
[ no ] wireless mobility load-balance
Syntax Description
threshold threshold Configures the threshold for the number of clients that can be anchored locally.
Command History
wireless mobility oracle ip
To configure mobility oracle settings, use the wireless mobility oracle ip command. To remove the mobility oracle settings, use the no form of the command.
Syntax Description
Command History
Usage Guidelines
By default the [no] wireless mobility oracle is configured on the switch. A peer mobility controller must be configured for mobility to work.
The mobility oracle is recommended when more than one mobility controller (MC) in a configurtion is allowed a fast client join and roaming across the sub-domains. The mobility oracle (MO) must be enabled on one of the MCs and the remaing MCs in the sub-domain must point to that MO.
show wireless mobility
show wireless mobility [ load-balance summary | agent | mobility-agent-ip | client summary | ap-list | controller client summary | dtls connections | oracle summary | statistics summary ]
Syntax Description
load-balance summary Shows the mobility load-balance properties.
agent mobility-agent-ip client summary Shows the active clients on a mobility agent.
ap-list Shows the list of Cisco APs known to the mobility group.
controller client summary Shows the active clients in the subdomain.
dtls connections Shows the DTLS server status.
oracle summary Displays the status of the mobility-controllers known to the mobility-oracle.
mobilityoracleclient summary Shows the mobility-oracle client and status database.
statistics Shows the statistics for the Mobility manager.
summary Shows the summary of the mobility manager.
Command History
Examples
This example shows how to display a summary of the mobility manager:
Switch (config)# show wireless mobility ap-list AP name AP radio MAC Controller IP Learnt from ------------------------------------------------------------------------------------------------------ TSIM_AP-101 0000.2000.6600 9.9.9.2 Self TSIM_AP-102 0000.2000.6700 9.9.9.2 Self TSIM_AP-103 0000.2000.6800 9.9.9.2 Self TSIM_AP-400 0000.2001.9100 9.9.9.2 Self TSIM_AP-402 0000.2001.9300 9.9.9.2 Self TSIM_AP-403 0000.2001.9400 9.9.9.2 Self TSIM_AP-406 0000.2001.9700 9.9.9.2 Self TSIM_AP-407 0000.2001.9800 9.9.9.2 Self TSIM_AP-409 0000.2001.9a00 9.9.9.2 Self
