This repository was archived by the owner on Oct 5, 2022. It is now read-only.
forked from ndt-project/ndt
-
Notifications
You must be signed in to change notification settings - Fork 8
Expand file tree
/
Copy pathadmin.html
More file actions
217 lines (216 loc) · 8.88 KB
/
admin.html
File metadata and controls
217 lines (216 loc) · 8.88 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
<html> <title>NDT server Admin Page</title>
<meta http-equiv="refresh" content=30 url=admin.html>
<table border>
<tr>
<th colspan=8><font size=+1>NDT Usage Statistics -- Current Test Results
</font></tr>
<tr>
<th>Date/Time
<th>Total Tests
<th rowspan=6>
<th>Bottleneck Link
<th>Theoritical Limit
<th rowspan=6>
<th>C2S Speed
<th>S2C Speed
</tr>
<tr>
<td align=right>Nov 30 12:09:56
<td align=right>112
<td align=right>FastEthernet
<td align=right>4934.51 Mbps
<td align=right>33.06 Mbps
<td align=right>21.89 Mbps
</tr>
<tr>
<th>Packet Loss
<th>Average RTT
<th>Mininum RTT
<th>Retrans/sec
<th>Timeouts/sec
<th>% Out-of-Order
</tr>
<tr>
<td align=right>None
<td align=right>2.26 msec
<td align=right>0 msec
<td align=right>0.00
<td align=right>0.00
<td align=right>3.18
</tr>
<tr>
<th>Send Buffer
<th>BW*Delay
<th>Receive Buffer
<th>BW*Delay
<th>Congestion Window
<th>BW*Delay
</tr>
<tr>
<td align=right>65535 Bytes
<td align=right>232.25 Mbps
<td align=right>32768 Bytes
<td align=right>116.13 Mbps
<td align=right>33580 Bytes
<td align=right>119.01 Mbps
</tr>
</table>
<applet codebase=Admin code=edu.internet2.ndt.Admin.class
width=600 height=400>
<PARAM NAME="Fault" VALUE="9">
<PARAM NAME="RTT" VALUE="0">
<PARAM NAME="Dial-up" VALUE="0">
<PARAM NAME="T1" VALUE="1">
<PARAM NAME="Enet" VALUE="4">
<PARAM NAME="T3" VALUE="0">
<PARAM NAME="FastE" VALUE="98">
<PARAM NAME="OC-12" VALUE="0">
<PARAM NAME="GigE" VALUE="0">
<PARAM NAME="OC-48" VALUE="0">
<PARAM NAME="tenGE" VALUE="0">
<PARAM NAME="Total" VALUE="112">
</applet>
<br>
<table border>
<tr>
<th>
<th>Date/Time
<th rowspan=5>
<th colspan=2>Throughput Summary
<th rowspan=5>
<th colspan=2>Configuration Fault Summary
</tr>
<tr>
<td><b>Log Starts</b>
<td align=right>Jul 2 15:31:08
<th>Client-to-Server
<th>Server-to-Client
<th>Duplex Mismatch
<th>Excessive Errors
</tr>
<tr>
<td><b>Current</b>
<td align=right>Nov 30 12:09:56
<td align=right>33.06 Mbps
<td align=right>21.89 Mbps
<td align=right>No
<td align=right>No
</tr>
<tr>
<td><b>Maximum</b>
<td align=right>Jul 7 16:42:31
<td align=right>91.96 Mbps
<td align=right>93.69 Mbps
<td align=right>0 found
<td align=right>0 found
</tr>
<tr>
<td><b>Minimum</b>
<td align=right>SEP 26 14:50:57
<td align=right>244 kbps
<td align=right>304 kbps
<td>
<td>
</tr>
</table>
<br><br>
<hr width=100% noShade size=4>
<h2 align=center>NDT Usage Statistics - Description</h2>
<p>This page provides a summary view of how often the NDT server is used
and what problems it has found. The purpose is to allow NDT administrators
and users to monitor the health of the NDT server.
<p>The page contains:
<ul>
<li>A <b>Current Test Results</b> summary table. This table shows several
important results from the latest user test.
<li>A graph showing the <b>Bottleneck Link</b> distribution. This graph
shows the usage distribution broken down by the slowest link in the
end-to-end path.
<li>A <b>Historical Summary</b> table. This table shows a summary of several
NDT variables.
<li>A description of the tables and graphs.
</ul>
<br>
<h3>Current Test Results</h3>
<p>This table provides insite into how the last NDT client performed. It provides the
administrator with some of the basic troubleshooting information that was displayed
in the users desktop browser. The table contains the following fields:
<p><b>Date/Time</b> - The date and time of the latest test.
<p><b>Total</b> - The total number of tests recorded in the <i>web100srv.log</i> file.
<p><b>Bottleneck Link</b> - The slowest link in the end-to-end path as determined by
the NDT Link detection algorithm>
<p><b>Theoritical Limit</b> - The maximum throughput that a connection could achieve
over the end-to-end path. This value is calculated using web100 values for
Round-Trip-Time, Packet size, and Packet loss. A properly functioning TCP
implementation will never exceed this value. This value does not take the
physical network interface speeds into account. This value is meaningful when
packet loss rates are large, RTT's are big, or packet sizes are small.
<p><b>C2S Speed</b> - The Client-to-Server throughput measured by the NDT.
<p><b>S2C Speed</b> - The Server-to-Client throughput measured by the NDT.
<p><b>Packet Loss</b> - The packet loss calculated by the NDT using the Web100 variables.
<p><b>Average RTT</b> - The average Round Trip Time (RTT) calculated by the NDT. This is the
time it takes a data packet to go from the NDT server to the desktop client and an
Ack packet to return to the NDT server.
<p><b>Minimum RTT</b> - The minimum Round Trip Time measured by the NDT server. The NDT
server uses a 10 msec resolution clock so values are rounded down to the closest
10 msec value.
<p><b>Retrans/sec</b> - The number of Packets Retransmitted per second over the 10 second
throughput test.
<p><b>Timeouts/sec</b> - Them number of times per second the TCP needed to retransmit
a packet based on the Timeout timer expiring.
<p><b>% Out of Order</b> - The percentage of packets that were received out-of-order.
This value is calculated based on the percentage of duplicate Ack packets that
were received that didn't result in a packet being retransmitted.
<p><b>Send Buffer</b> - The size, in Bytes, of the NDT server's transmit buffer.
<p><b>BW*Delay</b> - The Bandwidth * Delay product for the Send buffer. This value
is the maximum throughput that could be obtained over the end-to-end path
based on the NDT servers transmit buffer and the RTT of this path. This value
is meaningful if the connection is reported to be sender limited.
<p><b>Receive Buffer</b> - The size, in Bytes, of the Desktop Clients advertised receive
buffer.
<p><b>BW*Delay</b> - The Bandwidth * Delay product for the receive buffer. This value
is the maximum throughput that could be obtained over the end-to-end path
based on the Desktop Clients receive buffer and the RTT of this path. This
value is meaningful if the connection is reported to be receiver limited.
<p><b>Congestion Window</b> - The size, in Bytes, of the NDT servers congestion window (CWND)
variable.
<p><b>BW*Delay</b> - The Bandwidth * Delay product for the NDT servers maximum congestion
window (CWND) value. This value is the maximum throughput that could be obtained
over the end-to-end path based on the NDT servers CWND value and the RTT of this path.
This value is meaningful if the connection is reported to be Congestion Window limited.
<br>
<h3>Bottleneck Link Graph</h3>
<p>The NDT contains a link detection algorithm that determines the slowest physical link in
the end-to-end path. The end-to-end network path is composed of numerous physical links,
each with its own transmission rate. The NDT link detection algorithm attempts to determine
the slowest link in the end-to-end path. This information is used to determine if problems
exist or if the network is performing properly. This graph shows the distribution of bottleneck
link types reported by this detection algorithm. The X axis shows the different link types
the NDT is capable of detecting, the Y axis shows the percentage of connections that were
determined to be a specific link type, and the numbers listed over each bar show the total
number of connections of that type.
<br>
<h3>Historical Summary Statistics</h3>
<p>This table shows some historical summary statistics. They are generated based on data
stored in the <i>web100srv.log</i> log file. The NDT is designed to log numerous Web100
variable data to aid the NDT administartor in debugging problems. This table shows
some of the historical data collected in this log
<p><b>Log Starts</b> - The date and time of the first entry in the log file.
<p><b>Current</b> - The date/time and throughput values of the latest entry. Note: this is the same
as that in the Current Statistics table.
<p><b>Maximum</b> - The date/time and throughput values of the connection that achieved the
highest throughput since the Start Date.
<p><b>Minimum</b> - The date/time and throughput values of the connection that achieved the
lowest throughput since the Start Date.
<p><b>Duplex Mismatch</b> - A boolean flag that indicates if the current connection was reported
to have a duplex mismatch condition.
<p><b>Errors</b> - A boolean flag that indicates if the current connection was reported to
have an excessive error rate indicating a faulty NIC or patch cable.
<p><b>Total Mismatch</b> - The total number of duplex mismatch conditions detected since the
Start Date.
<p><b>Total Errors</b> - The total number of excessive error condition detected since the
Start Date.
<br>
<hr noshade size=3 width=100%>
<p>For more details contact Richard Carlson email:rcarlson501@comcast.net
</body></html>