3. Introduction to SDN (Software defined network) - SDN and Openflow Architecture

Video Statistics and Information

Video
Captions Word Cloud
Reddit Comments
Captions
Our Topic is SDN , It stands for Software defined networking Highly correlated with NFV , SDN is big thing in IT and telecom Industry I am going to build your concepts on SDN technology using very a simple graphics and the concepts The concepts which i am going to tell you are of use for everyone which is working in IT or telecom or Networks While NFV is all about building virtual platforms , SDN is making IP networks much more programmable so that packet routing is possible with lots of flexibility and agility . As shown here , SDN is based on concept of separating Brain and control plane for traffic routing , This separation of Brain and control plane makes SDN a very very powerful tool for customizing networks on the fly With SDN , You can provision new bandwidth and define traffic failovers just like never before Now , Let's start our journey with SDN There is lot of confusion between NFV and SDN , Don't worry , we are going to clarify both the technologies in very very simplified way using the real life examples Till now , We have seen , how NFV works in the previous videos How NFV helps us building the agile and flexible networks using the flexible Compute , the flexible resources like storage , the blades , the hardware . Since NFV is all about Three main Concepts : The Softwarization , The Virtualization & Orchestration and automation . SDN is a different animal , Its is all about networking control functions for routing & policy definition & This entire thing is done in very very automated way . & With SDN , what we are going to do We are going to ensure the IP & Network reachability is going to happen well in Time . Both SDN & NFV architectures are going to use network abstraction, But they do is totally in different way SDN provides a new level of programmability and abstraction to Network layer which is play a phenomenal role in Automating the networks . Let’s take deep dive on SDN & let's understand how its work Just see the Building blocks which represents the NFV & host multiple Applications . Just like you can remove , replace or keep new tenant in Build , Similarly you can host applications in NFV as well You can see traffic on road representing SDN whose main responsibility is to carry traffic to right destination in very very Automated way First thing First , Let’s understand why we need SDN & How it is helping .. Well , We have also seen this particular example in previous video wherein We have seen the NFV helps in Virtualizing networks which help us in rapid deployment & ultimately reduce our deployment time of New Service / New Nodes Now NFV does it in few seconds .. but what about network reachability The network connectivity and reachability is real problem , For any new node or new service , We need multiple things such as the IP Allocation , the Bandwidth Allocation , the Policy Opening , the Routing changes Actually , We need to do End to End Reachability and for doing that it takes lot of time .. it takes lot of time to prepare design , to execute the changes and we need to do in every router , every switch that is also prone to mistakes , Net Net , for doing the network reachability piece , we take few days & few weeks Ultimately , even if the NFV resource are available but we can't launch the new service or we can't make the new node live because our network reachability is not done The SDN is going to help us specifically out here , Let's understand how SDN works This is our traditional network where traffic is moving between various Switches & Router in order to reach the final destination SDN changes how networking is fundamentally done. Instead of having a network intelligence which is distributed in every device ( i mean to say every router and switch applying its own brain ) SDN aims to centralize the Brain .. SDN aims to centralize command and control into a central node And Its going to distribute the entire thing in different control plane and in a different data forwarding plane Let's understand , how this different plane works out there The 1st one is the Data Plane , We also call it as Forwarding function or Forwarding plane In traditional network , In traditional router and switches , There are multiple nodes which are connected to each other All these multiple router and switches , they are connected to each other via line card and the links running between these line cards This is where the data is actually moved from one device to another , As visible on screen traffic is going all the way from Router A to Router B to Router C to Router D .. Traffic is moving all the way from Left to the right That's how the packets are flowing here , We call it as Data or Forwarding Plane The next one is control plane . Well in traditional network , The role of control plane is to take routing decisions . Every router is having its own brain .. You can see brain in this orange color which is like rotating out there Every router apply its own brain to decide the best path to route the traffic These routing decisions are taken on basis of the routes configured in the router and routes learned from the adjacent nodes or adjacent routers For an example , In traditional network , Router A decides to route the traffic to router B on basis of Brain applied by itself i.e. Router A I mean to say the router A is taking the decision where to route the traffic Since Router A doesn’t know what’s happening in life of subsequent routers such as C or D , This can be point of concern I mean to say , if there is some problem with Router D , Router A never comes to know , because Router A is not speaking to Router D directly Its going via B , C and then ultimately reaching router D . And if there is problem with D , A will never come to know And A will keep on bombarding the traffic in the same direction & it will never route traffic to a better path There has to be someone , There has to be absolutely someone .. who is keeping end to end eye on complete network and take holistic decision That's the power of SDN where we are going to bring these resiliencies into the Network The last one is the Management Plane . Now , In traditional network , This is used for performing Operation & maintenance of network . I mean to say you can do the configuration , You can get the reports You are actually running the network out there , For an example ,We use management plane to fetch reports , Perform Configurations , Get Alerts and Alarms . You can see this guy who is logging into every router and doing the configuration out there on screen If you have to Open new route , Eventually we need to login into every router and this is very very tedious task which takes lot of time & this is always prone to errors Now we have covered all the 3 planes out there , The data or forwarding plane , The control plane and management plane Now , Let's see how SDN simplified the life and what good things SDN is going to bring to this particular network This is SDN Powered network where in the controller or brain of network is separated from data or forwarding plane . SDN will change dramatically the way we designing the networks the way we are managing the networks & the way we are running our networks Before we discuss this further , Let’s understand What is SDN ? SDN stands for the Software-Defined Networking (SDN) .. This is an emerging architecture of Network that is fully fully programmable , a much more dynamic network , it is manageable it is cost-effective, it is adaptable, It makes it ideal for meeting the dynamic & random requirements There are 4 key principles of the SDN Networks , The 1st key principle is It Makes the Networking & IP Routing flexible . SDN ultimately enable packets or traffic to reach its destination , It does same with help of software & dynamic algorithms with full flexibility & Agility Instead of wasting many days in performing manual routing for enabling reachability , SDN does this in better way , ultimately it saves lot of time The 2nd key principle is Decoupling control & Data plane In traditional network , Where Both Brain & Data forwarding layer sits on same router Here we can see the centralized controller in SDN , whereas Data forwarding plane is still residing on the Router The centralized Controller as part of SDN decides the traffic Routing , The Data Plane only used for forwarding the Payload to destination . We call it as De-Coupling of control & Data plane , They are totaly seperated The next key thing is .. Offloads brain to the centralized controller & the Central View of Resources . SDN provides a central view of much more efficient resource allocation and it is keeping end to end eye on network services This facilitates centralized monitoring of entire network The control plane is taking decision considering end to end topology . Considering end to end health of network . While routing traffic from Router-A down the line to router-B to C to D , It does consider what’s happening in life of Router-D . In case there is some outage or link congestion or some problem with Router-D or some degradation with Router-D It will route traffic via Router-X That's the beauty of SDN , It keep end to end eye on the network Last .. Network is much more Programmable , It is Centrally Managed and It is Agile for any need for any Need Centralized control plane means network control to become directly programmable and the underlying infrastructure to be abstracted for applications and network services SDN makes networks programmable so that operators can support multiple applications such as dynamic provisioning of bandwidth , Automatic Scaleout , Automatic Scale In , Building protection paths Making a new service live , Making new Nodes live , All of this can be entirely automated and can be made programmable There are upper layer applications which can flexibly manage the controller such as exposing Controller directly to user on Web portal where End user can provision or De-Provision bandwidth himself The true power of SDN is Abstraction, The whole logic flow is so automated that network applications can make requests SDN controller which in turn will adjust the network resources, change the configuration & All of this happens in few Seconds And ultimately , Your new Node , New Service , New thing which is required out there .. may be new bandwidth , new provisioning Everything is available on the fly within few seconds Now , Let's understand the SDN Framework - The SDN Architecture , OpenFlow protocol is key to entire topology As you can see this blue color arrow out there , This is openflow integration The openflow protocol is the key to the entire SDN topology The group of few Intellects ,They started working on OpenFlow specification in Stanford University & thereafter , In year 2011 , The ONF - The Open Networking Foundation also started working and they started working on developing the SDN Specs to promote SDN and to promote the OpenFlow . There are several working groups which were created by this organization and they all together standardized the Entire thing Most of OEMs & Vendor .. as of now , as on date , they are supporting this OpenFlow protocol . Here SDN Controller can belong from One OEM where Data / Forwarding plane may belong from another Vendor I mean to say , You put controller from Huawei or you put the forwarding plane from Juniper or may be from Cisco or Juniper , What ever combination you want to do , You can do .. SDN Controller can also communicate with many types of network elements from different vendors with help of the OpenFlow Protocol This OpenFlow protocol provides unified method or southbound interface for the control plane to communicate with the data plane . This This is followed by all the vendors such as Cisco , Juniper , HP - all of them .. OpenFlow works on standard API defined between the control and the Data or forwarding plane . With help of OpenFlow the Brain or Controller can manipulate the changes in the routing tables , the routing Algorithm which are used by forwarding or Data plane . This allows remote configuration of packet forwarding tables by adding, modifying and removing packet matching rules and actions in the data forwading plane . This OpenFlow needs to be supported by both Controller and Forwarding Plane . The existing devices can be also evolved to support OpenFlow , For example If you are having a old inventory of say Cisco switches , Juniper switches , Routers like Huawei Nodes or something like that You can convert all of that Traditional Switches into a Data Forwarding plane Most of these support the data forwarding plane function I mean to say , You can convert the traditional network into the Data forwarding plane & you can create new controller and that controller can create your new SDN Network where in your existing traditional networks will be reused altogether there Here we can transform our existing network to support SDN Since controller is exposed to the Business applications with help of APIs , This gives us opportunity to innovate multiple features & functionalities in the network as per customer requirements Not all the existing router or switches can be converted into SDN ... There are few Models which are not supported but more or less if you have procured in last few years , More or less thay can be upgraded to SDN Now , We will come back to our 1st Slide where network reachability was a big problem With SDN coming into picture , We have seen , We can get the network reachability done within few second This solves our major problem Let’s Quickly Re-Cap the benefits & Features of SDN based networks :- The SDN based networks , They are Directly Programmable , The SDN based networks they are Flexible , They are Dynamic , They are Agile They are Centrally Managed , They Abstracts the Network They De-Couples Control & Forwarding plane Based on Open Standards & Based upon the .. I mean to say .. They are usually Open on the standards , They are supported by more or less all the vendors They are neutral to the vendor , We have already discussed more or less all these points in previous Slides With this , I want to leave a strong Visual message so that you never forget the difference between SDN & NFV Just see the Building blocks which represents the NFV & host multiple Applications . Just like you can remove , replace or keep new tenant in Build , Similarly you can host applications in NFV as well You can see traffic on road representing SDN whose main responsibility is to carry traffic to right destination in a very very Automated way Hope this clarifies the concept of SDN and NFV And Hence , From there onwards , I am assuming there is absolutely no confusion in NFV and SDN Well that's me again .. We have covered both NFV and SDN for telco Operators , We have also covered Why it is cloud and why its required In next Video , I am going to demystify the Hypervisor Vs Container mystery which are going to become the foundation and building block of the Modern Cloud Networks , Stay tuned to the Videos If you want to download this PPT or Video , Please visit my Website : http://telecomtutorial.info/ Hope this Video presentation is useful for you . Please feel free to Like, Dislike , Comment & Share . Pls subscribe to my Youtube . channel for more Technical Videos . Thank you :)
Info
Channel: TelecomTutorial info
Views: 124,958
Rating: undefined out of 5
Keywords: SDN Intro, Openflow, ONF, Openflow Architecture, SDN Vs NFV, Introduction to SDN, sdn, software defined network, what is sdn, sdn introduction, SDN Overview, sdn network, sdn nfv, what is sdn network, sdn technology, sdn solutions, sdn and nfv, sdn architecture, sdn applications, sdn protocols, sdn in cloud computing, what is nfv, what is software defined networking, sdn infrastructure, sdn cloud, what is sdn nfv, what is sdn architecture, SDN PPT, NFV PPT, Vikas Shokeen
Id: TQVl5-G3u2U
Channel Id: undefined
Length: 18min 16sec (1096 seconds)
Published: Mon Dec 03 2018
Related Videos
Note
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.