Changes between Version 26 and Version 27 of GENIEducation/SampleAssignments/OpenFlowLoadBalancerTutorial/ExerciseLayout/Execute

Timestamp:

07/10/13 10:20:29 (11 years ago)

Author:

shuang@bbn.com

Comment:

--

GENIEducation/SampleAssignments/OpenFlowLoadBalancerTutorial/ExerciseLayout/Execute

@@ -56 +56 @@
   Use the ''tc'' command to enable and configure delay and lossrate constraints on the outgoing interfaces for traffic traveling from the OpenFlow switch to the Aggregator node. To configure a path with a 20 ms delay and 10% lossrate on eth2, you would issue the command: 
 {{{
-sudo tc qdisc add dev eth2 root handle 1:0 netem delay 20ms loss 10%
-}}}
-  Use the ''tc qdisc change'' command to reconfigure existing links,instead of ''tc qdisc add''. [[BR]]
+sudo tc qdisc add dev eth2 root handle 1:0 netem delay 20ms loss 2%
+}}}
+  Use the "tc qdisc change" command to reconfigure existing links,instead of "tc qdisc add". [[BR]]
   The outgoing links on node "Switch" in the provided rspec are numbered 192.168.2.1 and 192.168.3.1 for left and right, respectively.
 
@@ -71 +71 @@
 == 2.4 Use GIMI Portal to run the experiment and monitor the load balancer ==
    - Log on to your !LabWiki Account on http://emmy9.casa.umass.edu:3005 , on the `Prepare` Column, type "OpenFlow", it will pop up with a list of .rb choices. Choose any one, and replace the whole content with the ruby script [http://www.gpolab.bbn.com/experiment-support/OpenFlowExampleExperiment/ExoGENI/loadbalancer_monitor.rb HERE]. 
-   - Log on to node "Switch" and do "ifconfig" to see the IP addresses on each interfaces. Identify the two interfaces that you want to monitor: the interfaces with IP address 192.168.2.1 and 192.168.3.1 respectively. On the !LabWiki page, in your ruby script, find the following line:
+   - Log on to node "Switch" and do "ifconfig" to see the IP addresses on each interfaces. 
+    - '''Note''': You may not be able to see all interfaces up immediately when node "Switch" is ready; wait for some more time (about 1 min) then try "ifconfig" again.
+    - Identify the two interfaces that you want to monitor: the interfaces with IP address 192.168.2.1 and 192.168.3.1 respectively. On the !LabWiki page, in your ruby script, find the following line:
 {{{
 ###### Change the following to the correct interfaces ######
@@ -87 +89 @@
 
 == 2.6 Change network delay and lossrate parameter of left path using tc and repeat the experiment ==
- - use the following command to change network condition on node "Switch": here we assume eth2 is the interface connecting node "Left". User may use "ifconfig" to figure out the correct interface. 
-{{{
-tc qdisc add dev eth2 root handle 1:0 netem delay 20ms loss 10%
+ - use the following command to change network condition on node "Switch": here we assume eth2 is the interface connecting node "Left". '''User need to use "ifconfig" to figure out the correct interface'''. 
+{{{
+tc qdisc add dev eth2 root handle 1:0 netem delay 20ms loss 2%
 }}}
  - Did you see any difference from the graphs plotted on !LabWiki, compared with the graphs plotted in the first experiment? why?
- - Check out the OpenFlow Load Balancing Controller's Log on node "Switch" at /tmp/lb.tmp and tell how many flows are directed to the left path and how many are on the right path, why?
+ - Check out the OpenFlow Load Balancing Controller's Log on node "Switch" at "/tmp/lb.tmp" and tell how many flows are directed to the left path and how many are on the right path, why?
  - To answer the above question, you need to understand the Load Balancing controller. Check out the "load-balancer.rb" file in your home directory on node "Switch". Check Section 3 for hints/explanations about this OpenFlow Controller.