Running Mobility Ping Tests - Cisco SD2008T-NA Configuration Manual

4400 series wireless lan controller
Hide thumbs Also See for SD2008T-NA:
Table of Contents

Advertisement

Chapter 11
Configuring Mobility GroupsWireless Device Access

Running Mobility Ping Tests

Controllers belonging to the same mobility group 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 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.
2.
3.
OL-9141-03
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 a
mobility group.
To test the mobility EoIP data packet communication between two controllers, enter this command:
eping mobility_peer_IP_address
The mobility_peer_IP_address parameter must be the IP address of a controller that belongs to a
mobility group.
To troubleshoot your controller for mobility ping, enter these commands:
config msglog level verbose
show msglog
To troubleshoot your controller for mobility ping over UDP, enter this command to display the
mobility control packet:
debug mobility handoff enable
Cisco recommends using an ethereal trace capture when troubleshooting.
Note
Cisco Wireless LAN Controller Configuration Guide
Running Mobility Ping Tests
11-15

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Sfe2000p440244042000 series2100 series

Table of Contents