Context Navigation

bMininet

Timestamp:: Dec 22, 2014, 5:32:19 PM (9 years ago)
Author:: ssugrim
Comment:: —

Legend:

: Unmodified
: Added
: Removed
: Modified

Documentation/fSDN/bMininet

-              v2
+              v3
 === Getting started with Mininet ===
+==== Mininet Documentation ====
 This page documents the usage/installation of mininet as well as it's interaction with OEDL.
 The main source is the mininet homepage located at http://mininet.org/.
+==== 0. Installation ==== #install
+''' 0. Installation '''
 While mininet can be installed via an apt-package, the version that is in the repository is very old and does not have some important features so we will instead install by source. References can be found [http://mininet.org/download/ here]
 …
 }}}
+==== 1. Running the network ==== #nw_setup
+As a two-node example, we image the nodes on Sandbox8, as explained in [#imaging Section 1.1]. One is used for the controller, and the other, the Mininet network.
+. ''Bring up and assign addresses to eth0 of the nodes''. Both should be in the same IP block. If done from console, the commands look like this:
+ {{{
+$ ssh root@node1-1 "ifconfig eth0 inet 192.168.1.1 up"
+$ ssh root@node1-2 "ifconfig eth0 inet 192.168.1.2 up"
+ }}}
+ The nodes should now be able to ping eachother via eth0:
+ {{{
+$ ssh root@node1-1 "ping -c 1 192.168.1.2"
+PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
+bytes from 192.168.1.2: icmp_req=1 ttl=64 time=0.614 ms
+--- 192.168.1.2 ping statistics ---
+packets transmitted, 1 received, 0% packet loss, time 0ms
+rtt min/avg/max/mdev = 0.614/0.614/0.614/0.000 ms
+ }}}
+. ''Start the controller on one node''. We arbitrarily pick node1-1. From a shell on node1-1, launch Floodlight:
+ {{{
+# cd floodlight
+# java -jar target/floodlight.jar
+ }}}
+ After you give it a few seconds, Floodlight should be listening to port 6633 on all interfaces available on the node (eth0, 1, and lo). If you want, you can start up `tcpdump` or something similar on a separate terminal on node1-1 to begin capturing control messages:
+ {{{
+# tcpdump -i lo port 6633
+ }}}
+ Alternatively, you can start `tcpdump` to write to a .pcap file for later analysis with `wireshark` with the !OpenFlow plugin.
+ {{{
+# tcpdump -w outfile.pcap -i lo port 6633
+ }}}
+. ''Launch Mininet''. From another shell on node1-2:
+ {{{
+# mn --topo=single,2 --controller=remote,ip=192.168.1.1
+ }}}
+ This will give you a virtual network of two hosts and one switch pointed to the running Floodlight instance on node1-1. Once at the prompt, try pinging one host from the other:
+ {{{
+mininet> h1 ping h2
+PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
+bytes from 10.0.0.2: icmp_req=1 ttl=64 time=8.19 ms
+bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.164 ms
+bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.025 ms
+bytes from 10.0.0.2: icmp_req=4 ttl=64 time=0.024 ms
+^C
+--- 10.0.0.2 ping statistics ---
+packets transmitted, 4 received, 0% packet loss, time 2999ms
+rtt min/avg/max/mdev = 0.024/2.101/8.193/3.517 ms
+ }}}
+Notice how the first ping takes much longer. This is due to the flow installation process triggered by the first ping (Specifically, the ARPs sent by the hosts) as the switch suffers a flow table miss. At the same time, you should see (lots of) packets being captured by tcpdump in node1-1's terminal:
+ {{{
+root@node1-1:~/floodlight# tcpdump -i eth0 port 6633
+tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
+listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
+:18:30.188181 IP 192.168.1.2.41631 > 192.168.1.1.6633: Flags [S], seq 3242563912, win 14600, options [mss 1460,sackOK,TS val 699854 ecr 0,nop,wscale 4], length 0
+:18:30.188321 IP 192.168.1.1.6633 > 192.168.1.2.41631: Flags [S.], seq 2665849071, ack 3242563913, win 14480, options [mss 1460,sackOK,TS val 700809 ecr 699854,nop,wscale 4], length 0
+:18:30.188466 IP 192.168.1.2.41631 > 192.168.1.1.6633: Flags [.], ack 1, win 913, options [nop,nop,TS val 699854 ecr 700809], length 0
+:18:30.188618 IP 192.168.1.2.41631 > 192.168.1.1.6633: Flags [F.], seq 1, ack 1, win 913, options [nop,nop,TS val 699854 ecr 700809], length 0
+:18:30.190310 IP 192.168.1.1.6633 > 192.168.1.2.41631: Flags [.], ack 2, win 905, options [nop,nop,TS val 700810 ecr 699854], length 0
+:18:30.224204 IP 192.168.1.1.6633 > 192.168.1.2.41631: Flags [P.], seq 1:9, ack 2, win 905, options [nop,nop,TS val 700818 ecr 699854], length 8
+:18:30.224426 IP 192.168.1.2.41631 > 192.168.1.1.6633: Flags [R], seq 3242563914, win 0, length 0
+:18:30.402564 IP 192.168.1.2.41632 > 192.168.1.1.6633: Flags [S], seq 1611313095, win 14600, options [mss 1460,sackOK,TS val 699908 ecr 0,nop,wscale 4], length 0
+:18:30.402585 IP 192.168.1.1.6633 > 192.168.1.2.41632: Flags [S.], seq 367168075, ack 1611313096, win 14480, options [mss 1460,sackOK,TS val 700863 ecr 699908,nop,wscale 4], length 0
+...
+ }}}
+=== 1.2.1 Using Wireshark ===
+''' Example Usage '''
+[wiki:/Internal/HelloOF see here]
+----
+''' 1.2.1 Using Wireshark '''[[BR]]
 In the above example, `tcpdump` can be replaced by `wireshark`. Wireshark is "friendlier" in that it has a GUI and an !OpenFlow dissector plugin is available for it. In order to use Wireshark, you must enable X11 forwarding from your workstation to the node, with the -X or -Y flag for `ssh` e.g.:
 {{{
 …
 }}}
+=== 1.2.2 Using OpenVswitch directly ===
+----
+''' 1.2.2 Using OpenVswitch directly '''[[BR]]
 Mininet's datapaths are backed by OVS. Therefore, if you have a Mininet install, you get OVS for "free". You can use OVS directly for your data plane.
 …
 This section shows two examples of more complex SDN network setups - multiple controller instances and with !FlowVisor, a network hypervisor.
+=== Sections ===
+ [#multi 2.1 Multiple Controllers ][[BR]]
+ [#fv 2.2 Network virtualization/slicing ][[BR]]
+==== 2.1 Multiple Controllers ==== #multi
+----
+''' 2.1 Multiple Controllers '''[[BR]]
 You may have multiple controllers in the same logical space of the control plane for various reasons - special applications, fail-over, distributed control planes, etc.
 …
 }}}
+==== Launching multiple controllers ====
+----
+''' Launching multiple controllers '''[[BR]]
 Each instance of the controller run on the same host can be pointed to its own .properties file with the `-cf` flag, with different port value parameters. Begin by making as many copies of the default .properties file as you will have controllers. Going with a similar example as earlier, you can have one host A and three Floodlight instances 1,2, and 3, configured as below:
 …
 This should launch three backgrounded instances of Floodlight.
+==== 2.2 Network virtualization/slicing ====
+----
+''' 2.2 Network virtualization/slicing '''[[BR]]
 A more typical case you might encounter is a network that is sliced, or virtualized.
 …
  * 2.2.3 On the same host
+=== 2.2.1 A brief intro to network virtualization ===
+----
+''' 2.2.1 A brief intro to network virtualization '''[[BR]]
 A virtualized network is organized as below:
 {{{
 …
+''' 2.2.2 Virtualization with multiple hosts '''
+----
+''' 2.2.2 Virtualization with multiple hosts '''[[BR]]
 We begin by introducing a simple example of a virtualized topology:
 {{{
 …
+----
 ''' 2.2.3 On the same host '''
+----
 As with the case of multiple controllers on the same VM/host, you must be careful that neither !FlowVisor nor the controllers listen on the same sets of ports. For the multiple controllers, this can be avoided as described in [#s2_1_2 Section 2.1.2]. !FlowVisor and Floodlight conflict on ports 6633 and 8080.
+==== 3.3 Cbench ==== #cbench
+----
+''' 3.3 Cbench '''[[BR]]
 website: http://docs.projectfloodlight.org/display/floodlightcontroller/Cbench+(New)
+=== dependencies ===
+----
+''' dependencies '''[[BR]]
 {{{
 sudo apt-get install autoconf automake libtool libsnmp-dev libpcap-dev
 }}}
+=== installation/build ===
+''' installation/build '''
 {{{
 git clone git://gitosis.stanford.edu/openflow.git
 …
 Where OF_PATH is where you had cloned the !OpenFlow repository to.
+=== run ===
+----
+''' run ''' [[BR]]
 Run from the cbench directory under oflops:
 {{{
 …
 }}}
+== 3.4 liboftrace (ofdump/ofstats) == #loft
+---
+''' 3.4 liboftrace (ofdump/ofstats) '''[[BR]]
 docs: [[BR]]
  https://github.com/capveg/oftrace/blob/master/README [[BR]]
  http://www.openflow.org/wk/index.php/Liboftrace
+=== dependencies ===
+----
+''' dependencies '''[[BR]]
 {{{
 sudo apt-get install libpcap-dev swig libssl-dev
 }}}
+=== installation/build ===
+----
+''' installation/build '''[[BR]]
 {{{
 git clone git://github.com/capveg/oftrace.git
 …
 make && make install
 }}}
+=== run ===
+----
+''' run '''[[BR]]
 There are two tools pre-packaged with liboftrace (as per a [https://mailman.stanford.edu/pipermail/openflow-discuss/2009-April/000133.html mailing-list entry]):
 . ofstats: a program which calculates the controller processing delay, i.e., the difference in time between a packet_in message and the corresponding packet_out or flow_mod message.
 …
 }}}
+== 3.5 Wireshark == #ws
+----
+''' 3.5 Wireshark '''[[BR]]
 website(wireshark): http://www.wireshark.org [[BR]]
 docs(plugin): https://bitbucket.org/barnstorm/of-dissector
+=== dependencies ===
+----
+''' dependencies '''[[BR]]
 wireshark(source):
 {{{
 …
 }}}
+=== installation/build ===
+----
+''' installation/build '''[[BR]]
 You need the source for Wireshark to build the plugin. At the time of this writing Wireshark is at v.1.10.
 {{{
 …
 Where ${WS_ROOT} is the directory you've untarred the Wireshark source to. The plugin directory may also differ depending on if you installed Wireshark from source or not - if you did, the path will be something similar to /usr/local/lib/wireshark/plugins/1.10.0/
+=== run ===
+----
+''' run '''[[BR]]
 Run Wireshark as root:
 {{{
 …
+==== Refrences ====
+----
+''' Refrences '''[[BR]]
 ''' Floodlight '''