[chord] chord experiment on emulab

Wed Jul 12 16:45:55 EDT 2006

Hello,

This is a follow-up question to a question I asked before (the previous email is
attached below). Thanks to your suggestion, the -l argument to the lsd program
did make the chord node communication bypass the Emulab control network. But
currently in my new experiment, each emulab host has more than one network
interfaces. Is there any way for me to specify more than one network interfaces
or to specify which network interface should not be used? Thank you very much!

Thanks,
Yanyan :)

--------------------------------------------------------------------
Quoting Emil Sit <sit at MIT.EDU>:

> On Sun, 26 February 2006 at 21:32 (-0700), Yanyan Wang wrote:
> > by using the unqualified host name(host0) instead of fully qualified
> > name(host0.exp10.***.emulab.net). But it seems not. I used the "nodeq"
> program
> > to get the following information of node0 as follows:
>
> Try running lsd with the -l argument to specify what IP address you
> want lsd to bind its socket on.
>
> --
> Emil Sit / MIT CSAIL PDOS / http://pdos.csail.mit.edu/chord/
>

Hello Chord authors,

I met a problem in running chord on Emulab testbed. Could you please kindly help
me solve it? Thanks a lot!

I know that you have been doing experiments with Chord on Emulab. I also wish to
do some experiments with Chord on Emulab to evaluate my experiment automation
tool. But as you may have known, emulab has its "Control Network".
(http://www.emulab.net/tutorial/docwrapper.php3?docname=tutorial.html#Advanced)
Sometimes, applications will use this "control network" interface instead of
the interface in the experimental network. Now I met this problem, my
experiment setup is as follows:

1. I start up a chord node node0 on host0 port 27882: lsd ... -j host0:27882 -p
27882
2. I start up other 99 chord nodes on other hosts: lsd  ... -j host0:27882 -p
27882

I thought that I could bypass the "Control Network" in my experiment chord ring
by using the unqualified host name(host0) instead of fully qualified
name(host0.exp10.***.emulab.net). But it seems not. I used the "nodeq" program
to get the following information of node0 as follows:

=== predecessors
0.      8f740baa7956959e7080857d9373874f56706407 10.1.1.2 27882 0 453 336 26
-325 -289 519 532
1.      7eb5dd89f33913c94ef4fe27420a826cd208ecf5 pc135.emulab.net 27882 0 2025
509 16 217 293 100 900
2.      7b591201cffc9766fb131c6eae0509bc17fc3b59 10.1.1.18 27882 0 1367 622 13
345 127 2126 925
3.      752e1a71e6d112873c0c21ac479c6947513f94c0 pc143.emulab.net 27882 0 2412
589 17 257 -129 100 797
4.      7273289a234887df21407813d0b2104205c26d87 10.1.1.20 27882 0 0 0 0 1433
-380 205 873
5.      6ff31fa91674f7dff3b71da91f82d26d6d0b5aa5 pc142.emulab.net 27882 0 1916
614 21 -24 1157 157 892
6.      59f08310a62f99f2f2d1bb1dc8e225f215ed6ae0 10.1.1.30 27882 0 0 0 0 -45 -31
425 910
7.      4bffb42a8336a951b8416c1e9fb0d0c7c0b414df 10.1.1.32 27882 0 1861 0 1 1156
-232 585 805
8.      47028ebaac810847a501c1e7141a10dbdc8b325e pc44.emulab.net 27882 0 0 0 0
170 293 209 672
9.      465211db0e7773a408897f788845ef78e9faba3d pc133.emulab.net 27882 0 2374
427 3 78 198 1524 945
10.     30da14335b20e4050e5e100970871d6621f08e47 10.1.1.27 27882 0 1913 0 1 506
83 291 942
11.     2ffd55bf7a94ea6f3df18e35e4832de913f922e0 10.1.1.13 27882 0 1872 44 3 93
594 924 935
12.     2c05c0cfbd4fa43b11b0ff205b40a3bf4e1f7a6a 10.1.1.33 27882 0 0 0 0 298 61
1194 851
13.     2236ea456b33250fc6f89d1b821e320fa3317ace 10.1.1.6 27882 0 459 110 7 -12
645 1130 852
14.     178446944332367f006ab25e6d4095549f69bc0c pc46.emulab.net 27882 0 1722 0
1 170 646 768 793
15.     12055e43e72fa3b80175239e675af4def767ac28 pc131.emulab.net 27882 0 2563
469 9 5 -27 284 885
=== successors
0.      8f740baa7956959e7080857d9373874f56706407 10.1.1.2 27882 0 453 336 26
-325 -289 519 532
1.      98a05a7eef0be3f493c6fb147487b8847b5feadf pc48.emulab.net 27882 0 1693
353 38 371 573 776 912
2.      9a5034c35200d5628a77f684650426cc63fb966a pc140.emulab.net 27882 0 0 0 0
118 200 941 936
3.      9e67c335306b7354076bf5d2771c4d98032f5379 pc121.emulab.net 27882 0 1938
344 34 -342 138 476 870
4.      a237d25a6817934811691a8b7925cf1be3eda3dc 10.1.1.7 27882 0 475 91 12 739
933 383 836
5.      a5931986d500bf2266490b2944873cde386b42f6 pc138.emulab.net 27882 0 0 0 0
223 632 791 972
6.      bba6c75c0c39cb372583d27d7b1dc11f799be986 pc49.emulab.net 27882 0 2079 18
2 18 214 1149 807
7.      c7256e0fe5237b275f7fc0bb6485c3839ea6bb2f pc145.emulab.net 27882 0 2068
454 28 609 -135 130 895
8.      c8ca612f1257ad732b084d8d6eaa29b40ee4bfb0 10.1.1.21 27882 0 0 0 0 80 205
1728 849
9.      c9368520794f60ba152ff9e579ec41410fa0b2ed pc51.emulab.net 27882 0 2211
539 5 -172 324 635 792
10.     d5cbe7b5b310cdfcadc5f55c9836d4d71001c1f1 pc43.emulab.net 27882 0 0 0 0
88 -13 678 746
11.     d6e039cdaef909b977ad0f84410a7525cea94a56 pc141.emulab.net 27882 0 0 0 0
500 525 162 894
12.     e85127289d28f4235374814568541ec393072d27 10.1.1.8 27882 0 374 30 8 135
306 1019 797
13.     e900f77a79c6d5e13f3069d7b9eaaca9630d0e63 pc98.emulab.net 27882 0 2108
136 2 -441 262 244 -1
14.     f35cc96dc44097d013acc97b4907b287b77b57b7 pc130.emulab.net 27882 0 0 0 0
724 114 542 885
15.     f394f79c10e5324be52a860ed84b93e0ec239d0d pc62.emulab.net 27882 0 2738 25
2 550 658 630 908
16.     132f58b03e019328e1d30b6a5adbc09f2581c73 pc63.emulab.net 27882 0 0 0 0
133 253 401 813
=== fingers
0.      8f740baa7956959e7080857d9373874f56706407 10.1.1.2 27882 0 453 336 26
-325 -289 519 532
1.      98a05a7eef0be3f493c6fb147487b8847b5feadf pc48.emulab.net 27882 0 1693
353 38 371 573 776 912
2.      a237d25a6817934811691a8b7925cf1be3eda3dc 10.1.1.7 27882 0 475 91 12 739
933 383 836
3.      bba6c75c0c39cb372583d27d7b1dc11f799be986 pc49.emulab.net 27882 0 2079 18
2 18 214 1149 807
4.      d5cbe7b5b310cdfcadc5f55c9836d4d71001c1f1 pc43.emulab.net 27882 0 0 0 0
88 -13 678 746
5.      12055e43e72fa3b80175239e675af4def767ac28 pc131.emulab.net 27882 0 2563
469 9 5 -27 284 885

You could see that those entries with the form "pc*.emulab.net" is the "Control
Network" interface. It means that my chord ring still used control network
interfaces. Could you please suggest me some way to bypass the "Control
Network" interface? How could you solve this problem in your experiments on
Emulab? Thank you very much!

Thanks!
Yanyan :)