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

Timestamp:

07/10/13 10:50:19 (11 years ago)

Author:

shuang@bbn.com

Comment:

--

GENIEducation/SampleAssignments/OpenFlowLoadBalancerTutorial/ExerciseLayout/Execute

@@ -193 +193 @@
   - group "Monitor" monitors the left path statistics using nmetrics and trace. 
   - group "Monitor1" monitors the right path statistics using nmetrics and trace. 
-  - To monitor the throughput information, we used oml2-trace with the option of "--oml-config" which uses the configuration file we created at /tmp/monitor/conf.xml, which simply sums up the number of ip_len (in Bytes) for each second and save the info into the OML Server (in a Postgre database): 
+  - To monitor the throughput information, we used oml2-trace with the option of "--oml-config" which uses the configuration file we created at /tmp/monitor/conf.xml, which simply sums up the number of tcp_packet_size (in Bytes) for each second and save the info into the OML Server (in a Postgre database): 
   {{{
-   <omlc id="switch" encoding="binary">
-     <collect url="tcp:emmy9.casa.umass.edu:3004" name="traffic">
-       <stream mp="ip" interval="1">
-         <filter field="ip_len" operation="sum" rename="throughput" />
-       </stream>
-     </collect>
-   </omlc>
+<omlc id="switch" encoding="binary">
+  <collect url="tcp:emmy9.casa.umass.edu:3004" name="traffic">
+    <stream mp="tcp" interval="1">
+      <filter field="tcp_packet_size" operation="sum" rename="tcp_throughput" />
+    </stream>
+  </collect>
+</omlc>
   }}}
   - More information about nmetrics and trace can be found here: http://oml.mytestbed.net/projects/omlapp/wiki/OML-instrumented_Applications#Packet-tracer-trace-oml2