How to run ping, tcpping, tcpdump and traceroute on CloudGenix ION device

How to run ping, tcpping, tcpdump and traceroute on CloudGenix ION device

23118
Created On 05/06/21 00:06 AM - Last Modified 05/10/22 22:18 PM


Objective


  • Ping - Tests Internet Control Message Protocol (ICMP) reachability of a host.
  • tcpping - Debugs Transmission Control Protocol (TCP) connect/ping to a given destination or port combination
  • tcpdump - Displays traffic on a network
  • traceroute - Traces route to an IPv4 address to check a path


Environment


CloudGenix

Procedure


The following commands are run on the device CLI.

 

ping:  ping interface host (args =" ")

Example of ping which controls the count (-c) and the ping packet size (-s)

ION-1# ping controller1 8.8.8.8 args="-c 3 -s 1400"
PING 8.8.8.8 (8.8.8.8): 1400 data bytes
1408 bytes from 8.8.8.8: seq=0 ttl=59 time=50.710 ms
1408 bytes from 8.8.8.8: seq=1 ttl=59 time=50.590 ms
1408 bytes from 8.8.8.8: seq=2 ttl=59 time=50.568 ms

tcpping:  tcpping interface dst-ipv4:port
tcpping controller1 google.com:80
tcpping connected to 216.58.203.174:80 time=2ms
tcpping controller1 yahoo.com:80
tcpping connected to 206.190.36.45:80 time=28ms

tcpdump: tcpdump interface= interface name or number (args= " " | show | save file= filename)

Example: tcpdump filtering on host IP 8.8.8.8, protocol = icmp, and display ethernet frame info (-e)

ION-1# tcpdump controller1 args=" -e host 8.8.8.8 and icmp" show tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 14:06:13.488774 00:50:56:92:30:be > 00:50:56:92:8b:1a, ethertype IPv4 (0x0800), length 98: 192.168.30.10 > 8.8.8.8: ICMP echo request, id 12410, seq 0, length 64 14:06:13.539514 3e:2d:5f:3a:be:bd > 00:50:56:92:30:be, ethertype IPv4 (0x0800), length 98: 8.8.8.8 > 192.168.30.10: ICMP echo reply, id 12410, seq 0, length 64

traceroute: traceroute interface dst-ipv4 (args=" ")
ION-1# traceroute 1 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8) from 192.168.1.1, 30 hops max, 46 byte packets
 1  10.73.99.1 (10.73.99.1)  0.661 ms  0.572 ms  0.827 ms
 2  208.184.44.129.IPYX-118386-ZYO.zip.zayo.com (208.184.44.129)  0.752 ms  1.015 ms  0.938 ms
 3  ge-11-1-4.mpr1.dfw5.us.zip.zayo.com (208.185.28.181)  1.218 ms  1.320 ms  1.207 ms
 4  ae5.mcs1.dfw2.us.zip.zayo.com (64.125.28.85)  2.558 ms  2.429 ms  2.413 ms
 5  ae1.cs1.dfw2.us.eth.zayo.com (64.125.28.124)  2.067 ms  2.229 ms  1.971 ms
 6  *  *  *
 7  64.125.15.61 (64.125.15.61)  2.052 ms  1.923 ms  1.902 ms
 8  108.170.252.129 (108.170.252.129)  2.006 ms  1.985 ms  108.170.240.193 (108.170.240.193)  2.027 ms
 9  108.170.230.117 (108.170.230.117)  1.931 ms  108.170.231.71 (108.170.231.71)  2.188 ms  108.170.230.113 (108.170.230.113)  2.065 ms
10  dns.google (8.8.8.8)  2.047 ms  1.859 ms  1.899 ms

 



Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000oM5NCAU&lang=en_US%E2%80%A9&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail

Choose Language