1\cping
To test mobility data traffic using CAPWAP, use the cping command.
cping mobility_peer_IP_address
Syntax Description
|
mobility_peer_IP_address
|
IP address of a peer mobility controller.
|
Command Default
None
Command History
|
Release
|
Modification
|
|
7.5
|
This command was introduced in the controller 7.5 Release.
|
Usage Guidelines
This command tests the mobility data traffic using the new mobility architecture.
Examples
The following example shows how to test the data traffic of a controller with peer mobility IP address as 172.12.35.31:
(Cisco Controller) >cping 172.12.35.31
2\eping
To test the mobility Ethernet over IP (EoIP) data packet communication between two Cisco WLCs, use the eping command.
eping mobility_peer_IP_address
Syntax Description
|
mobility_peer_IP_address
|
IP address of a controller that belongs to a mobility group.
|
Command Default
None
Command History
|
Release
|
Modification
|
|
7.6
|
This command was introduced in a release earlier than Release 7.6.
|
|
8.0
|
This command supports only IPv4 address format.
|
Usage Guidelines
This command tests the mobility data traffic over the management interface.
|
Note
|
This ping test is not Internet Control Message Protocol (ICMP) based. The term “ping” is used to indicate an echo request and an echo reply message.
|
The IPv6 address format for this command is not supported.
Examples
The following example shows how to test EoIP data packets and to set the IP address of a controller that belongs to a mobility group to 172.12.35.31:
(Cisco Controller) >eping 172.12.35.31
3\mping
To test mobility UDP control packet communication between two Cisco WLCs, use the mping command.
mping mobility_peer_IP_address
Syntax Description
|
mobility_peer_IP_address
|
IP address of a controller that belongs to a mobility group.
|
Command Default
None
Command History
|
Release
|
Modification
|
|
7.6
|
This command was introduced in a release earlier than Release 7.6.
|
|
8.0
|
This command supports both IPv4 and IPv6 address formats.
|
Usage Guidelines
This test runs over mobility UDP port 16666. It tests whether the mobility control packet can be reached over the management interface.
|
Note
|
This ping test is not Internet Control Message Protocol (ICMP) based. The term “ping” is used to indicate an echo request and an echo reply message.
|
Examples
The following example shows how to test mobility UDP control packet communications and to set the IP address of a Cisco WLC that belongs to a mobility group to 172.12.35.31:
(Cisco Controller) >mping 172.12.35.31
4\ping
To send ICMP echo packets to a specified IP address, use the ping command:
ping ip-addr interface-name
Syntax Description
|
ip-addr
|
IP address of the interface that you are trying to send ICMP echo packets to
|
|
interface-name
|
Name of the interface to which you are trying to send ICMP echo packets
|
Command Default
None
Command History
|
Release
|
Modification
|
|
7.6
|
This command was introduced in a release earlier than Release 7.6.
|
Usage Guidelines
When you run the ping command, the CPU spikes up to 98 percent in the “osapi_ping_rx process”. While the ping command is running, the terminal and web activity on the Cisco WLC is blocked.
運行ping命令時，CPU在“osapi_ping_rx進程”中最高可達98％。 ping命令正在運行時，Cisco WLC上的終端和Web活動被阻止。
Examples
The following example shows how to send ICMP echo packets to an interface:
(Cisco Controller) >ping 209.165.200.225 dyn-interface-1