NDT-DEV email list created

Revision: 548
Author:   

Date:     Mon Aug 29 07:04:12 2011
Log:      Improvements to the web100srv.log description.
http://code.google.com/p/ndt/source/detail?r=548

Modified:
 /wiki/NDTDataFormat.wiki

=======================================
--- /wiki/NDTDataFormat.wiki    Mon Aug 29 04:34:16 2011
+++ /wiki/NDTDataFormat.wiki    Mon Aug 29 07:04:12 2011
@@ -83,16 +83,16 @@

 ===web100srv.log file===

-The NDT always writes a one-line summary of the test to the web100srv.log  
file.
+The NDT always writes a one-line summary of the test to the  
`web100srv.log` file. The `web100srv.log` file is a standard log file and  
may contain lines that aren't summary lines (e.g. if debugging is enabled,  
there's a ton of information logged to this file).

 This one-line summary contains the final values of some of the web100  
variables with an additional analysis details. The particular values are  
separated with commas without any spaces. The results are stored with the  
following order:

 || *#* || *Name* || *Description/Comment* ||
-|| 1. || date || start time of the test session (in the form "Wed Jun 30  
21:49:08 1993\n") ||
-|| 2. || client name || remote (client) host fully qualified name ||
+|| 1. || date || start time of the test session (in the form "Jun 30  
21:49:08") ||
+|| 2. || client name || remote (client) host fully qualified name (if the  
fully qualified name cannot be determined, then the numeric form of the  
address will be used here) ||
 || 3. || MID throughput speed || CWND limited throughput speed measured  
during Middlebox test (value in kb/s) ||
-|| 4. || S2C throughput speed || value in kb/s ||
-|| 5. || C2S throughput speed || value in kb/s ||
+|| 4. || S2C throughput speed || measured throughput speed from server to  
client (value in kb/s) ||
+|| 5. || C2S throughput speed || measured throughput speed from client to  
server (value in kb/s) ||
 || 6. || Timeouts || (*{{{*}}}*) The number of times the retransmit  
timeout has expired when the RTO backoff multiplier is equal to one. ||
 || 7. || SumRTT || (*{{{*}}}*) The sum of all sampled round trip times. ||
 || 8. || CountRTT || (*{{{*}}}*) The number of round trip time samples  
included in tcpEStatsPathSumRTT and tcpEStatsPathHCSumRTT. ||
@@ -116,15 +116,15 @@
 || 26. || !MaxSsthresh || (*{{{*}}}*) The maximum slow start threshold,  
excluding the initial value. ||
 || 27. || CurRTO || (*{{{*}}}*) The current value of the retransmit timer  
RTO. ||
 || 28. || !CurRwinRcvd || (*{{{*}}}*) The most recent window advertisement  
received, in octets. ||
-|| *29.* || *link* || A detected link type. The details of the detection  
algorithm can be found in the [NDTTestMethodology NDT Test Methodology  
document].<br><br>This variable can have the following values:<ul><li>*100*  
- link type cannot be detected</li><li>*0* - detection algorithm  
failed</li><li>*10* - Ethernet link (Fast Ethernet)</li><li>*3* - wireless  
link</li><li>*2* - DSL/Cable modem link</li></ul> ||
-|| *30.* || *mismatch* || A detected mismatch condition. The details of  
the detection algorithm can be found in the [NDTTestMethodology NDT Test  
Methodology document].<br><br>This variable can have the following  
values:<ul><li>*0* - no mismatch condition was detected</li><li>*1* - Old  
Duplex-Mismatch condition was detected</li><li>*2* - Duplex Mismatch  
condition was detected: Switch=Full and Host=Half</li></ul> ||
-|| *31.* || *bad_cable* || A detected bad cable condition. The details of  
the detection algorithm can be found in the [NDTTestMethodology NDT Test  
Methodology document].<br><br>This variable can have the following  
values:<ul><li>*0* - no bad cable condition was detected</li><li>*1* - bad  
cable condition was detected</li></ul> ||
-|| *32.* || *half_duplex* || A detected half duplex condition. The details  
of the detection algorithm can be found in the [NDTTestMethodology NDT Test  
Methodology document].<br><br>This variable can have the following  
values:<ul><li>*0* - no half duplex condition was detected (it means a full  
duplex subnet in the case of the Fast Ethernet link)</li><li>*1* - half  
duplex condition was detected (it means a half duplex subnet in the case of  
the Fast Ethernet link)</li></ul> ||
-|| *33.* || *congestion* || A detected congestion condition. The details  
of the detection algorithm can be found in the [NDTTestMethodology NDT Test  
Methodology document].<br><br>This variable can have the following  
values:<ul><li>*0* - no congestion condition was detected</li><li>*1* -  
congestion condition was detected (it means that other network traffic was  
congesting the link during the test)</li></ul> ||
-|| *34.* || *c2sdata* || A link type detected by the Bottleneck Link  
Detection algorithm using the Client --> Server data packets' inter-packet  
arrival times. The details of the detection algorithm can be found in the  
[NDTTestMethodology NDT Test Methodology document]. <br><br>This variable  
can have the following values:<ul><li>*-1* - System Fault</li><li>*0* -  
RTT</li><li>*1* - Dial-up Modem</li><li>*2* - Cable/DSL modem</li><li>*3* -  
10 Mbps Ethernet or !WiFi 11b subnet</li><li>*4* - 45 Mbps T3/DS3 or !WiFi  
11 a/g subnet</li><li>*5* - 100 Mbps Fast Ethernet subnet</li><li>*6* - a  
622 Mbps OC-12 subnet</li><li>*7* - 1.0 Gbps Gigabit Ethernet  
subnet</li><li>*8* - 2.4 Gbps OC-48 subnet</li><li>*9* - 10 Gbps 10 Gigabit  
Ethernet/OC-192 subnet</li><li>*10* - Retransmissions</li></ul>||
-|| *35.* || *c2sack* || A link type detected by the Bottleneck Link  
Detection algorithm using the Client <-- Server Ack packets' inter-packet  
arrival times. The details of the detection algorithm can be found in the  
[NDTTestMethodology NDT Test Methodology document]. <br><br>This variable  
can have the same values as the *c2sdata* variable ||
-|| *36.* || *s2cdata* || A link type detected by the Bottleneck Link  
Detection algorithm using the Server --> Client data packets' inter-packet  
arrival times. The details of the detection algorithm can be found in the  
[NDTTestMethodology NDT Test Methodology document]. <br><br>This variable  
can have the same values as the *c2sdata* variable ||
-|| *37.* || *s2cack* || A link type detected by the Bottleneck Link  
Detection algorithm using the Server <-- Client Ack packets' inter-packet  
arrival times. The details of the detection algorithm can be found in the  
[NDTTestMethodology NDT Test Methodology document]. <br><br>This variable  
can have the same values as the *c2sdata* variable ||
+|| *29.* || *link* || A detected link type by the set of custom  
heuristics. The details of the detection algorithm can be found in the  
[NDTTestMethodology NDT Test Methodology document].<br><br>This variable  
can have the following values:<ul><li>*100* - link type cannot be detected  
(tests did not recognize the link)</li><li>*0* - detection algorithm failed  
(due to some error condition)</li><li>*10* - Ethernet link (Fast  
Ethernet)</li><li>*3* - wireless link</li><li>*2* - DSL/Cable modem  
link</li></ul> ||
+|| *30.* || *duplex mismatch* || A detected duplex mismatch condition. The  
details of the detection algorithm can be found in the [NDTTestMethodology  
NDT Test Methodology document].<br><br>This variable can have the following  
values:<ul><li>*0* - no duplex mismatch condition was detected</li><li>*1*  
- possible duplex mismatch condition was detected by the Old  
Duplex-Mismatch algorithm</li><li>*2* - possible duplex mismatch condition  
was detected by the new algorithm: Switch=Full and Host=Half</li></ul> ||
+|| *31.* || *bad_cable* || A detected bad cable condition. The details of  
the detection algorithm can be found in the [NDTTestMethodology NDT Test  
Methodology document].<br><br>This variable can have the following  
values:<ul><li>*0* - no bad cable condition was detected</li><li>*1* -  
possible bad cable condition was detected</li></ul> ||
+|| *32.* || *half_duplex* || A detected half duplex condition. The details  
of the detection algorithm can be found in the [NDTTestMethodology NDT Test  
Methodology document].<br><br>This variable can have the following  
values:<ul><li>*0* - no half duplex condition was detected (it means a full  
duplex subnet in the case of the Fast Ethernet link)</li><li>*1* - possible  
half duplex condition was detected (it means a half duplex subnet in the  
case of the Fast Ethernet link)</li></ul> ||
+|| *33.* || *congestion* || A detected congestion condition. The details  
of the detection algorithm can be found in the [NDTTestMethodology NDT Test  
Methodology document].<br><br>This variable can have the following  
values:<ul><li>*0* - no congestion condition was detected</li><li>*1* -  
possible congestion condition was detected (it means that other network  
traffic was congesting the link during the test)</li></ul> ||
+|| *34.* || *c2sdata* || A link type detected by the Bottleneck Link  
Detection algorithm using the *Client --> Server data packets*'  
inter-packet arrival times. The details of the detection algorithm can be  
found in the [NDTTestMethodology NDT Test Methodology document].  
<br><br>This variable can have the following values:<ul><li>*-1* - System  
Fault</li><li>*0* - RTT</li><li>*1* - Dial-up Modem</li><li>*2* - Cable/DSL  
modem</li><li>*3* - 10 Mbps Ethernet or !WiFi 11b subnet</li><li>*4* - 45  
Mbps T3/DS3 or !WiFi 11 a/g subnet</li><li>*5* - 100 Mbps Fast Ethernet  
subnet</li><li>*6* - a 622 Mbps OC-12 subnet</li><li>*7* - 1.0 Gbps Gigabit  
Ethernet subnet</li><li>*8* - 2.4 Gbps OC-48 subnet</li><li>*9* - 10 Gbps  
10 Gigabit Ethernet/OC-192 subnet</li><li>*10* - Retransmissions</li></ul>||
+|| *35.* || *c2sack* || A link type detected by the Bottleneck Link  
Detection algorithm using the *Client <-- Server Ack packets*' inter-packet  
arrival times. The details of the detection algorithm can be found in the  
[NDTTestMethodology NDT Test Methodology document]. <br><br>This variable  
can have the same values as the *c2sdata* variable ||
+|| *36.* || *s2cdata* || A link type detected by the Bottleneck Link  
Detection algorithm using the *Server --> Client data packets*'  
inter-packet arrival times. The details of the detection algorithm can be  
found in the [NDTTestMethodology NDT Test Methodology document].  
<br><br>This variable can have the same values as the *c2sdata* variable ||
+|| *37.* || *s2cack* || A link type detected by the Bottleneck Link  
Detection algorithm using the *Server <-- Client Ack packets*' inter-packet  
arrival times. The details of the detection algorithm can be found in the  
[NDTTestMethodology NDT Test Methodology document]. <br><br>This variable  
can have the same values as the *c2sdata* variable ||
 || 38. || !CongestionSignals || (*{{{*}}}*) The number of multiplicative  
downward congestion window adjustments due to all forms of congestion  
signals, including Fast Retransmit, ECN and timeouts. This object  
summarizes all events that invoke the MD portion of AIMD congestion  
control, and as such is the best indicator of how cwnd is being affected by  
congestion. ||
 || 39. || !PktsOut || (*{{{*}}}*) The total number of segments sent. ||
 || 40. || MinRTT || (*{{{*}}}*) The minimum sampled round trip time. ||