...
We wrote a script ping-vs-tcp.pl.
| Code Block |
|---|
Usage: ping-vs-tcp.pl [opts] Opts: -v print this USAGE information -D debug_level (default=0) -p protocol (6 or '') (default '') -a application port (default = 80) -c count of pinfs to be sent (default = 10) Function: Ping the host provided in %NODE_DETAILS For each host it gets the IP address either from NODE_DETAILS (IPv4) or using the dig command (IPv6). It then Pings and npings the host and gathers the min, average, maximum RTTs and losses and reports them to STDOUT. together with a time stamp and host information such as name, IP address, countrycontry, region etc. Externals: Requires nping (requires root/sudo privs), dig Input: It gets information on the PingER hosts from %NODE_DETAILS using: wget to get the require '/afs/slac/package/pinger/nodes.cf';required file from http://www-iepm.slac.stanford.edu/pinger/pingerworld/slaconly-nodes.cf. The required file is saved in in /tmp with a unique name /tmp/nodes-3458.cf (based on the process number). Examples: ping-vs-tcp.pl ping-vs-tcp.pl -p 6 -a 22 -c 2010 ping-vs-tcp.pl -v -D 1 |
The output is in comma separated value format and is exported to Excel (one file for IPv4, one for IPv6) where it is analyzed to look at the histograms of Average(ping_rtt)-Average(nping_rtt) etc. The script was run from a host (pinger.slac.stanford.edu) located st SLAC in Northern California in the San Francisco Bay Area. For the IPv4 data measurements, the script ran for about 6hours and 45 minutes.The distribution histograms shown below show that the agreement between ping and nping average RTT is good:
...