70 | | rtt min/avg/max/mdev = 1.501/26.489/327.007/83.532 ms}}} |
71 | | |
72 | | 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 | | |
74 | | 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: |
| 70 | rtt min/avg/max/mdev = 1.501/26.489/327.007/83.532 ms |
| 71 | }}} |
| 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. |
| 74 | |
| 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: |
87 | | 1. If you are using OVS, to see the flow table entries on your OVS switch: |
88 | | {{{ |
89 | | sudo ovs-ofctl dump-flows br0 |
90 | | }}} |
91 | | 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. |
92 | | |
93 | | 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.) |
94 | | {{{ |
95 | | sudo tcpdump -i eth0 tcp port 6633 |
| 88 | 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 controller is listening on usually 6653. (You can also run `tcpdump` on the `OVS` control interface if you desire.) |
| 89 | {{{ |
| 90 | sudo tcpdump -i eth1 tcp port 6653 |
99 | | 3. Kill your POX controller by pressing `Ctrl-C`: |
100 | | {{{ |
101 | | DEBUG:forwarding.l2_learning:installing flow for 02:c7:e8:a7:40:65.1 -> 02:f1:ae:bb:e3:a8.2 |
102 | | INFO:core:Going down... |
103 | | INFO:openflow.of_01:[3a-51-a1-ab-c3-43 1] disconnected |
104 | | INFO:core:Down. |
| 94 | 3. Kill your Floodlight controller by pressing `Ctrl-C`: |
| 95 | {{{ |
| 96 | 2016-10-30 21:00:47.333 INFO [n.f.l.i.LinkDiscoveryManager] Sending LLDP packets out of all the enabled ports |
| 97 | 2016-10-30 21:01:02.339 INFO [n.f.l.i.LinkDiscoveryManager] Sending LLDP packets out of all the enabled ports |
| 98 | 2016-10-30 21:01:17.344 INFO [n.f.l.i.LinkDiscoveryManager] Sending LLDP packets out of all the enabled ports |
| 99 | ^C |
| 100 | pjayant@controller:~/floodlight$ |