Changes between Version 14 and Version 15 of GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute
- Timestamp:
- 11/18/16 08:55:14 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute
v14 v15 30 30 In this example we are going to run a very simple learning switch controller to forward traffic between `host1` and `host2`. 31 31 32 1. First start a ping from `host1` to `host2` , which should timeout, since there is no controller running.33 34 {{{ 35 ping host2 -c 1032 1. First start a ping from `host1` to `host2` , which should timeout, since there is no controller running. 33 34 {{{ 35 ping 10.0.0.2 -c 10 36 36 }}} 37 37 … … 47 47 [[Image(GENIExperimenter/Tutorials/OpenFlowOVS-Floodlight/Execute:Open vSwitch.png, 50%)]] 48 48 49 3. In the terminal of `host1`, ping `host2` :49 3. In the terminal of `host1`, ping `host2` i.e. 10.0.0.2: 50 50 {{{ 51 51 [pjayant@host1:~$ ping 10.0.0.2 … … 71 71 }}} 72 72 73 Now the ping should work. You can see that the time for the first ICMP packet is longer than the rest of the ICMP packets. This is because the Open vSwitch consults the controller the first time a packet-in event occurs. The controller then inserts the flow in the Open vSwitch and the switch consults this flow for further packet-in events. 73 Now the ping should work. You can see that the time for the first ICMP packet is longer than the rest of the ICMP packets. This is because the Open vSwitch consults the controller the first time a packet-in event occurs. The controller then inserts the flow in the Open vSwitch and the switch consults this flow for further packet-in events. Similarly, ping host 3 i.e. 10.0.0.3 from `host1`. 74 74 75 75 4. Go to your Open vSwitch host and take a look at the flows. You should see that your controller installed flows based on the mac addresses of your packets. Enter the following command: … … 120 120 121 121 122 === 4 e. Debugging your Controller ===122 === 4d. Debugging your Controller === 123 123 While you are developing your controller, some useful debugging tools are: 124 124 … … 156 156 When the wireshark window pops up, you might still have to choose eth0 for a live capture. And you will want to use a filter to cut down on the chatter in the wireshark window. One such filter might be just seeing what shows up on port 6633. To do that type ''tcp.port eq 6633'' in the filter window, assuming that 6633 is the port that the controller is 157 157 listening on. And once you have lines, you can choose one of the lines and choose "Decode as ...." and choose the ''OFP protocol''. 158 159 === 4e. Web GUI === 160 161 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: 162 163 {{{ 164 http://<controller-ip>:8080/ui/pages/index.html 165 }}} 166 167 <controller-ip> is the IP address of the control interface of the Controller node(eth0). 168 158 169 159 170 === 4f. Topology Details ===
