Changes between Version 61 and Version 62 of GENIExperimenter/Tutorials/OpenFlowOVS/Execute
- Timestamp:
- 07/07/14 20:16:34 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/OpenFlowOVS/Execute
v61 v62 24 24 25 25 To get ready for the tutorial you will need to have the following windows open: 26 * t wowindows with ssh into OVS26 * three windows with ssh into OVS 27 27 * one windows with ssh into host1 28 28 * two window with ssh into host2 … … 193 193 In the above example we ran a very simple learning switch 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. For this tutorial we are going to verify the duplication by doing a `tcpdump` on a port on the OVS switch. 194 194 195 1. Look at the slice ''Details'' page in the portal, select the aggregate that you chose in flack to create the sliver, if you used the portal to create the sliver, then the aggregate is already selected for you). Click on "Resource Details" to find the interfaces bound to ''OVS:if1'' (connected to `host2`) and ''OVS:if2'' (connected to `host3`), use the MAC address of the interface to figure this out. Run tcpdump on these interfaces; one in each of the newterminals you opened. This will allow you to see all traffic going out the interfaces.195 1. Use the interfaces that are connected to `host2` and `host3`. If you haven't note them down you can use the manifest and the MAC address of the interfaces (ovs:if1 and ovs:if2) to figure this out. Run tcpdump on these interfaces; one in each of the other two terminals you opened. This will allow you to see all traffic going out the interfaces. 196 196 {{{ 197 197 sudo tcpdump -i <data_interface_name>