The NIPING Program can be used to diagnose the network or measure network metrics between any two machines running SAP software, for example between:
•Frontend PC and application server
•Two application servers, perhaps belonging to different SAP systems
•Application server and database server or live cache server
•RFC server or client programs and application server
For self guided troubleshooting, please try our Guided Answer for Network analysis.
The NIPING result can be used to measure throughput and roundtrip time and perform stability test for LAN or WAN used. Detailed information can be found in following SAP note.
For demonstration purposes the following example gives commands for a long LAN stability test;
On the client (source) side: niping -c -H your target server name here -B 10 -L 4000 -P -D 900
On the server (target side): niping -s -I 0 (the last character is zero, not the letter O)
So in the above case you have defined the client (-c) and server (-s) commands and the duration of the NIPING trace (4000 loops with a delay of 900ms between each loop which will last for approximately 1 hour).
The results from the output will be as follows;
------- times -----
avg 4.695 ms
max 36.867 ms
min 0.658 ms
tr 12479.766 kB/s
av2 1.178 ms
tr2 49729.472 kB/s
The important values here are av2 and tr2.
av2: This will test your latency between machines, also known as round trip time. For a typical setup, a value of 0.7ms or less is considered a good value although this can vary. If this value is higher, this may suggest communication delay issues between your systems.
tr2: The average throughput will display the real data volume capability of your system connnections (as opposed to bandwidth which is ideal data volume allowance). For example, if you have a 1GB connection and you are only getting throughput values of 100Mbps, this could suggest an performance issue where high data transfers occur.
Please see more about NIPING output results here;
SAP Note 1100926 - FAQ: Network Performance