Testing Basic Functions of the SAProuter
Context
Before using SAProuter, you should test whether there are any network problems.
The following table shows the test scenario when using niping:
SAProuter runs in window 1, the server in window 2, and the client in window 3.
|
Window 2 (host2) |
Window 1 (host1) |
Window 3 (host3) |
|
|---|---|---|---|
|
Without SAProuter |
niping -s |
niping -c -H host2 |
|
|
With SAProuter |
niping -s |
saprouter -r |
niping -c -H /H/host1/H/host2 |
|
Window 2 (host2) |
Window 1 (host1) |
Window 3 (host3) |
|
|---|---|---|---|
|
Without SAProuter |
call niping ('-s') |
call niping ( '-c' '-H' 'host2' ) |
|
|
With SAProuter |
call niping ('-s') |
call saprouter ('-r') |
call niping ( '-c' '-H' '/H/host1/H/host2' ) |
Procedure
Results
-
In steps 3 and 4, data packages are sent to the server, and the server sends the data packages back.
-
In step 7 a list of function names, parameters, and return codes is displayed. If the self-test is successful, the following message appears:
*** SELFTEST O.K. ***
