Changes between Version 25 and Version 26 of Tutorials/m0SDN/aHowTo
- Timestamp:
- Oct 18, 2013, 10:39:19 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tutorials/m0SDN/aHowTo
v25 v26 1 = Tutorial 1: "Simple" Controllers=1 == Tutorial 1: "Simple" Controllers == 2 2 3 3 We can run the OF controller on the sb9 console or on one of the nodes as they each have access the the !OpenFlow switch management interface. In this document, we are about to use two distinct controllers, one from the !OpenFlow reference System and another from NOX-core, for management of the setup. These may be even installed in your userspace if you wish to run one of these controllers from the Console (normaly they are installe under root account on one of the nodes in the sb9). 4 4 5 == Controller on a node==5 === Controller on a node === 6 6 The software can be downloaded from the following places: 7 7 … … 16 16 }}} 17 17 18 === Installing the !OpenFlow Reference System (old)===18 ==== Installing the !OpenFlow Reference System (old) ==== 19 19 While presented, it is not recommended to install from tarball. 20 20 The detailed instructions may be found here: http://www.openflowswitch.org/wp/getstarted/ … … 71 71 72 72 73 == Controllers on the Console==73 === Controllers on the Console === 74 74 75 75 A sub-set of these instructions can be used to install a "custom" controller in userspace on the console. Most of the requisite libraries should already be installed. Use the following commands to install the Reference system in your userspace: … … 100 100 101 101 102 == Starting the controller==102 === Starting the controller === 103 103 Both commands start the controller and establish a connection with the !OpenFlow switch. The -v is for verbose. -h for both will give you the help files for the controllers. In the reference system, the controller is found under .../openflow/controller/ 104 104 {{{ … … 115 115 116 116 ---- 117 == Available Tools==117 === Available Tools === 118 118 119 119 Some of these tools require root privileges and will thus require a custom installation on a node. Others can be run from the console directly in an unprivileged mode. 120 120 121 === the Wireshark plugin ===121 ==== the Wireshark plugin ==== 122 122 The !OpenFlow Reference system comes with an !OpenFlow wireshark dissector. 123 123 … … 144 144 tcpdump pcap files can also be opened using wireshark - once the plugin has been installed, !OpenFlow packets can be interpreted from these files as well. 145 145 146 === Iperf===146 ==== Iperf ==== 147 147 For 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. 148 148 … … 171 171 * eth1.100 / OFP interface - 172.16.100.1 172 172 173 === BWM-ng===173 ==== BWM-ng ==== 174 174 BWM-ng is a tool capable of taking real-time throughput measurements of different interfaces of a host. 175 175 … … 194 194 195 195 ---- 196 === Development===196 ==== Development ==== 197 197 The files defining !OpenFlow Protocol can be found in the following locations: 198 198 * !OpenFlow reference system: openflow/include/openflow/openflow.h
