$ cd /opt/score/sbin $ ./rpmtest comp0 udp -iter 10000 -dest 0 -ping Success: Two numbers similar to "8 0.000233266" are printed The first number is the data size (in bytes) The second number is the latency (in seconds) Failure: Error and dump messages are printedIf this test fails, read the Troubleshooting section.
$ cd /opt/score/sbin $ ./rpmtest comp1 udp -replyIssue the following commands in another window on the server host:
$ cd /opt/score/sbin $ ./rpmtest comp0 udp -iter 10000 -dest 1 -ping Results should be the same as the loopback testWhen the test finishes, do not forget to kill the
pmtest
process on the server host because the process is in an infinite loop.
Note that, on PM/Agent/UDP, you have to kill and restart the
``pmtest...-reply
'' process each time before running
``pmtest...-ping
'', if you try
``pmtest...-ping
'' repeatedly.
PM_DEBUG=1; export PM_DEBUG
'',
or, if you are using csh
, please execute
``setenv PM_DEBUG 1
''),
and run pmtest again.PM_DEBUG=1; export PM_DEBUG
'',
or, if you are using csh
, please execute
``setenv PM_DEBUG 1
''),
and run pmtest again../rpmtest...-ping
'' was invoked
repeatedly without restarting
``./rpmtest...-reply
''.
If so, this is normal and there is no problem.
On PM/Agent, The process
``./rpmtest...-reply
'' should be killed
and restarted before invoking
``./rpmtest...-ping
''.
-dest
argument
is different from the configuration file.