Changes between Version 71 and Version 72 of GeniTmixCalibTutorial


Ignore:
Timestamp:
06/21/14 15:19:50 (6 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTmixCalibTutorial

    v71 v72  
    2222
    2323== C. Run Tmix  Script and view data files ==
    24 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.  List the contents of your home directory on either node.
     241.  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.  List the contents of your home directory on either node.
    2525{{{
    2626ls
    2727}}}
    28 2.  If you do not see a tmix.conf file in your home directory type:
     282.  If you do not see a "tmix.conf" file in your home directory type:
    2929{{{
    3030/local/tmix-script.sh
    3131}}}
    32 This script generates a tmix.conf file and attempts to reload the kernel module.  Ignore the warning that that effect.
     32This script generates a "tmix.conf" file and attempts to reload the kernel module.  Ignore the warning that that effect.
    3333
    34343. '''Repeat''' step 2 for the other node. 
    3535
    36 4. Open the tmix.conf file with an editor such as vim, emacs, or nano, and browse its contents.  The entries represent 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 two lines you will need to change as we run our calibration experiments. 
     364. Open the "tmix.conf" file with an editor such as vim, emacs, or nano, and browse its contents.  The entries represent 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 two lines you will need to change as we run our calibration experiments. 
    3737
    38 5.  List the contents of the tmix data directory by typing the following on either node:
     385.  List the contents of the Tmix data directory by typing the following on either node:
    3939{{{
    4040ls /opt/tmix-1.2/data
    4141}}}
    42 A set of connection vectors is described by with a pair of tcvec files (labeled cinit.tcvec and crecv.tcvec).  These two files correspond to connections that are initiated on either side of the link on which the traffic data was originally captured.  Since all of the traffic crossing a busy link cannot generally be replayed using a single pair of nodes, it is customary to split the connection vectors into N pairs of tcvec files.  Most of the files displayed in the listing are named 1ofN.crecv.tcvec.  This is a single pair of connection vector files obtained by evenly splitting the original set of connection vectors into N parts.  For example, running tmix with the pair of files, 1of10.crecv.tcvec and 1of10.cinit.tcvec, will replay about 1/10th the traffic originally recorded on the link.  Below we will perform a set of experiments in which we iterate to find the point at which our pair of nodes can no longer work fast enough to simulate all the network traffic.   
     42A set of connection vectors is described by with a pair of tcvec files (labeled cinit.tcvec and crecv.tcvec).  These two files correspond to connections that are initiated on either side of the link on which the traffic data was originally captured.  Since all of the traffic crossing a busy link cannot generally be replayed using a single pair of nodes, it is customary to split the connection vectors into N pairs of tcvec files.  Most of the files displayed in the listing are named 1ofN.crecv.tcvec.  This is a single pair of connection vector files obtained by evenly splitting the original set of connection vectors into N parts.  For example, running Tmix with the pair of files, 1of10.crecv.tcvec and 1of10.cinit.tcvec, will replay about 1/10th the traffic originally recorded on the link.  Below we will perform a set of experiments in which we iterate to find the point at which our pair of nodes can no longer work fast enough to simulate all the network traffic.   
    4343
    4444== D. Run Tmix  Script and view data files ==
    45 1. Make a new directory for this experiment, change to it, and copy tmix.conf there by typing:
     451. Make a new directory for this experiment, change to it, and copy "tmix.conf" there by typing:
    4646{{{
    4747mkdir 1of10
     
    6363}}}
    6464on the "right" node.
    65 Note that the filenames are swapped on the "right" node.  All you should need to change is what is after "data/" and before ".cinit" or ".crecv".  You are now ready to run the tmix experiment. 
     65Note that the filenames are swapped on the "right" node.  All you should need to change is what is after "data/" and before ".cinit" or ".crecv".  You are now ready to run the Tmix experiment. 
    6666
    67 4.  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:
     674.  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:
    6868{{{
    6969date
    7070}}}
    7171Note that the time may be in a different time zone. 
    72 Decide on a start time about a minute or two in the future, relative to the time displayed by the date command.  It should be far enough in the future for you to issue the following command on both nodes and allow tmix to initialize.
     72Decide on a start time about a minute or two in the future, relative to the time displayed by the date command.  It should be far enough in the future for you to issue the following command on both nodes and allow Tmix to initialize.
    7373
    74745.  Finally, execute the following command on both nodes:
     
    7979
    80806.  Tmix on both hosts will load the data files and then wait until the designated start time. 
    81 You will see "Running for 720 seconds" once tmix is ready to go.  When the start time arrives, Tmix will start running for 12 minutes (a 10 minute experiment plus 2 minutes of buffer).  You will not see any indication on the terminal that it has started running. 
     81You will see "Running for 720 seconds" once Tmix is ready to go.  When the start time arrives, Tmix will start running for 12 minutes (a 10 minute experiment plus 2 minutes of buffer).  You will not see any indication on the terminal that it has started running. 
    8282
    83 7.  One way to verify that tmix is running is to open another SSH terminal to either node and type:
     837.  One way to verify that Tmix is running is to open another SSH terminal to either node and type:
    8484{{{
    8585top
    8686}}}
    87 This shows a listing of the most active processes.  You should see tmix at the top of the list once it starts.  Top can also give you an indication of what percentage of the CPU tmix is using ( in the %CPU column).  If you see numbers near 80% or 90% you are near the capacity of the number of connections that this pair of nodes can simulate.  To exit top type 'q'.
     87This shows a listing of the most active processes.  You should see "tmix" at the top of the list once it starts.  Top can also give you an indication of what percentage of the CPU Tmix is using ( in the %CPU column).  If you see numbers near 80% or 90% you are near the capacity of the number of connections that this pair of nodes can simulate.  To exit top type 'q'.
    8888
    89 8.  Once the experiment is complete, a list of statistics will be output to the console.  Also, a set of log files with extensions .ert, .trt, .unc, .rt, and .ts will be created in the directory.  While tmix runs it is customary to experience a few errors, where connections fail to open or close.  It is also customary to see several errors at the end of the experiment indicating that some connections failed to close.  If, however, you see a steady stream of errors, something is wrong or you are trying to simulate too much traffic.  Type "Ctrl-c" on both terminals, and verify your tmix.conf file, and ensure you followed the above directions. 
     898.  Once the experiment is complete, a list of statistics will be output to the console.  Also, a set of log files with extensions .ert, .trt, .unc, .rt, and .ts will be created in the directory.  While Tmix runs it is customary to experience a few errors, where connections fail to open or close.  It is also customary to see several errors at the end of the experiment indicating that some connections failed to close.  If, however, you see a steady stream of errors, something is wrong or you are trying to simulate too much traffic.  Type "Ctrl-c" on both terminals, and verify your "tmix.conf" file, and ensure you followed the above directions. 
    9090
    91919.  To determine the number of bytes transferred during your experiment type the following on the '''"right"''' SSH terminal: