12.07.2015 Views

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 ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

21.4 Test-suites for XCP<strong>The</strong> xcp test-suite uses 3 tests. <strong>The</strong> first one is similar to the one we discussed in the earlier section. It co<strong>ns</strong>ists of a dumb-belltopology where 3 xcp flows share a bottleneck link. <strong>The</strong> second test has a similar topology having 3 xcp <strong>and</strong> 1 tcp flow sharingthe same bottleneck. And finally the last test is built on Dina K<strong>at</strong>abi’s parking-lot experiment referred in her SIGCOMM’02paper. It is a dow<strong>ns</strong>ized version of Dina’s example. <strong>The</strong> test uses a 9-hop link string topology. It has 10 long XCP flows th<strong>at</strong>flow through the entire length of the chain topology. <strong>The</strong>n it has 10 XCP flows th<strong>at</strong> run through each hop, starting <strong>at</strong> (n-1)thhop <strong>and</strong> ending <strong>at</strong> nth hop <strong>and</strong> so on cre<strong>at</strong>ing the intermittent flows. And finally there are long XCP flows in the reversedirection, starting from the last (10th) node <strong>and</strong> ending in the first (1st) node. <strong>The</strong>re is a bottleneck <strong>at</strong> the middle of the chaintopology. Thus the third test employs a large <strong>and</strong> complex topology <strong>and</strong> shows the utiliz<strong>at</strong>ion, queue length <strong>and</strong> packet dropvalues <strong>at</strong> every link.21.5 Comm<strong>and</strong>s <strong>at</strong> a glanceFollowing is a list of comm<strong>and</strong>s used for xcp rel<strong>at</strong>ed simul<strong>at</strong>ion in <strong>ns</strong>.set xcp_src [new Agent/TCP/Reno/XCP]This comm<strong>and</strong> cre<strong>at</strong>es an XCP source agent.set xcp_dst [new Agent/TCPSink/XCPSink]This comm<strong>and</strong> cre<strong>at</strong>es an XCP sink.$<strong>ns</strong> duplex-link $R0 $R1 Mb ms XCPThis code cre<strong>at</strong>es a duplex link with specified b<strong>and</strong>width <strong>and</strong> link delay using an XCP router between node R0 <strong>and</strong> R1.$xcp_queue set-link-capacity This comm<strong>and</strong> propag<strong>at</strong>es the link b<strong>and</strong>width inform<strong>at</strong>ion to the xcp queue which uses it for the router feedback calcul<strong>at</strong>ion.set tfile [open tfile w]$xcp_queue <strong>at</strong>tach $tfileThis Tcl comm<strong>and</strong> allows a file to be <strong>at</strong>tached for tracing xcp queue parameters.$xcp_src <strong>at</strong>tach-trace $xcp_src tracevar This comm<strong>and</strong> allows the xcp sources to trace variables.$queue queue-sample-everyrtt $rtt_valueThis comm<strong>and</strong> allows the user to set rtt interval values <strong>at</strong> which variables like packet_drops <strong>and</strong> queue lengths are measured<strong>at</strong> the xcp queue.Queue/XCP set tcp_xcp_on_ 1This flag lets tcp <strong>and</strong> xcp flows to use the same xcp router. This flag is a temporary fix <strong>and</strong> should go away when dynamicqueue weights come into effect.207

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!