ndt-dev - [ndt-dev] [ndt] r537 committed - Added descriptions of the c2sdata, c2sack, s2cdata and s2cack variable...
Subject: NDT-DEV email list created
List archive
[ndt-dev] [ndt] r537 committed - Added descriptions of the c2sdata, c2sack, s2cdata and s2cack variable...
Chronological Thread
- From:
- To:
- Subject: [ndt-dev] [ndt] r537 committed - Added descriptions of the c2sdata, c2sack, s2cdata and s2cack variable...
- Date: Fri, 26 Aug 2011 10:53:13 +0000
Revision: 537
Author:
Date: Fri Aug 26 03:52:48 2011
Log: Added descriptions of the c2sdata, c2sack, s2cdata and s2cack variables.
http://code.google.com/p/ndt/source/detail?r=537
Modified:
/wiki/NDTDataFormat.wiki
=======================================
--- /wiki/NDTDataFormat.wiki Fri Aug 26 02:46:27 2011
+++ /wiki/NDTDataFormat.wiki Fri Aug 26 03:52:48 2011
@@ -75,10 +75,10 @@
|| *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 || ||
-|| 35. || c2sack || ||
-|| 36. || s2cdata || ||
-|| 37. || s2cack || ||
+|| *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. ||
- [ndt-dev] [ndt] r537 committed - Added descriptions of the c2sdata, c2sack, s2cdata and s2cack variable..., ndt, 08/26/2011
Archive powered by MHonArc 2.6.16.