Validating Wireless Controller Mobility Packets
Short answer
A Use the mping command to send mobility control packets to the peer IP address to validate reachability.
Question
Key Takeaways
The exam tests knowledge of the 'mping' utility versus standard ping or debug commands, with the common trap being confusion with management IP connectivity checks.
This question addresses the specific CLI command required to verify reachability of mobility peers across firewalls on Cisco wireless controllers. The correct answer is (A) mping, which validates that control packets can traverse the network path.
Common mistake: Candidates often select option D because they associate 'eping' with ICMP pings or management plane traffic, failing to recognize that mobility uses a dedicated protocol and peer IP.
Expert Analysis
Why the Answer Is Correct
The mping command (Mobile Ping) is specifically designed to test the reachability of a mobility peer by sending encapsulated mobility control packets. It validates that the necessary ports (typically UDP 16666-16669) are open and that the WLCs can exchange mobility messages, which is critical for seamless roaming. This directly addresses the requirement to validate mobility control packet transmission between separated controllers.
Why the Other Options Are Wrong
Option B (debug mobility handoff enable) and Option C (debug mobility config enable) are troubleshooting tools that display real-time events but do not actively test reachability or connectivity; they generate output only when events occur. Option D (eping mobility_peer_management_IP_address) is not a valid Cisco IOS-XE WLAN controller command for testing mobility; while management IPs are used for GUI/SSH access, mobility peers communicate via their mobility peer addresses, not management addresses, using the mping utility.
Community Comment Notes
The majority of the community voted for A, confirming it as the standard solution. One commenter noted that test packets are sourced from the controller's management interface but target the far end's mobility peer address, reinforcing why mping is the correct tool rather than a simple ping to the management IP.
Exam Strategy
Focus on distinguishing between diagnostic/debugging commands and active testing utilities. For wireless controller exams, memorize the specific syntax for mobility troubleshooting, such as mping, as it is a frequent scenario involving firewall traversal.
Frequently Asked Questions
What is the difference between mping and regular ping on Cisco WLC?
Does mping use the management IP or mobility IP?
Community Votes
75% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 4 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 4
-
Lakshan__97 👍 1 Answered DTest packets are sourced from the controller’s management IP address and target the far end controller’s management IP address.
-
Bembs 👍 2A is the correct answer
-
All_ultrex 👍 2 Answered AA is correct
-
Farhad123 👍 1A is right choice
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.