Changes between Version 10 and Version 11 of Tutorials/m0SDN/aHowTo


Ignore:
Timestamp:
Aug 20, 2009, 4:30:11 AM (15 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/m0SDN/aHowTo

    v10 v11  
    117117tcpdump pcap files can also be opened using wireshark - once the plugin has been installed, !OpenFlow packets can be interpreted from these files as well. 
    118118
    119 === BWM-ng ===
    120 For performance testing, you may want to run some bandwidth tests. Real-time bandwidth use can be monitored using BWM-ng. By default, the tool will monitor all interfaces on the Console. To just monitor the !OpenFlow interface, you must specify `eth1.100`. To output this to a csv, use the following command:
     119=== Iperf ===
     120For performance testing, you may want to run some bandwidth tests. iperf is a tool that measures maximum network performance using TCP for throughput and UDP for jitter and datagram loss. The standard image used for the Sandbox nodes when booted with command `omf tell on` comes with iperf. To take measurements, you need at least two nodes. One node becomes the server, the other(s), clients.
     121
     122To start the server:
     123{{{
     124iperf -s
     125}}}   
     126and on the client:
     127{{{
     128iperf -c <server ip address>
     129}}}
     130
     131iperf, however, cannot take real-time bandwidth measurements. Real-time bandwidth use can be monitored using BWM-ng.
     132
     133=== BWM-ng ===
     134By default, the tool will monitor all interfaces on the Console. To monitor just the !OpenFlow interface, you must specify `eth1.100`. To output this to a csv, use the following command:
    121135
    122136{{{
    123137bwm-ng -I eth1.100 -o csv -t 1000 -F <file-name>
    124138}}} 
    125 
    126 
    127139
    128140=== Development ===