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
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
|
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252">
<META NAME="Generator" CONTENT="Microsoft Word 97">
<TITLE>Internet Performance Measurement and Analysis (IPMA)</TITLE>
</HEAD>
<BODY>
<I><FONT FACE="Arial" SIZE=4><STRONG><P ALIGN="CENTER"> </P>
<P ALIGN="CENTER">Internet Performance Measurement and Analysis (IPMA)</P>
<P ALIGN="CENTER"> </P>
</I></FONT></STRONG><B><FONT FACE="Arial" SIZE=7><EM><P ALIGN="CENTER">Internet Statistics Toolset </P>
<P ALIGN="CENTER">User Guide</P>
</B></FONT></EM><I><FONT FACE="Arial" SIZE=6><STRONG><P ALIGN="CENTER">Version 1.0 Alpha</P>
</FONT><FONT FACE="Arial" SIZE=4><P ALIGN="CENTER"> </P>
<P ALIGN="CENTER"> (Draft 4/14/98 3:24 PM)</P>
<P ALIGN="CENTER"> </P>
</STRONG><B><P ALIGN="CENTER"> </P>
</B></I></FONT><FONT SIZE=7><STRONG><P> </P>
<P> </P>
<P> </P>
<H1> </H1>
</FONT><H1><A NAME="_Toc412453973"><A NAME="_Toc414767366">Table of Contents</A></A> <DIR>
</STRONG><FONT SIZE=2><P>Table of Contents	</FONT><A HREF="#_Toc414767366">*</A></P>
<FONT SIZE=2><P>Introduction	</FONT><A HREF="#_Toc414767367">*</A></P>
<FONT SIZE=2><P>Document Conventions	</FONT><A HREF="#_Toc414767368">*</A></P>
<FONT SIZE=2><P>Getting Help	</FONT><A HREF="#_Toc414767369">*</A></P>
<FONT SIZE=2><P>Credits	</FONT><A HREF="#_Toc414767370">*</A></P>
<FONT SIZE=2><P>1. Overview	</FONT><A HREF="#_Toc414767371">*</A></P>
<FONT SIZE=2><P>2. ASExplorer	</FONT><A HREF="#_Toc414767372">*</A></P>
<FONT SIZE=2><P>Main Window	</FONT><A HREF="#_Toc414767373">*</A></P>
<FONT SIZE=2><P>Real-Time Graphs	</FONT><A HREF="#_Toc414767374">*</A></P>
<FONT SIZE=2><P>Table of Current Flapping Prefixes	</FONT><A HREF="#_Toc414767375">*</A></P>
<FONT SIZE=2><P>3. NetNowd	</FONT><A HREF="#_Toc414767376">*</A></P>
<FONT SIZE=2><P>Synopsis	</FONT><A HREF="#_Toc414767377">*</A></P>
<FONT SIZE=2><P>Options	</FONT><A HREF="#_Toc414767378">*</A></P>
<FONT SIZE=2><P>Description	</FONT><A HREF="#_Toc414767379">*</A></P>
<FONT SIZE=2><P>Sample Configuration File	</FONT><A HREF="#_Toc414767380">*</A></P>
<FONT SIZE=2><P>Configuration Commands	</FONT><A HREF="#_Toc414767381">*</A></P>
<FONT SIZE=2><P>Interactive Interface Commands	</FONT><A HREF="#_Toc414767382">*</A></P>
<FONT SIZE=2><P>Viewing the Results	</FONT><A HREF="#_Toc414767383">*</A></P>
<FONT SIZE=2><P>Related Documents	</FONT><A HREF="#_Toc414767384">*</A></P>
<H1> </H1></DIR>
</H1>
<FONT SIZE=7><STRONG><P> </P>
</FONT></STRONG><B><FONT SIZE=5><P><A NAME="_Toc410609076">Copyright (c) 1997, 1998</P>
</B></FONT><FONT FACE="Courier" SIZE=3><P> </P>
<P> </P>
<P>The Regents of the University of Michigan ("The Regents") and Merit Network, Inc. All rights reserved.<BR>
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:</P>
<P>1. Redistributions of source code must retain the above <BR>
copyright notice, this list of conditions and the <BR>
following disclaimer.</P>
<P>2. Redistributions in binary form must reproduce the above <BR>
copyright notice, this list of conditions and the <BR>
following disclaimer in the documentation and/or other <BR>
materials provided with the distribution.</P>
<P>3. All advertising materials mentioning features or use of <BR>
this software must display the following acknowledgement:</P><DIR>
<DIR>
<P>This product includes software developed by the University of Michigan, Merit Network, Inc., and their contributors.</P></DIR>
</DIR>
<P>4. Neither the name of the University, Merit Network, nor the<BR>
names of their contributors may be used to endorse or <BR>
promote products derived from this software without <BR>
specific prior written permission.</P>
<P>THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. </P>
</FONT><P ALIGN="JUSTIFY"></A></P>
<H2><A NAME="_Toc414767367">Introduction</A></H2>
<FONT SIZE=2><P>This chapter introduces the <I>IPMA User Guide</I> and explains how to obtain further information about the project.</P>
</FONT><H3><A NAME="_Toc414767368">Document Conventions</A></H3>
<FONT SIZE=2><P>The following document conventions are used in the <I>User Guide:</P>
<P> </P>
<UL>
</I><LI>Commands and keywords are in <B>boldface</B>.</LI>
<LI>User-supplied variables are enclosed in <angle brackets>.</LI>
<LI>Optional elements are shown in [square brackets].</LI>
<LI>Alternative but required keywords are grouped in {braces} and separated by a vertical bar.</LI></UL>
</FONT><H3><A NAME="_Toc414767369">Getting Help</A></H3>
<FONT SIZE=2><P>For more information about IPMA, send mail to ipma-support@merit.edu. </P>
<P> </P>
<P>The IPMA development teams are available to answer questions and provide configuration advice. We are also very interested in bug reports, feature requests, and general feedback.</P>
<P> </P>
<P>A mailing list, ipma-discuss-request@merit.edu is also available for IPMA users to share advice and experiences with the toolkit.</P>
</FONT><H3><A NAME="_Toc414767370">Credits</A></H3>
<FONT SIZE=2><P>The Internet Performance Measurement and Analysis (IPMA) project is supported by National Science Foundation grant NCR-9710176, a gift from Intel Corporation. </P>
<P> </P>
<P>The University of Michigan/Merit Network IPMA development team includes: Craig Labovitz, Farnam Jahanian, Rob Malan, Susan Rebecca Harris, Scott Johnson, Jimmy Wan, Aaron Klink, Mukesh , and Nancy Scala.</P>
<P> </P>
<P>The IPMA team would also like to thank other colleagues who have made major contributions to the project: John Hanley (Yahoo), K. Claffy (CAIDA), Curtis Villamizar (ANS), and Jay Brock (AT&T).</P>
</FONT><H2><A NAME="_Toc414767371">1. Overview</A></H2>
<FONT SIZE=2><P> </P>
<P>The Internet Performance Measurement and Analysis project is a joint effort of Merit Network, Inc., and the Department of Electrical Engineering and Computer Science at the University of Michigans College of Engineering. </P>
<P> </P>
<P>IPMA focuses on two primary areas of Internet statistics: routing stability, topology, and visualization; and provider performance measurements. The overall goal of the project is to develop tools and perform statistical research that promotes the stability and rational growth of the Internet. </P>
<P> </P>
<P>The IPMA project works closely with the Cooperative Association for Internet Data Analysis (CAIDA) and the National Laboratory for Applied Network Research (NLANR) to create a shared measurement infrastructure for the U.S. Internet. </P>
<P> </P>
<P> </P>
<P> </P>
<P> </P>
<P> </P>
</FONT><H2> </H2>
<H2><A NAME="_Toc414767372">2. ASExplorer</A></H2>
<FONT SIZE=2><P>The ASExplorer applet queries the Route Server systems at the five major U.S. inter-exchange points (IXPs) and determines how many BGP routing announcements have been made by each of the Route Servers' peers in the last 75 minutes. Currently, ASExplorer can display statistics from MAE-East (Washington, D.C.), MAE-West (San Francisco area), the Ameritech Network Access Point (AADS, in Chicago), the Digital Internet Exchange (PAIX), in Palo Alto), and the PacBell NAP in San Francisco.</P>
<P>ASExplorer uses the Salamander data distribution system to provide updated information via a real-time push webcasting system. Users simply launch the Java applet, click on an AS, and follow the links to display the number of announcements made by successive layers of neighbor ASs. </P>
<P> </P>
<P><IMG SRC="Image2.gif" WIDTH=719 HEIGHT=516>Once you launch the Java applet, it may take a minute or so for the new window to appear on your screen. In the applet window, you'll see a black box representing the AS that is your current "vantage point" in the Internet topology. BGP announcements are made right-to-left, with upstream ASs to the right of the vantage point AS, and downstream ASs to the left. </P>
<P> </P>
</FONT><H3><A NAME="_Toc414767373">Main Window</A> </H3>
<FONT SIZE=2><P> </P>
<P>By default, a red box in the main window (shown above) indicates that the AS has made over 75 BGP routing announcements in the last 75 minutes. Orange indicates over 16 announcements, and so on. Users can easily change the color coding to use any system preferred. Similarly, the user can change the value at which ASExplorer will filter out data. For example, by default, only AS's that make more than 4 BGP announcements will be displayed. </P>
<P> </P>
<P> </P>
</FONT><H3><A NAME="_Toc414767374">Real-Time Graphs</A> </H3>
<FONT SIZE=2><P>By choosing 'Show Graph of Current Instability Levels', you can display instability graphs that are constantly updated in real-time. The graph plots the aggregate number of BGP announcements and withdraws in 15 minute intervals seen at the Route Servers today. </P>
<P> </P>
</FONT><H3><A NAME="_Toc414767375">Table of Current Flapping Prefixes</A> </H3>
<FONT SIZE=2><P>By Choosing 'Show Current Flapping Prefixes' under 'Show Data', you can view a table detailing the number of BGP announcements and withdrawals recieved from each Route Server peer during the last fifteen minutes. </P>
<P> </P>
</FONT><H2><A NAME="_Toc409238199"><A NAME="_Toc409241010"><A NAME="_Toc413226747"></H2>
<H2><A NAME="_Toc414767376">3. NetNowd</A></H2>
<H3><A NAME="_Toc414767377">Synopsis</A></H3>
<B><FONT SIZE=2><P>netnowd [-v] [-f config file] </P>
</B></FONT><H3><A NAME="_Toc414767378">Options</A></H3>
<B><FONT SIZE=2><P>-f config_file </P><DIR>
</B><P>Specify the configuration file to use. By default, NetNowd looks in /etc/netnowd.config. </P></DIR>
<B><P>-v </P><DIR>
</B><P>verbose logging </P></DIR>
</FONT><H3><A NAME="_Toc414767379">Description</A></H3>
<P>NetNowd collects network performance statistics information and reports real-time results to one or more Statistics servers (SalServer). In turn, reporting tools and Java clients can connect to a statistics server to generate real-time and historical reports of network performance. NetNowd is the back-end tool for a number of visualization clients, including ASExplorer, FlapGraph and TopologyNow. See the IPMA web site (http://www.merit.edu/ipma) for more information about the visualization tools.</P>
<P>This release of NetNowd includes support for the following network measurements: </P>
<UL>
<FONT SIZE=2><LI>One-way latency (IETF IPPM working group) </LI>
<LI>One-way loss (IETF IPPM working group) </LI>
<LI>ICMP pings </LI>
<LI>Bulk file transfer <BR>
</LI></UL>
</FONT><P>NetNowd first reads its configuration file (by default /etc/netnowd.config) to configure security controls, plink streams and other measurements. If a configuration file does not exist on disk, NetNowd will create a default configuration in volatile memory. The configuration file strongly resembles the files used by Cisco Systems. </P>
<P>After reading the configuration file, NetNowd will begin network measurement tests and report the results to the one or more configured statistics servers. NetNowd will also listen on the UII port for user telnet connections (specified in /etc/services as the TCP port for "netnowd"). </P>
<P>The daemon has been set up to run in a default configuration "out of the box". You should simply be able to download the binary and run it. If you want more control over what the daemon does (such as which machines it peers with, how it outputs error and diagnostic information, and security features) you will need to edit the configuration file. By default, the daemon participates in an "Alpha" community of NetNowd testers and publishes performance data to a public statistics server (currently based at Merit Network, Inc.).</P>
<P>Note that if you want to specify the next hop of a plink packet, or if you want to do a local (subnet) plink, you will need to run the NetNow daemon as root.</P>
<P>Below is an example of starting the NetNowd daemon from the command line:</P><DIR>
<DIR>
<CODE><P>snoopy% ./netnowd -v</P>
<P>Jan 14 22:11:00 [1] Netnowd opened the config file /etc/netnowd.config</P>
<P>Jan 14 22:11:00 [1] CONFIG: password foo 0</P>
<P>Jan 14 22:11:00 [1] CONFIG community um_campus added</P>
<P>Jan 14 22:11:01 [1] CONFIG salamander host zounds.merit.net (198.108.0.13) with key 123456</P>
<P>Jan 14 22:11:01 [1] Allowing unconfigured peers</P>
<P>Jan 14 22:11:01 [1] Listening for plink packets on port 5670 (socket 0)</P>
<P>Jan 14 22:11:01 [1] ERROR ** could not open hme **</P>
<P>Jan 14 22:11:01 [1] ** Physical interface unavailable. **</P>
<P>Jan 14 22:11:01 [1] UII listening for connections on port 5674 (socket 6)</P>
<P>Jan 14 22:11:01 [1] Attempting connect to Salamander Server zounds.merit.net (key 123456)</P>
<P>Jan 14 22:11:01 [1] Salamander connection made!</P>
<P>Jan 14 22:11:01 [1] SALAMANDER query um_campus</P>
<P>Jan 14 22:11:01 [1] SALAMANDER query NetNow:Stats</P>
<P>Jan 14 22:11:01 [4] SALAMANDER recv community: um_campus, type: uping, data: compute.merit.edu zax.eecs.umich.edu zounds.merit.net snoopy.merit.net mrt.merit.edu zowie.merit.edu</CODE><FONT SIZE=2> <BR>
</P></DIR>
</DIR>
</FONT><P>Notice in the above example that we did not run NetNowd as root, and the daemon could not obtain access to the ethernet (hme) interface. Lacking this access, the NetNowd probe will only be able to send UDP packets via the default route.</P>
<H3><A NAME="_Toc414767380">Sample Configuration File</A> </H3>
<P>A sample NewNowd configuration file is shown on the next page.</P><DIR>
<DIR>
<PRE>!####################################################################
! NetNowdMRT version 1.4.1 ALPHA December 17, 1997
!####################################################################
!
debug all /var/tmp/netnowd.log 1000
!
password blechy 1
!
source_ip 192.41.177.169 /dev/le ethernet
!
! The sites we plink and accept plinks from
!
community alpha
!
! Salamander Server
salserver zounds.merit.net 123456
!
allow unconfigured-peers
!
!
plink_subnet 192.41.177.181 tag 3561 # MCI
plink_subnet 192.41.177.80 tag 5000 # IOSnet
plink_subnet 192.41.177.87 tag 4969 # NetAxs
!
access-list 1 198.108.60.0 permit
access-list 1 141.213.8.0 permit
!###################################################################</PRE></DIR>
</DIR>
<P> </P>
<H3><A NAME="_Toc414767381">Configuration Commands</A></H3>
<P>Configuration commands are used to configure NetNowd; interactive interface (telnet) commands are used to show and modify the status of various metrics, such as packet latency and loss. </P>
<U><P>A WARNING </U> Most, but not all, configuration commands may be issued even through the interactive, telnet interface. In this alpha release of NetNowd, the modification of volatile memory occasionally may have unintended side effects. In rare instances, the alteration of some volatile memory setting may crash the application. We recommend most configuration changes be made directly to the configuration file on disk. The program must be restarted, or <B>rebooted</B>, to reread the changed configuration file. Improved support for configuration management will be available with the next release of NetNowd.<BR>
</P>
<B><P>uii</B>configures the user interface (by telnet)</P>
<B><FONT SIZE=2><P>uii_password <string> <access-list number></P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Sets a password <string> for telnet interface. Note that if a password is not set, access verification will not be performed and interactive user telnet connections will be disabled. If <access-list number> is specified, telnet connections will be restricted to IP addresses allowed by the access list. See the access-list description below for more information.</P></DIR>
</DIR>
</DIR>
</DIR>
<B><P>uii port <number> </P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Changes the port number with <number> for the telnet interface. The default is the port value specified in /etc/services for the application name. If a /etc/services entry does not exist, the port number assigned to the service defaults to "mrt" or 5674.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>debug</B>controls debug options</P>
<B><FONT SIZE=2><P>debug <flag> [<file> [<size>]]</P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Logs debug messages specified <flag> to <file>. If the limit is specified with <size>, the file will be truncated after reaching at the limit. If <file> is omitted, stderr will be chosen.</P></DIR>
</DIR>
</DIR>
</DIR>
<PRE> <flag></FONT><B> .... info, norm, trace, parse, packet, state, timer, all
<file> .... filename or "stdout".
		 Some applications also support "syslog"
			
</PRE>
<P>access-list</B>defines a filter</P>
<B><FONT SIZE=2><P>access-list <number> {permit|deny} <prefix> [refine|exact]</P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Defines an access list <number>, which permits or denies access if the condition is matched. <B>all</B> can be specified as <prefix>. <B>exact</B> will be assumed if neither <B>refine</B> or <B>exact</B> is specified. <B>exact</B> matches only the prefix, while <B>refine</B> matches more specific prefixes, excluding the prefix itself.</P>
<P>Matches are performed in the order in which they appear. At the end of a list with the same number, <B>permit all</B> is assumed.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>!</B>comment and separator</P><DIR>
<DIR>
<FONT SIZE=2><P>Comments can appear at the beginning of a line, or any other place in the line. A comment at the beginning of a line is treated as a separator, which ends a command clause followed by its sub-commands, such as router and interface.</P></DIR>
</DIR>
</FONT><B><P>redirect</B>allows shell-like redirection of output (> or >>).</P><DIR>
<DIR>
<B><FONT SIZE=2><P>redirect</B> <directory></P><DIR>
<DIR>
<P>Allows redirection to files in this directory. Unrestricted redirection was deemed a security problem.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>plink</B>define a remote plink host</P>
<B><FONT SIZE=2><P>plink <hostname> [via <next_hop] [tag <numner>]</P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Sends a one-way UDP stream to the specified host. If next hop is specified, NetNowd will encapsulate the UDP packets in a MAC-level packet destined for the nexthop interface.</P>
<P>If tag is specified, NetNowd will "tag" all UDP packets with this number. A tag is generally used to allow client visualization tools to distinguish between multiple plink streams between the same two hosts utilizing different nexthops.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>plink_subnet</P>
<FONT SIZE=2><P>plink_subnet <hostname> tag <number></P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Sends a one-way UDP stream to the interface of a machine on the same subnet</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>community</B>define a community</P>
<B><P>community </P><DIR>
<DIR>
<DIR>
<DIR>
</B><FONT SIZE=2><P>NetNowd queries the statistics server for all hosts belonging to this community. The community identifies both machine name, as well as the test to perform (plink, icmp, etc). After recieiving a response from the statistics server, NetNowd will initiate the specified test.</P>
<P>At the moment, there is no convenient way to add machines to a community. Send mail to ipma-support@merit.edu if you would like a machine added.</P>
<P>By default, NetNowd uses "alpha" as the test community.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>salserver</B>specify the Statistics server</P>
<B><FONT SIZE=2><P>salserver <hostname> <number></P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Publish results of network performance tests to <hostname>. The <number> field is a security key (currently unused).</P>
<P>NetNowd also requires a statistics to query for information about communities.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>packet_size</B>specify the packet size of all plink packets</P>
<B><FONT SIZE=2><P>packet_size <number></P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Set the size of all plink packets as <number>. There is currently no way to set the size of a packet for a specific plink stream.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><P>interval</B>specify the inter-transmission time of plink packets</P>
<B><FONT SIZE=2><P>interval <number> jitter <number></P><DIR>
<DIR>
<DIR>
<DIR>
</B><P>Set the delay between plink packets as <number> of milliseconds. Add a random value with a maxmimum of <number> jitter milliseconds to the delay on each transmission.</P></DIR>
</DIR>
</DIR>
</DIR>
</FONT><B><PRE> </PRE>
</B><H3><A NAME="_Toc414767382">Interactive Interface Commands</A></H3>
<P>NetNowd provides an interactive telnet user interface for configuration and display/management of various statistics and measurement parameters. </P>
<P>The port number can be specified in the configuration file, or in /etc/services ("netnowd"). The default port is 5674. If a password is specified in the configuration, it must be supplied on logging in. </P>
<P>Unix shell-like redirection ( or filename) is available for output. To edit a line, emacs-like line editing including ^b, ^f, ^d, ^k, ^u and ^c is available. To reuse a previous line, tcsh-line history function is available by typing ^p and ^n. </P>
<P>The following commands are available from the user interface.</P>
<B><PRE></PRE>
<UL>
<LI>show community</B>Show community of machines in statistics mesh</LI>
<B><LI>show config</B>Display current configuration</LI>
<B><LI>show plink</B>Show machines we are plinking</LI>
<B><LI>show stats</B>Show netnow statistics</LI>
<B><LI>show timers</B>Show status of NetNow timers</LI></UL>
<B><P> </P>
</B><P>Below is an example of several netnowd user interface commands:</P>
<B><P> </P><DIR>
</B><CODE><P>[ 9] NETNOWD> show stats</P>
<P>SalServer: zounds.merit.net (9) [Connected]</P>
<P>Send Update Timer: (5) Recv Update Timer: (5)</P>
<P>Last update from NADMIN Server on zounds.merit.net (8)</P>
<P> </P>
<P> Destination Sent Recv Delay </P>
<P> ----------- ---- ---- ----- </P>
<P> home.merit.edu 115 0 -</P>
<P> zowie.merit.edu 119 0 -</P>
<P>* zax.eecs.umich.edu - - -</P>
<P> compute.merit.edu 119 119 -</P>
<P> zounds.merit.net 119 119 567.9 67580</P>
<P> snoopy.merit.net 120 120 -</P>
<P> mrt.merit.edu 117 0 -</P>
<P>Interval 500ms Jitter 200ms</P></DIR>
</CODE><H3><A NAME="_Toc414767383">Viewing the Results</A></H3>
<P>A number of client applications are available for viewing and monitoring NetNow performance data. NetNowGraph is a Java application that graphs latency/loss information between a given source probe and destination over the course of a day. NetNowReport is a Perl program that shows the latency/loss information from a given source to all destinations over the course of a day. Both tools are distributed with the IPMA Internet Performance Toolkit at http://www.merit.edu/ipma/tools. A version of NetNowReport is also distributed with the NetNowd source code.</P>
<FONT SIZE=2><P> </P>
<P><IMG SRC="Image3.gif" WIDTH=669 HEIGHT=369></P><DIR>
<DIR>
<DIR>
<DIR>
<DIR>
<DIR>
<DIR>
<DIR>
</FONT><B><P>NetNow Visualization Tool</P>
</B><FONT SIZE=2><P> </P></DIR>
</DIR>
</DIR>
</DIR>
</DIR>
</DIR>
</DIR>
</DIR>
</FONT><H3><A NAME="_Toc414767384">Related Documents</A></H3><DIR>
<DIR>
<P>Almes, G., Mathis, M., Mahdavi, J. and V. Paxson. "Framework for IP Performance Metrics" (ftp://ietf.org/internet-drafts/draft-ietf-ippm-framework-01.txt). Defines a general framework for particular metrics to be developed by the IETF's IP Performance Metrics (IPPM) Working Group.</P>
<P>Almes, Guy and S. Kalidindi, "A One-way Delay Metric for IPPM." (ftp://ietf.org/internet-drafts/draft-ietf-ippm-delay-01.txt).</P>
<H2> </H2></DIR>
</DIR>
<H2></A></A></A></H2>
<FONT SIZE=2><P> </P></FONT></BODY>
</HTML>
|
