Changes between Version 7 and Version 8 of GeniTmixCalibTutorial
- Timestamp:
- 06/19/14 13:12:51 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GeniTmixCalibTutorial
v7 v8 22 22 23 23 == C Run Tmix Script == 24 The image loaded on the nodes has the tmix tools already installed and in your path. Each time the system boots, a kernel module is automatically inserted to assist in simulating the packet delays. Issue the following command to run a Tmix setup script24 1. The image loaded on the nodes has the tmix tools already installed and in your path. Each time the system boots, a kernel module is automatically inserted to assist in simulating the packet delays. Issue the following command to run a Tmix setup script 25 25 {{{ 26 26 sudo /local/tmix-script.sh 27 27 }}} 28 28 29 Now, list the contents of your home directory.29 2. Now, list the contents of your home directory. 30 30 {{{ 31 31 ls 32 32 }}} 33 You should see a tmix.conf file, which contains the configuration for a tmix experiment. Open the file with an editor such as vim, emacs, or nano, and browse its contents. These are various settings that control a tmix experiment. At the end of the file 33 You should see a tmix.conf file, which contains the configuration for a tmix experiment. Open the file with an editor such as vim, emacs, or nano, and browse its contents. These are various settings that control a tmix experiment. At the end of the file notice the Crecv_Trace and Cinit_Trace lines. These are the only lines you will need to change as we run our calibration experiments. 34 35 3. List the contents of the tmix data directory by typing the following: 36 {{{ 37 ls /opt/tmix-1.2/data 38 }}} 39 Each file with the .tcvec extension contains connection vectors (or c-vecs). The connection vectors list attributes of a set of connections that are a part of the network traffic we wish to emulate. There is a separate file for the connect 40 41 4. Whe 34 42 Tmix relies upon a pre-determined start time to synchronize tmix on the two nodes. On both nodes run the following command to determine the time and date: 35 43 {{{