GNS3 Talks: Docker, Open vSwitch, SDN and OpenFlow Part 3: GNS3 Switching Part 9

Key Takeaways

this is one of multiple videos discussing switching with gns3 this is also one of multiple videos discussing open V switch in previous videos I explained how to integrate open V switch with gns3 I explained a bit about flow tables I explained a bit about open V switch as a virtual switch in this video I'm going to show you the integration between open daylight and open V switch [Music] opendaylight is a Software Defined Networking controller for Sdn controller and in this example we are going to use the OpenFlow protocol on the southbound interface between open daylight and open V switch running in GNA 3 I've also got the sukkah dev net open daylight open flow app installed on the opendaylight controller you can find this application on github the open flow manager or OFM application runs as a separate process on the opendaylight controller and uses the rest conf API on the northbound interface for communication to open daylight so I'm going to demonstrate using this application to write the flows via the rest conf or API on the northbound interface and open flow on the southbound interface open daylight supports multiple southbound protocols but in this example we're using open flow to write open flow rules to open flow switches that are running open flow agents open V switch supports both traditional software-defined networking protocols such as OpenFlow in this example of got two cisco routers connected to the open V switch switch and the open V switch switch is connected via ethernet 0 to my physical network in this example rather than running open daylight within gns3 on leveraging and ovae that I already have running within a virtual box so in this example VirtualBox is running on a separate computer here it's running on a Windows computer but I'm using gns3 2.0 on a Mac figuration and setup is very similar if you're using Windows I've simply connected the open V switch Ethernet zero module which is the bolt in management port of the open V switch appliance that you get from the genie 3 marketplace to the cloud that's available in 2 unit 3 2.0 I've once again got opendaylight installed on the OVA running in Windows and I additionally have the dev net github open flow app running on the same OVA so everything is running on this odl OVA so both the OpenFlow app and ODL are running on that OVA I've also got a mini net OVA and just to get us started I'll kick start mini net and get it to talk to the opendaylight controller so in open daylight when I click reload you can see that we have four open flow switches and four hosts connected to this topology and now within the Cisco app I can see a similar topology I'll click this option here to show the host devices I could zoom in as an example and I'd be able to view the flows on that open flow switch but we want to look at the genus 3 integration so I'm going to shut down mini net so now when I click reload on odl we see that no devices are connected and when i refresh i'm told that it can't get the OpenFlow topology data now the first thing we should do is check connectivity to the controller this is the CLI of the open V switch switch so we do have connectivity to the controller the next thing we want to do is configure the switch to talk to that controller so what we're going to do is configure bridge BR 0 which is our open flow bridge to talk to the controller 192 168 165 on TCP port 6633 which is the open flow port then we can use commands such as OVS vs c TL or vs ketal if you prefer to see if the switch is connected to the controller and here we can see that the connection is set to true in other words this bridge BR 0 is connected to the controller on TCP port 6633 in other words on the open flow port a whole range of interfaces are configured as part of that bridge but notice here ethernet 1 as well as ethernet to our part of the open flow bridge in other words the ports that rattle one and rather two are connected to our part of the open flow bridge and we can confirm that by looking at the open flow ports port 1 4 2 are the 2 ports of interest we can view the open flow table by dumping flows and we can see a range of flows have been written to the switch the open flow version that we using is open flow 1.3 this data link type is lldp a flow entry was written with a priority of a hundred and the traffic is being sent to the controller this flow entry was written to table 0 traffic coming in on port 1 is going to be matched on and sent out of multiple ports including port 2 of the switch this entry was also written to table 0 and has a priority of 2 we could look for port 2 in the output so traffic coming in on port 2 is also going to be sent out of port 1 as well as other ports that means that writer one should be able to ping router 2 so let's confirm that writer 1 as an IP address of 10111 right a2 has an IP address of 10 1 1 2 so can write a 1 ping right at - yes it can and I was running a debug here and notice we can see that an echo reply was sent back to write a 1 as an example right a to contain write a 1 and that's because of these flow entries that were written by the ODL controller so in odl when we reload we could see an individual switch when I click on nodes we can see that it's a 16 ports which we can see various interfaces including local Ethernet 1 and Ethernet 2 we can see the flow tables and by default an open V switch switch has 254 tables so that doesn't show us a lot of data I'll show you a better output in a moment we can see that traffic is arriving on port 1 and being sent on port 1 as well as port 2 and the management stack of the switch so traffic sent between right or 1 and writer 2 and the local port is the local management stack of the switch here's the view on the open flow application from Cisco when we click on flow management we can see various flows have been written to the switch so quite a few flows were written for that single switch to allow communication we could look at one of the flows as an example and we'd be able to see that it has a priority of two and in this example it's traffic coming in on port 9 is going to be sent out of multiple ports so at to the moment once again right or one can print router 2 what I'd like you to see is that for the priority of these flows is to quite a low priority there's port 1 so traffic coming and import one you sent out of a multiple ports it has a priority of two what we'll do now however is write a new flow entry to this open V switch or switch the switch is using open flow 1.34 communication with the controller it has 16 flows configured so let's add a new flow entry for our Gina 3 switch will write this to tables 0 that's the only table that we have at the moment let's call this flow ID ABC priority now I'm going to set to 1000 in other words I'm going to make it higher than the other flow entries I'll set a hard time out of 1000 seconds in this example I'm going to match traffic coming in on port 1 and the action that will set here on the flow is to drop the traffic so before I send that to the switch that's a preview of the flow so we're writing traffic to table 0 with an ID of ABC priorities 1,000 hard timeout is 1000 seconds in other words the flow will be removed after 1000 seconds we are matching traffic coming in on port 1 and we're going to drop that traffic now before I send the flow to the section notice we can ping from writer 1 to write it too so let's send the request to the switch we had a success so if we go back we should see our flow entry there it is ABC and notice Rada one is not able to ping write a two so if I clear this notice no pings are arriving we don't see any output on the screen of router to router 2 is not able to ping writer 1 now if we do a debug on this side what we should see is that the traffic from router 2 gets to write a 1 but rather one is not able to send it back to write it 2 because we are dropping all traffic received on port 1 so this flow entry which we created is matching traffic on port 1 and is dropping the traffic so let's delete that flow entry floo entry is being deleted rather one thing rotted - yes it can can write a tube thing writer one yes it can so let's write the flow back and then look at it on the switch open flow table so we're going to select the genus 3 switch table of 0 will set to the ID to ABC again change the priority to let's say 2000 we're going to match traffic coming in on port 1 I won't set a hard time out here and we're going to drop the traffic so notice it's a drop for traffic coming in on port 1 of idea 3 switch give it an ID of ABC let's send the request it was successful click back refresh the flow table there's our flow entry rather one is not able to pain writer too and if we look at the flow table we see a whole bunch of entries but let's grep for mm here's our flow entry that we created notice priority is 2000 we are matching traffic in on port 1 and the action is to drop the traffic this flow entry was written to table 0 we've had nine matches or twelve matches on that flow sensor more pings notice the packet count is going up as the packets are matched and dropped by the open flow switch so let's delete the flow once again flow is being removed rather one contain rather to once again so that was an example of a virtual open flow switch connected to the opendaylight controller using a cisco open flow application installed on the opendaylight controller I was writing flows to the switch to stop writer one from pinging writer to there was an example of the Software Defined Networking architecture we've got the Cisco application using a northbound interface to a controller and open flow on the southbound interface updating the flows of an open flow switch which in this example was an open V switch switch running in a docker container within gns3 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]