Changes between Version 16 and Version 17 of GENIExperimenter/Tutorials/OpenFlowOVS/Execute

09/19/13 11:27:44 (6 years ago)



  • GENIExperimenter/Tutorials/OpenFlowOVS/Execute

    v16 v17  
    110110Go back to your OVS host and take a look at the print outs. You should see that your controller installed flows based on the mac addresses of your packets.
    112 Kill your POX controller by pressing `Ctrl-C`. Notice what will happen to your ping.
     112Kill your POX controller by pressing `Ctrl-C`:
     115DEBUG:forwarding.l2_learning:installing flow for 02:c7:e8:a7:40:65.1 -> 02:f1:ae:bb:e3:a8.2
     117INFO:core:Going down...
     118INFO:openflow.of_01:[3a-51-a1-ab-c3-43 1] disconnected
     123Notice what will happen to your ping on host1.
    114125==== Soft vs Hard Timeouts ====
    145156In the above example we ran a very simple controller. The power of OpenFlow comes from the fact that you can decide to forward the packet anyway you want based on the supported OpenFlow actions. A very simple but powerful modification you can do, is to duplicate all the traffic of the switch out a specific port. This is very useful for application and network analysis. You can imagine that at the port where you duplicate traffic you connect a device that does analysis. Our hosts are VMs so we are going to verify the duplication by doing a `tcpdump`  on the port on the OVS switch.
    147   1. Open two new terminals to the OVS switch.
     158  1. Open two new terminals to the OVS host.
    149160  2. Look at the sliver details page in the portal and see what interfaces are bound to OVS:if1 and OVS:if2, use the MAC address of the interface to figure this out. Run tcpdump on these interfaces; one in each of the new terminals you opened. This will allow you to see all traffic going out the interfaces
    152163  }}}
    154   2. In the other ovs host go under the `/local/pox/ext` directory:
     165  2. In the other OVS host go under the `/local/pox/ext` directory:
    155166  {{{
    156167   cd ext