The ns Manual (formerly ns Notes and Documentation)1 - NM Lab at ...
The ns Manual (formerly ns Notes and Documentation)1 - NM Lab at ... The ns Manual (formerly ns Notes and Documentation)1 - NM Lab at ...
Part IXVisualization with Nam - The NetworkAnimator389
Chapter 45Nam45.1 IntroductionNam is a Tcl/TK based animation tool for viewing network simulation traces and real world packet tracedata. The designtheory behind nam was to create an animator that is able to read large animation data sets and be extensible enough so that itcould be used indifferent network visualization situations. Under this constraint nam was designed to read simple animationevent commands from a large trace file. In order to handle large animtion data sets a minimum amount of information is keptin memory. Event commands are kept in the file and reread from the file whenever necessary.The first step to use nam is to produce the trace file. The trace file contains topology information, e.g., nodes, links, as wellas packet traces. The detailed format is described in the section 46.1. Usually, the trace file is generated by ns. During anns simulation, user can produce topology configurations, layout information, and packet traces using tracing events in ns.However any application can generate a nam trace file.When the trace file is generated, it is ready to be animated by nam. Upon startup, nam will read the tracefile, create topology,pop up a window, do layout if necessary, and then pause at time 0. Through its user interface, nam provides control over manyaspects of animation. These functionalities will be described in detail in the USER INTERFACE section.There are bugs in nam however each successive has become much more stable than the previous one. Please mail nsusers@isi.eduif you encounter any bugs, or have suggestions for addiotional desired functionality.45.2 Nam Command Line Optionsnam [ -g ] [ -t ] [ -i ] [ -j ][ -k ] [ -N ] [ -c ][ -f ] [ -r initial animation rate ][ -a ] [ -p ] [ -S ][ ]Command Line Options390
- Page 339 and 340: set src [new Agent/UDP]set sink [ne
- Page 341 and 342: Application FTP FTP objects produce
- Page 343 and 344: send_data(ADU)Application(HttpApp,
- Page 345 and 346: 39.1.4 Transmitting user data over
- Page 347 and 348: and teardown of connections. Only O
- Page 349 and 350: TclObjectPagePoolPagePool/CompMathP
- Page 351 and 352: PagePool/ProxyTrace takes these two
- Page 353 and 354: }int id_; // object IDWebTrafSessio
- Page 355 and 356: An Http/Server object waits for inc
- Page 357 and 358: set tmp [new RandomVariable/Exponen
- Page 359 and 360: Object Type Event Type Explaination
- Page 361 and 362: Chapter 40Worm ModelIn this chapter
- Page 363 and 364: $w local-p 0.5Following are some co
- Page 365 and 366: (nsnode) clientcloudPackM ime(nsnod
- Page 367 and 368: HTTP responsesclients servers Delay
- Page 369 and 370: 41.5 Commands at a GlanceThe follow
- Page 371 and 372: • HTTP response size (bytes)• s
- Page 373 and 374: Chapter 42Session-level Packet Dist
- Page 375 and 376: 42.1.2 Inserting a Loss ModuleWhen
- Page 377 and 378: Delay and Loss Modules Each receive
- Page 379 and 380: Chapter 43Asim: approximate analyti
- Page 381 and 382: set n(1) [$ns node]set link(0:1) [$
- Page 383 and 384: Part VIIIEmulation382
- Page 385 and 386: When using the emulation mode, a sp
- Page 387 and 388: set intf [$pf1 open readonly]puts "
- Page 389: puts "install nets into taps..."$a0
- Page 393 and 394: • Button 6 (Chevron logo) - Close
- Page 395 and 396: Second, when dealing with randomly
- Page 397 and 398: dst_portaddr,seqno,flags,sname);A n
- Page 399 and 400: • up• down• right• left•
- Page 401 and 402: 46.1.7 Agent TracingAgent trace eve
- Page 403 and 404: v -t 1.0 -e node_tclscript 2 "Echo
- Page 405 and 406: If nam ever gets to the end of an e
- Page 407 and 408: l :link-t time-s source id-d des
- Page 409 and 410: E :D :P :a :session enqueue-t time
- Page 411 and 412: v :V :N :W :g :A :c :q :execute tcl
- Page 413 and 414: $ns duplex-link-op orient right$ns
- Page 415 and 416: Chapter 47Educational use of NS and
- Page 417 and 418: Bibliography[1] C. Alaettinoğlu, A
Chapter 45Nam45.1 IntroductionNam is a Tcl/TK based anim<strong>at</strong>ion tool for viewing network simul<strong>at</strong>ion traces <strong>and</strong> real world packet traced<strong>at</strong>a. <strong>The</strong> designtheory behind nam was to cre<strong>at</strong>e an anim<strong>at</strong>or th<strong>at</strong> is able to read large anim<strong>at</strong>ion d<strong>at</strong>a sets <strong>and</strong> be exte<strong>ns</strong>ible enough so th<strong>at</strong> itcould be used indifferent network visualiz<strong>at</strong>ion situ<strong>at</strong>io<strong>ns</strong>. Under this co<strong>ns</strong>traint nam was designed to read simple anim<strong>at</strong>ionevent comm<strong>and</strong>s from a large trace file. In order to h<strong>and</strong>le large animtion d<strong>at</strong>a sets a minimum amount of inform<strong>at</strong>ion is keptin memory. Event comm<strong>and</strong>s are kept in the file <strong>and</strong> reread from the file whenever necessary.<strong>The</strong> first step to use nam is to produce the trace file. <strong>The</strong> trace file contai<strong>ns</strong> topology inform<strong>at</strong>ion, e.g., nodes, links, as wellas packet traces. <strong>The</strong> detailed form<strong>at</strong> is described in the section 46.1. Usually, the trace file is gener<strong>at</strong>ed by <strong>ns</strong>. During an<strong>ns</strong> simul<strong>at</strong>ion, user can produce topology configur<strong>at</strong>io<strong>ns</strong>, layout inform<strong>at</strong>ion, <strong>and</strong> packet traces using tracing events in <strong>ns</strong>.However any applic<strong>at</strong>ion can gener<strong>at</strong>e a nam trace file.When the trace file is gener<strong>at</strong>ed, it is ready to be anim<strong>at</strong>ed by nam. Upon startup, nam will read the tracefile, cre<strong>at</strong>e topology,pop up a window, do layout if necessary, <strong>and</strong> then pause <strong>at</strong> time 0. Through its user interface, nam provides control over manyaspects of anim<strong>at</strong>ion. <strong>The</strong>se functionalities will be described in detail in the USER INTERFACE section.<strong>The</strong>re are bugs in nam however each successive has become much more stable than the previous one. Please mail <strong>ns</strong>users@isi.eduif you encounter any bugs, or have suggestio<strong>ns</strong> for addiotional desired functionality.45.2 Nam Comm<strong>and</strong> Line Optio<strong>ns</strong>nam [ -g ] [ -t ] [ -i ] [ -j ][ -k ] [ -N ] [ -c ][ -f ] [ -r initial anim<strong>at</strong>ion r<strong>at</strong>e ][ -a ] [ -p ] [ -S ][ ]Comm<strong>and</strong> Line Optio<strong>ns</strong>390