GNS3 Talks: Docker, Open vSwitch, SDN and OpenFlow Part 5: GNS3 Switching Part 11

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 the community topology I have all routers connected to an open V switch or switch the writer one has prescribed address rotted - that's right it's Revis and right afford this so write a three can ping write a four but can it ping rather - at the moment we're getting a timeout if we do a debug IP ICMP on braddock to and send traffic you will notice that the traffic does get to write a 2 but write a 2 can't send back the reply if we want to make sure that these devices can't even send traffic to one another what we do now is add a flow entry to table 0 with an idea of let's say three or four party a thousand matching traffic coming in on port 3 we are going to output the traffic to port for so traffic coming in on pork three is going to be sent to out of port for and I'll send that to the switch flow entry is being written refresh the flow table here three or four back in open V switch we now have three flow entries of priority 1000 traffic coming in on port 3 is going to be sent out a port for so previously router 3 was able to send a traffic to write a 2 but doesn't get a reply that notice now the traffic doesn't even reach rotted 2 because we forcing all traffic that comes in on port 3 to go out of port for the last piece is to create a flow entry for router for so table 0 for 3 produce 1000 in port is port 4 we're going to Center the traffic out of porch three this is what it looks like again traffic coming in a port for it's going to be sent out of port three I'll sent that to the open flow switch flow entry has been written refresh the flow table there's the latest flow entry that was written to the switch so back on the switch let's grep for entries with priority 1000 we've got four of them so traffic in on port 1 will go to port to port 2 will go to port 1 port 3 to 4 and 43 we've successfully configured this switch as a virtual patch panel so on writer for we should be able to ping writer 3 as we can but can write a full ping write it - no it can't and what about writer 1 no it can't write a 1 can ping writer - but can't ping the other writers so we've isolated writer 3 and writer for an isolated writer 1 and write a 2 this is kind of like private VLANs or a virtual patch panel no traffic from writer 1 is going to go out of port for it's only going to be switched out of port 2 and vice versa so we've created this virtual patch panel but we could move things around if we wanted to so it could delete these individual flow entries and then add new flow increase now I'm doing this manually through GUI which is taking a long time you could obviously write a script that automates this so you could use the rest api talk directly to the controller using a Python script and the rest api and write flows to the switch to move things around a lot quicker what I'm showing you here but as an example let's say we want to patch router three to write a one what I'll do here is create a higher priority flow entry saying that traffic coming in on port three should go to port 1 and I'll send that request to the switch and [Music] what I'll do here that another one 103 produce mm import support one output port is going to be three and center that to the switch so if I go back and refresh the flute table you'll notice we've got this entry and this entry but high-priority flow entries take precedence so at the moment we still have four flow increases priority 1000 but I've added two flow entries with a higher precedence of 2,000 so previously rather one was able to ping rather to but not router 3 but is now able to ping router 3 and not rotted - so I've logically moved to the patch panel and patch two these two tables together where previously this cable was patched to this cable now again I'm doing this through a GUI you could automate this by using a script but what I'll do here is delete 301 and delete 103 so now we don't have any 2000 flow entries we've only got 1000 priority flow entries so in the last test writer one was able to ping router 3 but not rather - but is now able to ping router 2 and not router 3 so I've changed the patch panel these two are connected to each other and these two are connected to each other so router 3 is able to pain rather fall and I could send a broadcast as I've done over here and we should only get a reply back from router fall because router 3 and write a four connected to each other may take a while for that reply to come back but what we've done here is move cables around so that's a very simple example of using open flow to change the behavior of network devices in this example we created a virtual patch panel but you could do that on a physical switch as well so you could have a physical switch cabled up and then move the cables around using open flow so you could create a virtual patch panel rather than paying huge sums of money for a proprietary virtual patch panel hope you enjoyed the video if it was a benefit to you please like it and please subscribe to my youtube channel wish you all the very best [Music]