Controller Based WLANs

How to better troubleshoot network issues with extended ping and extended traceroute ?

by on ‎07-10-2014 02:19 PM

Environment : This article applies to Aruba Mobility Controllers running ArubaOS version 6.3.x and Above.

 

Starting from Aruba OS 6.3.x extended ping and extended traceroute functionality was Included which will better help to troubleshoot network issues.

 

(NTWK-SER-3400) #ping 74.125.236.135 ?

count           The number of ping packets [ 1 - 100 ] that are sent to the target-ip-address.

The default is five with standard ping, but you could send 100 with extended ping. If your network is having trouble periodically you could test this with extended ping.
 

df-flag           Sets the Dont-Fragment Flag.

The Don't Fragment option does not allow this packet to be fragmented when it has to go through a segment with a smaller maximum transmission unit (MTU), and you will receive an error message from the device that wanted to fragment the packet. This is useful for determining the smallest MTU in the path to a destination.


packet-size  The size in bytes [ 10 - 2000 ] of a ping datagram.


While the default is to send a 100-byte ping, with extended ping you could send very large ping packets. Perhaps your network is having trouble with large data transfers.
 

source        Sets the source interface for a ping datagram.

The Vlan interface or IP address of the router to use as a source address for the probes. The Controller normally picks the IP address of the outbound interface to use. Useful to troubleshoot Vlan related issues.


Just as you can use the extended ping command to determine what kind of connectivity problems you're having, you can use the extended traceroute command to narrow down where the problem is happening.

(NTWK-SER-3400) #traceroute 74.125.236.135 ?

source                  Sets the Source IP Address, thorugh which route is traced.
<cr>

Comments
Len.Francies

I'm using a default-gw and not routing on my controllers so I have a bunch of connected routes for my vlan interfaces and the 0/0 route in the show ip route table.

It took me a while to realize this was why I could not source ping to the internet to prove firewall settings.

 

The source traceroute really looked enticing but it hangs up the cli session until the 30 hops fail then that is printed to the screen and I regain access to the controller. I haven't intuited the proper control-break sequence to stop the traceroute.  Tried control-break and killed my vty session and when I came back in it paused until the 30 hops of the lost vty session finished.

 

If there is a way to break gracefully that would be nice to know.

RAP_Deployment

" The source traceroute really looked enticing but it hangs up the cli session until the 30 hops fail then that is printed to the screen and I regain access to the controller. I haven't intuited the proper control-break sequence to stop the traceroute.  Tried control-break and killed my vty session and when I came back in it paused until the 30 hops of the lost vty session finished."

 

Same here.  Anyone know how to break out of the traceroute?

TSCPL_Brian

Still seems to be an issue-how can we break out of the traceroute, or set fewer failures?

Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.