An engineer is planning a wireless deployment with two members in a mobility group. The engineer notices that there are issues establishing the mobility tunnel. The engineer must test the mobility…

The 'debug route' command traces IP routing decisions on the controller and does not send or test EoIP data packets between mobility peers.

The 'eping' command on a Cisco WLC sends an EoIP ping to a peer mobility controller, specifically testing whether the GRE/EoIP data plane of the mobility tunnel is operational. This is the correct tool for verifying that actual client data can traverse the mobility tunnel between two controllers, and a successful response confirms bidirectional EoIP connectivity at the data-forwarding layer.

The 'debug icmp' command enables ICMP packet debugging on the controller and does not test EoIP data-plane connectivity between mobility group members.

The 'mping' command tests the mobility control-plane (UDP port 16666) between WLCs, verifying mobility messaging connectivity - not EoIP data forwarding, which is what the question specifically requires.