Changes between Version 2 and Version 3 of GENIExperimenter/Tutorials/SystematicExprCaseStudy/SmallTopo/Execute


Ignore:
Timestamp:
08/18/14 19:13:22 (5 years ago)
Author:
xuan.liu@mail.umkc.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIExperimenter/Tutorials/SystematicExprCaseStudy/SmallTopo/Execute

    v2 v3  
    3434== a. End-to-End `traceroute` and `ping` ==
    3535
    36  * Run `ping` from `client` to `server`.
    37 
     36 * Run `ping` from `client` (192.168.10.11) to `server` (192.168.20.10).
     37 
    3838{{{
    3939xuanliu@client:~$ ping 192.168.20.10
     
    4949
    5050
    51  * Run `traceroute` from `client` to `server`.
     51 * Run `traceroute` from `client` (192.168.10.11) to `server` (192.168.20.10).
    5252
    5353{{{
     
    110110
    111111
    112  * `iperf` End-to-End UDP Test
    113 
    114    Server Side:
     112 * `iperf` End-to-End UDP Test, where the bandwidth is set as 1Mbps by default.
     113
     114   Server (192.168.20.10) Side:
    115115{{{
    116116xuanliu@server:~$ iperf -s -t 10 -i 1 -u
     
    135135}}}
    136136
    137    Client Side:
     137   Client (192.168.10.11) Side:
    138138{{{
    139139xuanliu@client:~$ iperf -c 192.168.20.10 -t 10 -i 1 -u
     
    172172Now let's try some failure events and see how many updates occurs at a particular router, and we select `router-1` to view the updates, and trigger the failures at `router-2`.
    173173
    174  * Login to `router-1` and start the script (i.e., `xorp_run.sh`) that periodically tracking the routing table updates. If there is no change, you will see ''No Change'' from the terminal. Here we run the script for 60 seconds. The script captures the routing table every 1 second.
     174 * Login to `router-1` and start the script (i.e., `xorp_log.sh`) that periodically tracking the routing table updates. If there is no change, you will see ''No Change'' from the terminal. Here we run the script for 60 seconds. The script captures the routing table every 1 second.
    175175 
    176176{{{
     
    193193 * Bring down the interface at router-2
    194194
    195  We can make the link between `router-1` and `router-2` fail by bringing down the corresponding interface on `router-2`. While running `xorp_log.sh` at `router-2`, we disable the virtual interface (`eth2`) that is associated with the virtual link (`192.168.1.0/24`) to `router-2`. We can see one routing table update occurred at `router-1`:
     195 We can make the link between `router-1` and `router-2` fail by bringing down the corresponding interface on `router-2`. While running `xorp_log.sh` at `router-1`, we disable the virtual interface (assuming it's `eth2`) at `router-2`, which is associated with the virtual link (`192.168.1.0/24`) to `router-1`, and the command is:
     196{{{
     197xuanliu@router-2:$ sudo ifconfig eth2 down
     198}}}
     199
     200We can see one routing table update occurred at `router-1`:
    196201
    197202{{{