Measurement	Description	Measurement Unit	Interpretation
Connection_attempts	The number of TCP connections attempted by the client	Number
Connection_successes	The number of TCP connection attempts that succeeded	Number
Connection_failures	The number of TCP connection attempts that failed	Number	Connection failures could be due to performance issues in the interconnection network or at the server end.
Connection_status	The percentage of TCP connection attempts that succeeded	Percent	A value close to 100 indicates that the network connection is good. A drop in this value is an indicator of poor network or server performance.
Avg_connect_time	This measure indicates how long it took on an average to establish a TCP connection.	Secs	When packet loss occurs on the network, TCP uses an exponential back-off algorithm to retry connection establishment. Hence, connection times are likely to grow exponentially as packet loss worsens. A high increase in this metric is an indicator of network connectivity issues (mostly congestion).
Max_connect_time	This measure indicates the longest TCP connect time during the last measurement period.	Secs
Out_of_order_xmits	The number of TCP packets that were received out of order. TCP is a connection-oriented protocol, and in most cases, packets are received in order	Number	While out of order transmissions by themselves are not a problem, a large number of our of order transmissions could potentially happen because of packet retransmissions being done at the TCP layer. It is important to monitor retransmissions because TCP throughput and responsiveness decrease drastically with increase in retransmissions. A sudden increase in the out of order transmits or a high percentage of out of order transmissions requires additional investigation. More often than not, such an increase in transmissions is an indicator of a network performance issue.
Out_of_order_xmit_pct	The ratio of packets transmitted out of order to packets transmitted. TCP is a connection-oriented protocol, and in most cases, packets are received in order.	Percent	While out of order transmissions by themselves are not a problem, a large number of our of order transmissions could potentially happen because of packet retransmissions being done at the TCP layer. It is important to monitor retransmissions because TCP throughput and responsiveness decrease drastically with increase in retransmissions. A sudden increase in the out of order transmits or a high percentage of out of order transmissions requires additional investigation. More often than not, such an increase in transmissions is an indicator of a network performance issue. A value of 30% or above is a cause for investigation (e.g., use a network sniffer to drill down deeper into the network transmissions).
Out_of_order_receives	The number of TCP packets received out of order	Number	Typically, this should be a very low value. A large value is an indicator that potentially a number of retransmissions are happening on the network. Just like packet transmissions (see above), retransmission of packets received can also indicate potential network issues.
Out_of_order_receive_pct	The ratio of packets received out of order to packets received	Percent	A value greater than 20% requires additional investigation (e.g., use a network sniffer to drill down deeper into the network transmissions).

Note:

For the ClientTcpTest and ClientServiceTest to function smoothly, the eG agent on Windows is bundled with a WinPcap library. WinPcap is the industry-standard tool for link-layer network access in Windows environments: it allows applications to capture and transmit network packets bypassing the protocol stack, and has additional useful features, including kernel-level packet filtering, a network statistics engine and support for remote packet capture. WinPcap consists of a driver, that extends the operating system to provide low-level network access, and a library that is used to easily access the low-level network layers. This library also contains the Windows version of the well known libpcap Unix API. Since the WinPcap library cannot operate on 64-bit environments, the ClientTcpTest and ClientServiceTest will not function on 64-bit Windows clients.