Changes between Version 150 and Version 151 of GENIExperimenter/Tutorials/OpenFlowOVS/Execute
- Timestamp:
- 03/18/16 13:54:34 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIExperimenter/Tutorials/OpenFlowOVS/Execute
v150 v151 150 150 You should see at least two table entries: One for ICMP Echo (icmp_type=8) messages from host1 to host2 and one for ICMP Echo Reply (icmp_type=0) messages from host2 to host1. You may also see flow entries for arp packets. 151 151 152 2. To see messages go between your switch and your controller, open a new ssh window to your controller node and run tcpdump on the `eth0` interface and on the tcp port that your controller is listening on usually 6633. (You can also run `tcpdump` on the `OVS` control interface if you desire. However, when using the hardware switch, you can only do the `tcpdump` on your controller host.)152 2. To see messages go between your switch and your controller, open a new ssh window to your controller node and run tcpdump on the `eth0` interface and on the tcp port that your controller is listening on usually 6633. (You can also run `tcpdump` on the `OVS` control interface if you desire.) 153 153 {{{ 154 154 sudo tcpdump -i eth0 tcp port 6633 … … 235 235 236 236 ==== iii. Use Wireshark to see the OpenFlow messages ==== 237 Many times it is useful to see the OpenFlow messages being exchanged between your controller and the switch. This will tell you whether the messages that are created by your controller are correct and will allow you to see the details of any errors you might be seeing from the switch. If you are using OVS then you can use wireshark on both ends of the connection, in hardware switches you have to rely only on the controller view.237 Many times it is useful to see the OpenFlow messages being exchanged between your controller and the switch. This will tell you whether the messages that are created by your controller are correct and will allow you to see the details of any errors you might be seeing from the switch. You can use wireshark on both ends of the connection, in hardware switches you have to rely only on the controller view. 238 238 239 239 The controller host and OVS has wireshark installed, including the openflow dissector. For more information on wireshark you can take a look at the [http://wiki.wireshark.org/ wireshark wiki]. … … 262 262 1. '''Use the interfaces that are connected to `host2` and `host3`. ''' 263 263 * Software Switch (OVS): If you have not noted them down you can use the manifest and the MAC address of the interfaces (ovs:if1 and ovs:if2) to figure this out. But you should have noted down the interfaces in Section 2 when you were configuring the software switch. Run tcpdump on these interfaces; one in each of the two ovs terminals you opened. This will allow you to see all traffic going out the interfaces. 264 * Hardware Switch: Refer to this Section to figure out ports: [http://groups.geni.net/geni/wiki/GENIExperimenter/Tutorials/OpenFlowHW/DesignSetup#a2a.ConfiguretheControllerfortheHardwareSwitch:UsefulTips UsefulTips]. If you are using a hardware switch, you may not see the traffic on host3, but if you observe your controller output, you will notice that flows are being installed for forwarding to host2 and host3.[[BR]]264 [[BR]] 265 265 266 266 To see that duplication is happening, on the ovs host, run: … … 396 396 }}} 397 397 398 {{{ 399 #!comment 398 400 == 4. Moving to a Hardware Switch == 399 401 To try your controller with a GENI Hardware !OpenFlow switch: … … 402 404 403 405 If you do not want to do the Hardware !OpenFlow portion of the tutorial, proceed to [wiki:GENIExperimenter/Tutorials/OpenFlowOVS/Finish Finish] 406 }}} 404 407 ---- 405 408 406 409 = [wiki:GENIExperimenter/Tutorials/OpenFlowOVS/DesignSetup Prev: Design and Setup for OVS] = 407 = [wiki:GENIExperimenter/Tutorials/OpenFlowOVS/HW/DesignSetup Prev: Design and Setup for Hardware Switch] =408 410 409 411 {{{
