Changes between Version 6 and Version 7 of Internal/OpenFlow/OFIntro


Ignore:
Timestamp:
Jul 26, 2013, 12:45:42 AM (11 years ago)
Author:
akoshibe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Internal/OpenFlow/OFIntro

    v6 v7  
    8686# mn --topo=single,2 --controller=remote,ip=192.168.1.1
    8787 }}}
    88  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 (it should work):
     88 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:
    8989 {{{
    9090mininet> h1 ping h2
     
    9999rtt min/avg/max/mdev = 0.024/2.101/8.193/3.517 ms
    100100 }}}
    101  At the same time, you should see (lots of) packets being captured by tcpdump in node1-1's terminal:
     101Notice 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:
    102102 {{{
    103103root@node1-1:~/floodlight# tcpdump -i eth0 port 6633
     
    122122}}}
    123123
    124 == Using OpenVswitch directly ==
     124=== 1.2.2 Using OpenVswitch directly ===
    125125Mininet'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.
    126126
    127127= II More complex examples =
    128 You can launch multiple instances of Floodlight on one or more nodes. If you decide to run the instances on a single host, the ports used by the Floodlight instances must not conflict i.e. each instance must be assigned a different set of ports.
    129  
     128You can launch multiple instances of Floodlight on one or more nodes. If you decide to run the instances on a single host, the ports used by the Floodlight instances must not conflict i.e. each instance must be assigned a different ports.
     129 
     130== 2.1 Multiple Controllers == 
     131
     132== 2.2 With FlowVisor ==
     133
    130134----
    131135= III Installation = #install
     
    141145Note, the following examples are for Ubuntu, since that's what is used at WINLAB. A quick search will often bring up hints/steps for CentOS/RHEL and OSX, but for the most part, you will have to experiment a bit.
    142146 
    143 == 2.1 Floodlight == #floodlight
     147== 3.1 Floodlight == #floodlight
    144148docs: http://docs.projectfloodlight.org/display/floodlightcontroller/Floodlight+Documentation [[BR]]
    145149
     
    172176Tutorials and other information can be found here: http://docs.projectfloodlight.org/display/floodlightcontroller/For+Developers
    173177
    174 == 2.2 Mininet == #mn
     178== 3.2 Mininet == #mn
    175179website: http://mininet.org/ [[BR]]
    176180It is highly recommended to run trough the docs, especially the following:
     
    316320}}}
    317321
    318 == 2.3 Cbench == #cbench
     322== 3.3 Cbench == #cbench
    319323website: http://docs.projectfloodlight.org/display/floodlightcontroller/Cbench+(New)
    320324
     
    373377}}}
    374378
    375 == 2.4 liboftrace (ofdump/ofstats) == #loft
     379== 3.4 liboftrace (ofdump/ofstats) == #loft
    376380docs: [[BR]]
    377381 https://github.com/capveg/oftrace/blob/master/README [[BR]]