Changes between Version 73 and Version 74 of GeniTmixCalibTutorial


Ignore:
Timestamp:
06/21/14 17:21:13 (5 years ago)
Author:
Ben Newton
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GeniTmixCalibTutorial

    v73 v74  
    4040ls /opt/tmix-1.2/data
    4141}}}
    42 A set of connection vectors is described by 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 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.  Pairs of connection vector files are obtained by evenly splitting an 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 ==
     
    52522.  '''Repeat''' for the other node. 
    5353
    54 3.  '''Edit the copied tmix.conf''' file on both nodes using a terminal text editor such that your Crecv and Cinit lines are the following. 
     543.  '''Edit the copied tmix.conf''' file on both nodes using a terminal text editor such that your Crecv and Cinit lines are the following: 
    5555{{{
    5656Cinit_Trace = /opt/tmix-1.2/data/1of10.cinit.tcvec
     
    6565Note 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