|
One-way Ping (OWAMP)
|
|
|
|
owping(1) Manual Page
owping(1) owping(1)
NAME
owping - Client application to request one-way latency tests.
SYNOPSIS
owping [options] testpeer [server]
DESCRIPTION
owping is a command line client application that is used to initiate
one-way latency tests.
Round-trip latency measurements (ping) are an accepted technique to
look for network problems; One-way measurements have the potential to
be even more useful. With round-trip measurements it is difficult to
isolate the direction in which congestion is experienced. Traffic is
often asymmetric with many sites being either primarily producers or
consumers of data. One-way measurements allow more informative measure-
ments. It is much easier to isolate the effects of traffic on specific
parts of a network.
owping works by contacting an owampd daemon on the remote peer host.
owampd manages the resources of the host on which it runs.
testpeer can be specified using rfc2396 and rfc2732 syntax for both
host and port specification:
node:port
IPv4 syntax where node is either a DNS name or a numeric host
address string consisting of a dotted decimal IPv4 address. The
port is an optional port specifier to contact servers running on
a non-default port and can be left off in most cases. This syn-
tax also works for IPv6 addresses specified using DNS names.
[node]:port
IPv6 syntax where node is specified using a numeric IPv6 host
address string. The []'s are required only if the optional port
port specifier is used.
server is an optional argument that indicates the OWAMP server address
if it is different from the testpeer. This is mostly useful in the case
of hosts with more than one network interface where the OWAMP server is
not listening on the interface that you want to test. The server can
be specified using the same syntax as the testpeer.
The owping client is used to request the type of test wanted. The
parameters allow the user to select the full send schedule, direction
of test (send, receive, or both) as well as packet size. The results
are returned to the client after the test completes. The test will not
be complete until timeout after the last packet is scheduled to be
sent.
With no options specified, owping will perform concurrent bidirectional
tests of 100 packets each at a rate of approximately 1 packet every 0.1
seconds to and from the testpeer. Then, the receivers on each host will
wait a reasonable period after that to count possible duplicate pack-
ets. (See the -L option.) Upon completion of the sessions, summary
statistics are printed to STDOUT.
OPTIONS
-h
Print a usage message and exit.
Default:
Unset.
ENVIRONMENT VARIABLES
OWAMP Environment Variable Description
----------------------------------------------------------------
OWAMP_DEBUG_TIMEOFFSET Offset time by this amount (float)
EXAMPLES
owping somehost.com
Run two concurrent ~10-second test sessions at a rate of a
packet every 0.1 seconds. One session sending packets from the
local host to somehost.com, the other session receiving packets
from somehost.com.) Print summary statistics of the results
only.
owping somehost.com:98765
Run the same two concurrent test sessions to a server running on
somehost.com but on a non-default port.
owping -u someuser somehost.com
Run the default test as in the first example. Authenticate using
the identity someuser. owping will prompt for a passphrase.
owping -f somehost.com
Run a single ~10-second test session at a rate of one packet
every 0.1 seconds with the packets being sent from somehost.com
and received at the local host.
owping -F from.owp somehost.com
Same as the previous example, with the resulting data saved in
from.owp. The owstats program can be used to decode that
datafile using the same Output options that are available in
owping.
owping -F from.owp -T to.owp somehost.com
Run two concurrent ~10-second test sessions at a rate of a
packet every 0.1 seconds. One session sending packets from the
local host to somehost.com, the other session receiving packets
from somehost.com.) Print summary statistics of the results and
save the resulting data saved in from.owp and to.owp.
owping -i 1e -c 10 somehost.com
Run two concurrent ~10-second test sessions at an average rate
of 1 packet every second. One session sending packets from the
local host to somehost.com, the other session receiving packets
from somehost.com.) Print summary statistics of the results
only.
owping -i 1f -c 10 somehost.com
Run two concurrent ~10-second test sessions at a rate of 1
packet every second. One session sending packets from the local
host to somehost.com, the other session receiving packets from
somehost.com.) Print summary statistics of the results only.
owping -i 1.0e,0f -c 20 somehost.com
Run two concurrent ~10-second test sessions. Send back-to-back
packet pairs at an average rate of a packet pair every 1 sec-
onds. One session sending packets from the local host to some-
host.com, the other session receiving packets from some-
host.com.) Print summary statistics of the results only.
SEE ALSO
owampd(8), owstats(1), owfetch(1) and the
http://e2epi.internet2.edu/owamp/ web site.
ACKNOWLEDGMENTS
This material is based in part on work supported by the National Sci-
ence Foundation (NSF) under Grant No. ANI-0314723. Any opinions, find-
ings and conclusions or recommendations expressed in this material are
those of the author(s) and do not necessarily reflect the views of the
NSF.
$Date: 2007/02/24 11:22:14 $ owping(1)
Man(1) output converted with
man2html
|
|
| One-Way Ping (OWAMP) |
12 September, 2005 |
|
This material is based, in part, on work supported by the National Science
Foundation (NSF) under Grant No. ANI-0314723. Any opinions, findings and conclusions or
recommendations expressed in this material are those of the author(s) and do not necessarily
reflect the views of the NSF.
|
| 
