PING Example
C:\>ping -w 5000 172.23.10.2
Pinging 172.23.10.2 with 32 bytes of data:
Reply from 172.23.10.2: bytes=32 time=641ms TTL=59
Reply from 172.23.10.2: bytes=32 time=703ms TTL=59
Reply from 172.23.10.2: bytes=32 time=593ms TTL=59
Reply from 172.23.10.2: bytes=32 time=641ms TTL=59
Ping statistics for 172.23.10.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 593ms, Maximum = 703ms, Average = 644ms
TRACEROUTE (TRACERT) as a Performance Measuring Tool
Traceroute,
named tracert in Windows™ environments,
is a utility that describes the path in real-time from the
client machine to the remote host being contacted. It reports the IP addresses of all the routers in between. It also
reports the latency delays encountered at each hop. As with ping, E-DBA’s cycle mechanism may produce an unex-
pectedly large delay when traversing an E-DBA airlink. A large timeout value is also recommended when using
Traceroute.
TRACEROUTE Example
C:\>tracert -w 5000 172.23.10.2
Tracing route to 172.23.10.2 over a maximum of 30 hops
1 <10 ms <10 ms <10 ms 192.168.36.37
(host
→
base)
2 641 ms 734 ms 750 ms 172.23.10.2
(host
→
base
→
mobile)
Trace complete.
FTP as a Performance Measuring Tool
FTP is a protocol used to transfer files over a TCP/IP network. Applications that implement that protocol are good
candidates for measuring the throughput of a link. Note that the FTP & TCP/IP software components in the server
and client computers may have an adverse effect on performance – factors such as FTP buffer size, TCP window
size and the TCP congestion-control algorithm may interact to produce throughput lower than that of the theoreti-
cal maximum. As well, be careful about inferring total system performance from the result of a single FTP transfer.
92
