Using The Cli To Configure Auto-Anchor Mobility - Cisco 2100 Series Configuration Manual

Chapter 12 Configuring Mobility GroupsWireless Device Access
This page lists the controllers that have already been configured as mobility anchors and shows the
current state of their data and control paths. Controllers within a mobility group communicate among
themselves control information over a well-known UDP port and exchange data traffic through an
Ethernet-over-IP (EoIP) tunnel. Specifically, they send mpings, which test mobility control packet
reachability over the management interface, over mobility UDP port 16666 and epings, which test the
mobility data traffic over the management interface, over EoIP port 97. The Control Path field shows
whether mpings have passed (up) or failed (down), and the Data Path field shows whether epings have
passed (up) or failed (down). If the Data or Control Path field shows "down," the mobility anchor cannot
be reached and is considered failed.
Select the IP address of the controller to be designated a mobility anchor in the Switch IP Address
Step 4
(Anchor) drop-down box.
Click Mobility Anchor Create. The selected controller becomes an anchor for this WLAN or wired
Step 5
guest LAN.
Note
Click Save Configuration to save your changes.
Step 6
Repeat
Step 7
LAN.
Configure the same set of mobility anchors on every controller in the mobility group.
Step 8

Using the CLI to Configure Auto-Anchor Mobility

Use these commands to configure auto-anchor mobility using the CLI.
Refer to the
Note
ranges and default values of the parameters used in the CLI commands.
1.
2.
OL-17037-01
To delete a mobility anchor for a WLAN or wired guest LAN, hover your cursor over the blue
drop-down arrow for the anchor and choose Remove.
Step 4 and Step 6 to set any other controllers as mobility anchors for this WLAN or wired guest
"Using the GUI to Configure Auto-Anchor Mobility" section on page 12-21
The controller is programmed to always detect failed mobility list members. To change the
parameters for the ping exchange between mobility members, enter these commands:
config mobility group keepalive count count—Specifies 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.
• config mobility group keepalive interval seconds—Specifies the amount of time (in seconds)
between each ping request sent to a mobility list member. The valid range is 1 to 30 seconds,
and the default value is 10 seconds.
Enter config {wlan | guest-lan} disable {wlan_id | guest_lan_id} to disable the WLAN or wired
guest LAN for which you are configuring mobility anchors.
Configuring Auto-Anchor Mobility
Cisco Wireless LAN Controller Configuration Guide
for the valid
12-23