Running Mobility Ping Tests - Cisco 2100 Series Configuration Manual

Running Mobility Ping Tests

•
Running Mobility Ping Tests
Controllers in a mobility list communicate with each other by controlling information over a well-known
UDP port and exchanging data traffic through an Ethernet-over-IP (EoIP) tunnel. Because UDP and EoIP
are not reliable transport mechanisms, there is no guarantee that a mobility control packet or data packet
will be delivered to a mobility peer. Mobility packets may be lost in transit due to a firewall filtering the
UDP port or EoIP packets or due to routing issues.
Controller software release 4.0 or later enables you to test the mobility communication environment by
performing mobility ping tests. These tests may be used to validate connectivity between members of a
mobility group (including guest controllers). Two ping tests are available:
•
•
Only one mobility ping test per controller can be run at a given time.
These ping tests are not Internet Control Message Protocol (ICMP) based. The term "ping" is used to
Note
indicate an echo request and an echo reply message.
Use these commands to run mobility ping tests using the controller CLI.
1.
Cisco Wireless LAN Controller Configuration Guide
12-28
To use the controller CLI to verify that symmetric mobility tunneling is enabled, enter this
command:
show mobility summary
Information similar to the following appears:
Symmetric Mobility Tunneling (current) .......... Enabled
Symmetric Mobility Tunneling (after reboot) ..... Enabled
Mobility Protocol Port........................... 16666
Mobility Security Mode........................... Disabled
Default Mobility Domain.......................... User1
Mobility Keepalive interval...................... 10
Mobility Keepalive count......................... 3
Mobility Group members configured................ 7
Controllers configured in the Mobility Group
MAC Address IP Address
00:0b:85:32:b0:80 10.28.8.30
00:0b:85:47:f6:00 10.28.16.10
00:16:9d:ca:d8:e0 10.28.32.10
00:18:73:34:a9:60 10.28.24.10
00:18:73:36:55:00 10.28.8.10
00:1a:a1:c1:7c:e0 10.28.32.30
00:d0:2b:fc:90:20 10.28.32.61
Mobility ping over UDP—This test runs over mobility UDP port 16666. It tests whether the
mobility control packet can be reached over the management interface.
Mobility ping over EoIP—This test runs over EoIP. It tests the mobility data traffic over the
management interface.
To test the mobility UDP control packet communication between two controllers, enter this
command:
mping mobility_peer_IP_address
The mobility_peer_IP_address parameter must be the IP address of a controller that belongs to the
mobility list.
Chapter 12 Configuring Mobility GroupsWireless Device Access
Group Name Status
User1 Up
User1 Up
User1 Up
<local> Up
User1 Up
User1 Up
User1 Control and Data Path Down
OL-17037-01