Changes between Version 58 and Version 59 of GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute
- Timestamp:
- 10/25/17 13:16:24 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute
v58 v59 16 16 }}} 17 17 [[PageOutline]] 18 == Step 4. Execute Experiment ==18 == Step 3. Execute Experiment == 19 19 20 20 Now that the switch is up and running we are ready to start working on the controller. For this tutorial we are going to use the [https://floodlight.atlassian.net/wiki/spaces/floodlightcontroller Floodlight Controller]. 21 21 22 === 4a. Login to your hosts ===22 === 3a. Login to your hosts === 23 23 24 24 To start our experiment we need to ssh into all of our hosts. … … 26 26 Depending on which tool and OS you are using there is a slightly different process for logging in. If you don't know how to SSH to your reserved hosts learn [wiki:HowTo/LoginToNodes how to login.] Once you have logged in follow the rest of the instructions. 27 27 28 === 4b. Use a Learning Switch Controller ===28 === 3b. Use a Learning Switch Controller === 29 29 30 30 In this example we are going to run a very simple learning switch controller to forward traffic between `host1` and `host2`. … … 89 89 [[Image(GENIExperimenter/Tutorials/Graphics:4NotesIcon_512x512.png, 5%, nolink)]] If you do not see the individual flow entries in the command output, keep in mind that the flows may have timed out, so simply re-ran the traffic to re-add the flows'' 90 90 91 === 4c. Look around your OVS switch ===91 === 3c. Look around your OVS switch === 92 92 93 93 1. To see messages go between your switch and your controller, open a new ssh window to your controller node and run tcpdump on the `eth1` interface and on the tcp port that your Floodight controller is listening on by default 6653. (You can also run `tcpdump` on the `OVS` control interface if you desire.) … … 130 130 131 131 132 === 4d. Debugging your Controller ===132 === 3d. Debugging your Controller === 133 133 While you are developing your controller, some useful debugging tools are: 134 134 … … 172 172 173 173 174 === 4e. Web GUI===174 ==== iv. Web GUI ==== 175 175 176 176 The Floodlight Controller comes equipped with a [https://floodlight.atlassian.net/wiki/display/floodlightcontroller/Web+GUI web-based GUI]. The GUI can be accessed by pointing your favorite browser to the following URL: … … 183 183 184 184 185 === 4f. Topology Details ===185 === 3e. Topology Details === 186 186 187 187 Before we insert flows into the Open vSwitch, we are going to need all the details regarding the topology such as the Data Path IDentifier (DPID) of the Open vSwitch, the MAC addresses of the hosts, and the port numbers on which the Hosts are connected to the Open vSwitch etc. These details can be found by issuing the following command in a new Controller terminal: … … 201 201 202 202 203 === 4f. Run a traffic duplication controller ===203 === 3f. Run a traffic duplication controller === 204 204 205 205 In the above example we ran a very simple learning switch controller. [[BR]] … … 245 245 }}} 246 246 247 === 4g. Run a Port Forwarding Controller ===247 === 3g. Run a Port Forwarding Controller === 248 248 249 249 Now let's do a slightly more complicated controller. !OpenFlow gives you the power to overwrite fields of your packets at the switch, for example the TCP source or destination port and do port forwarding. You can have clients trying to contact a server at port 5000, and the !OpenFlow switch can redirect your traffic to a service listening on port 6000. … … 294 294 295 295 296 === 4h. Run a Server Proxy Controller ===296 === 3h. Run a Server Proxy Controller === 297 297 298 298 As our last exercise, instead of diverting the traffic to a different server running on the same host, we will divert the traffic to a server running on a different host and on a different port. … … 338 338 6. If your controller works correctly, you should see your text appearing on the terminal window of `host3`. 339 339 340 === 4i. Delete your bridge ===340 === 3i. Delete your bridge === 341 341 342 342 Before moving to the next step make sure you delete the bridge you have created, especially if you are using the same reservation for a different exercise:
