Context Navigation

aHowTo

Timestamp:: Aug 27, 2009, 4:49:14 PM (15 years ago)
Author:: akoshibe
Comment:: —

Legend:

: Unmodified
: Added
: Removed
: Modified

Tutorials/m0SDN/aHowTo

-              v16
+              v17
 covers the following:
  * The network topology of the testbed
- * The !OpenFlow components of the testbed
  * Installation of the !OpenFlow Reference System and NOX
+ * Operating the controller
  * Performance analysis tools
 …
 === The Testbed ===
 Sandbox 9 consists of three nodes connected to the SB9 Console through a !OpenFlow enabled gigabit switch. The network topology is shown below:
+Sandbox 9 consists of eight nodes (currently three are available) connected to the SB9 Console through a !OpenFlow enabled gigabit switch. The network topology is shown below:
 [[BR]]
 [[BR]]
 [[Image(wiki:Documentation/OpenFlow/OFHowTo:OFSetup.jpg, 450)]]
 The dotted box (labeled sw_sb09) represents the !OpenFlow enabled NEC IP8800/S3640-48T2XW switch, currently running firmware supporting !OpenFlow v0.8.9. The switch is pre-configured so that ports 25-36 (the data VLAN, in red) is an !OpenFlow virtual switch that listens for a controller running on the SB9 Console. There exists a virtual connection between the controller and virtual switch, represented by the dotted red line. Two trunked connections exist - one connects the setup with the ORBIT network (through sw_sb_top), and  the other not only allows the console to communicate with the nodes, but also provides the secure controller-switch VLAN needed for the !OpenFlow setup. The experimenter would be able to monitor and manipulate the setup from the Console.
+The dotted box (labeled sw_sb09) represents the !OpenFlow enabled NEC IP8800/S3640-48T2XW switch, currently running firmware supporting !OpenFlow v0.8.9. The switch is pre-configured so that ports 25-36 (the data VLAN, in red) is an !OpenFlow virtual switch that listens for a controller running on the SB9 Console. There exists a virtual connection between the controller and virtual switch, represented by the dotted red line. Two trunked connections exist on the sw_sb09 - one connects the setup with the ORBIT network (through sw_sb_top), and  the other not only allows the console to communicate with the nodes, but also provides the secure controller-switch VLAN needed for the !OpenFlow setup. The experimenter would be able to monitor and manipulate the setup from the Console.
 ----
+== The Console ==
+We can run the controller on the console or on one of the nodes as they each can have equal access the the openflow controling vlan.
+=== Installing the controller (on a node) ===
+Two distinct controllers, one from the !OpenFlow reference System (v0.8.9r2) and another from NOX-core (v0.5.0), have been successfully installed and tested on the Console. These can be downloaded from the following places:
+== The Controller ==
+We can run the controller on the Console or on one of the nodes as they each can have equal access the the !OpenFlow Control VLAN. Two distinct controllers, one from the !OpenFlow reference System (v0.8.9r2) and another from NOX-core (v0.5.0), have been successfully installed and tested on the Console. These may be installed in your userspace if you wish to run one of these controllers from the Console.
+=== Installing the controller on a node ===
+The software can be downloaded from the following places:
  * !OpenFlow reference system: http://www.openflowswitch.org/wp/downloads/
 …
 }}}
 === Installing the !OpenFlow Reference System ===
+==== Installing the !OpenFlow Reference System ====
 While presented, it is not recommended to install from tarball.
 The detailed instructions may be found here: http://www.openflowswitch.org/wp/getstarted/
 …
 }}}
 === Installing NOX (on a node) ===
+==== Installing NOX  ====
 It is not only recommended but also much simpler to use git to install NOX. Therefore the following instructions assume you are using git. The full instructions are found at noxrepo.org:  http://noxrepo.org/manual/installation.html [[BR]]
 …
  * SQLite 3 development files (libsqlite3-dev)
  * Simple JSON for Python (python-simplejson)
+Note, this is with respect to the Console, not the node - you may need to install additional packages before NOX can be installed properly.
 If all dependencies are taken care of, NOX will install with the following steps.
 {{{
-cd
 git clone git://noxrepo.org/noxcore
 cd noxcore/
 …
 == Controllers on the Console ==
+A sub-set of these instructions can be used to install a "custom" controller in userspace on the console. Most of the requsite libraries should already be installed.
+''TODO'' list subset.
+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:
+'''for the !OpenFlow Reference System :'''[[BR]]
+{{{
+cd
+git clone http://openflowswitch.org/openflow
+cd openflow
+./boot.sh
+./configure --with-l26=/lib/modules/`uname -r`/build
+make
+make install
+}}}
+'''for NOX :'''[[BR]]
+{{{
+cd
+git clone git://noxrepo.org/noxcore
+cd noxcore/
+./boot.sh
+mkdir build/
+cd build/
+../configure --with-python=yes
+make
+make check
+}}}
 === Starting the controller ===
 …
 `ptcp:6633` refers to a passive connection to TCP 6633, the default !OpenFlow port. An active connection method using standard TCP exists, however this does not work on this setup. In the !OpenFlow reference system, a log of the verbose output can be saved by appending `--log-file [filename]`.
+[[BR]]
+[[BR]]
 ----
 == Available Tools ==
+Some of these tools require root privlages and will thus require a custom installation on a node. Otherse can be run from the console directly in an unprivlaged mode.
+''TODO'' indicate what credentails are required for each tool.
+=== the Wireshark plugin ===
+The !OpenFlow Reference system comes with an !OpenFlow wireshark dissector. glib is required for the plugin to work:
+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.
+=== the Wireshark plugin ===
+The !OpenFlow Reference system comes with an !OpenFlow wireshark dissector.
+'''Permissions:''' [[BR]]
+You must be root in order to use Wireshark; Therefore you must install it on a node. [[BR]]
+'''Prerequisites:''' [[BR]]
+glib (and of course, wireshark) is required for the plugin to work:
 {{{
 apt-get install wireshark libgtk2.0-dev
+}}}
+'''Installation:'''[[BR]]
+The patch is located under the utilities directory:
+{{{
 cd utilities/wireshark_dissectors/openflow
 make
 sudo make install
 }}}
+'''Usage:'''[[BR]]
+To use wireshark, you need to do some X11 tunneling. To do this, add the -X option when using SSH to access the Console and the nodes.
 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.
 === Iperf ===
 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.
+'''Permissions:''' [[BR]]
+Iperf does not require root access.
+'''Usage:'''[[BR]]
+Initially, eth0 (the !OpenFlow interface for the nodes) will be disabled. Additionally, there is no DHCP service on that VLAN - you need to enable the interface and statically set the IP address (i.e. using ifconfig). 192.168.x.y is the block associated with the !OpenFlow VLAN.
 To start the server:
 …
 iperf -c 192.168.x.y
 }}}
+.168.x.y is the IP address block associated with the !OpenFlow VLAN. When setting the node IP addresses (i.e. using ifconfig), x.y should be made unique to each node. A caveat is that iperf cannot take real-time bandwidth measurements. Real-time bandwidth use can be monitored using BWM-ng.
+Where 192.168.x.y is the IP address of the iperf server. A caveat is that iperf cannot take real-time bandwidth measurements. Real-time bandwidth use can be monitored using BWM-ng.
+'''On the Console'''[[BR]]
+Iperf is also installed on the Console. The interfaces available on the Console are the following:
+ * eth1 - 192.168.100.28
+ * eth1.27 / Control - 10.19.0.10
+ * eth1.28 / OF virtual switch - 192.168.1.28
+ * eth1.100 / OFP interface - 172.16.100.1
 === BWM-ng ===
+By 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 (-t specifies a sampling rate of 1000 msec, or 1 sample/sec):
+BWM-ng is a tool capable of taking real-time throughput measurements of different interfaces of a host.
+'''Permissions:''' [[BR]]
+BWM-ng does not require root access, and is installed on the Console.
+'''Usage:'''[[BR]]
+By 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:
 {{{
 bwm-ng -I eth1.100 -o csv -t 1000 -F <file-name>
 }}}
+ * -I : interface
+ * -o : output, either in csv or html
+ * -t : specifies sampling rate in msec. Here, it is 1000 msec, or 1 sample/sec
+ * -F : Filename of output
+'''Installation on a node'''[[BR]]
+The following command will install BWM-ng:
+{{{
+apt-get install bwm-ng
+}}}
+----
 === Development ===
 The files defining !OpenFlow Protocol can be found in the following locations: