GNS3 Talks: Docker, Open vSwitch, SDN and OpenFlow Part 4: GNS3 Switching Part 10

Key Takeaways

in this video I'm going to show you an application of Software Defined Networking using the opendaylight controller in this example I'm going to show you how to configure an open flow patch panel so in a creative virtual patch panel in this topology [Music] in this gns3 topology I have four routers connected to an open V switch and switch so router one has this IP address write it to this router three this and rather forward this in other words they are in the 10110 slash 24 network and are connected to ports one two three and four on the open V switch switch please see my other videos which have linked below which show you how to integrate two open V switch and open daylight in gns3 in this topology I'm using the management interface of open V switch to connect it to the physical network and I've got the opendaylight controller running in VirtualBox on a PC in my physical network so opendaylight is currently running and the open V switch switch has connected to the opendaylight controller as you can see here the open V switch switch has registered and the four host devices have been picked up in open daylight so this topology represents the genus 3 topology open flow is enabled on these 4 interfaces it's not running on the management interface he has my open V switch switch OVS vs CTL show shows me details of the switch br0 is the bridge used by the jr. 3 implementation for open flow and currently it's connected to the opendaylight controller using TCP port 6633 as you can see it's connected and in the output here we can see that Ethernet 1 ethernet 3 & 4 as well as Ethernet two are part of the open flow bridge now I've previously used this command to configure the switch to talk to open daylight so won't enter that again this command will show us the ports running an open flow second seaport one port to port three and port four are sending and receiving packets this command will allow us to view the flows on the switch so as you can see various flows have been written by the open flow controller the switch is using open flow 1.3 this is a match as an example for lldp which is being sent to the controller and traffic coming in on port 1 as an example it's going to be forwarded out of other ports traffic coming in on port 4 will be forwarded out of other ports on the switch as well as sent to the controller see here's write a one can obtain write a 2 as an example yes it can can ping write a 3 and it can ping write a 4 if I send a broadcast we should get a reply from those three writers and we do so both broadcast traffic and unicast traffic of being sent to the other writers in the topology and that's because of this flow entry that says that traffic coming in on port 1 will be forwarded out of port for 42 and 43 it's also going to be sent out of other ports but they are not currently connected to the switch and to the controller now you could remove these flow entries either directly on the switch or by using an open flow application now in this example I'm using the opendaylight controller once again but in addition I've installed the Cisco dev net open daylight open flow app you can get to this from github this application uses the rest conf API for communication to the opendaylight controller which in turn writes open flow rules to these switches using the OpenFlow protocol so on the northbound interface or NBI a REST API is being used and on the southbound interface or SPI the OpenFlow protocol is used by the controller to update data the open flow tables of open flow switches in this example the open flow switch running within gns3 will be updated so I've connected to the controller on Porter 9000 this is the subscribe like a ssin and as you can see here's my switch and my 4 pcs connected to that switch when I click on flow management I'll be able to see the flows that have been added to the switch so in this example I've got a single open V switch switch running open flow 1.3 and sixteen flows have been configured on the switch so as an example if we click one of the flows and view it we can see that to this flow entry matches traffic in on port 10 and then forwards it out of a number of ports as well as the controller what I want to do however is override these flow entries now we could as an example delete all the flow entries if we wanted to but in this example I'm going to create a new flow entry on the open flow switch and I'm going to write a flow to Table zero with a flow entry of 1 0 2 in other words I want only write a 1 to talk to router to you and not to other riders I'm going to set to the priority to 1000 I'm going to match traffic coming in on port 1 because that's where rather 1 is now what we want to do with this traffic is forward it out of a port we could drop it sent it to the loopback interface flooded senators of controller sent it to the normal port but in this case I'm going to output it to port 2 so traffic that comes in on port 1 is going to be sent out of port 2 clicking show preview shows us the flow that we're going to write it to the switch so we're going to write a flow entry to table 0 with an ID of 102 and a priority of 1000 matching traffic coming in on port 1 and we're going to send it out of port 2 now before I sent it back to the switch notice that rather one campaign router 3 and rather fall but I'm going to send that to the switch we can see that it was successfully written as you can see in the output the flow entry has been rewritten you could refresh your flow table to see the latest information but notice of 102 has been written to table 0 on the open flow switch I could grep for a flow entry with priority 1,000 so there's our flow entry stating that traffic coming in on port 1 will be sent out of port 2 so write a one at the moment can pain write a to that notice can't pen write a three because all traffic coming in on port one on this switch is going to be forwarded out of port to rather one can also not ping write a four because all traffic is going from rudder one two rather to you because all traffic coming in on port 1 is sent out of Port 2 because of this flow entry you can see that they've been hits on this flow entry the flow entry takes priority over the default flow entries because it has a higher priority the other flow entries have a priority of 2 where's this one has a Prada of a thousand so as an example if we ping the broadcast address we get a reply back from router 2 but we don't get a reply back from router 3 or rather for so we've successfully configured the network so that writer one can only send traffic to write a 2 now we may want to do the reverse after the moment writer - can ping writer 1 but it could also pain writer 3 and rather fall so perhaps who want to limit this so that only writer 1 and writer - can ping each other so back in our Cisco app I'll add a new flow entry to open V switch one to table 0 the ID will be 201 in other words rotted - sending traffic to write a 1 Prada will be a thousand we're going to match traffic coming in on port 2 and the action will be to send the traffic out of Port 1 [Music] so preview traffic coming in report to will be sent out of port 1 send that to the switch the flow entry is written click back refresh the flow table notice years 201 and he has 102 the to flow entries that we wrote to the switch back in open research if I grep for 1000 we can see our two flow entries traffic coming in on cord one is sent out a port to traffic coming in on port 2 is sent out of Port one writer one can ping rudder to write a 2 can ping writer one like rudder - can no longer ping router 3 or rather fall we have successfully patched this port to the sport and back again I hope you've enjoyed this video if it's been a benefit to you please like it and please subscribe to my youtube channel I wish you all the very best [Music]