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.
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.
You can 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:
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.
Only one mobility ping test per controller can be run at a given time.
These ping tests are not based on Internet Control Message Protocol (ICMP). The term ping is used to indicate an echo request and an echo reply message.
| Step 1 |
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. |
||
| Step 2 |
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 the mobility list. |
||
| Step 3 |
To troubleshoot your controller for mobility ping over UDP, enter this command to display the mobility control packet: debug mobility handoff enable
|
Feedback