SD-WAN 360

Episode 3: Software Defined Networking (SDN)

February 01, 2019 Season 1 Episode 3
SD-WAN 360
Episode 3: Software Defined Networking (SDN)
Chapters
00:00:00
Intro to the SD-WAN 360 Podcast
00:00:26
What is this Episode About?
00:00:43
What is Software Defined? SDN=Software Defined Networking
00:02:16
Control Plane and Data Plane
00:02:46
What is the shift happening with SDN?
00:04:04
What are the benefits of using SDN approach?
00:05:54
Use case for SDN in Service Provider space?
00:06:45
What is NFV?
00:07:39
What is VNF?
00:08:50
Episode Summary
SD-WAN 360
Episode 3: Software Defined Networking (SDN)
Feb 01, 2019 Season 1 Episode 3
Rohan Naggi
What is so special about SDN
Show Notes Transcript Chapter Markers

We will explore the basics of SD-WAN. Let's separate out "SD" and "WAN". Understand the evolution of SDN, What is SDN and the benefits. 



Support the show

Speaker 1:
0:00
Hello and welcome to the podcast. I'm your host Stu. She ran free. 60 podcast is your destination for all things is the technology that is transforming. Neck booking is differently. 60 podcast will help you keep abreast of the leaders in their industries and learn from industry experts, opinion and experiences. It was on about sdn software defined wide adient, but before we get knocking with St van, let's understand some basics and this episode is exactly based on building up those basics around sd run.
Speaker 1:
0:44
Now that we have talked about different types of answer because they're not, what are the problems? Challenges with brand, what is mpls? Well, let's keep the focus to the other part of his Divan, which is as the software define software defined networking. In today's world, if you see, and typically enterprise traffic flow, traffic is no more predictable, traffic is no more point to point. Let's say from brand site data center site, our branch to branch traffic is going everywhere because the resources are scattered around. The soul says our on prem on premise or the resources could be in cloud. So your brand site traffic is going from data center to cloud or directly from branch to clunk. These massive changes, unpredictability, effect sensing that is soul says, neck foot traffic is going every period now finishing a book on not able to keep up with the demand of processing of these data traffic are spinning up resources, make storage, compute servers on demand, so to manage and control these changes in their traditional book and to make it flexible at the same time I joined a centralized entity is required on demand resource bringed up like compute storage or what was required.
Speaker 1:
2:17
Did that play. It's your user traffic frantically in a traditional router or switch the sides, how the package should flow to the network and the data plane we talked about. It's basically the moment of the packet and then the management management name is randy. The orchestration is which pushes the configuration or the policies through these devices
Speaker 1:
2:46
with sdn, software defined networking, there is a shift happening and what is that change happening? We're moving away from hardware to software. Remember the condition they took, all the three planes, control plane management, plane data, plane, all are stuck together or running on a hardware device. He, if we're making the shift from hardware to software and then the second year with sdns segregating, separating out the data plane and the control plane, basically separating out the control of the network from the hardware. So if you use this software or an application to control or program your network. So the key here is software and centrally controlling the network. Software defined networking is designing, building, and then managing your network basically by separating out the network control plane control plane here means the network policies and then the data plane. So this makes network control separate from the underlying network infrastructure, the hardware.
Speaker 1:
4:01
So we are moving away from the hardware. What are the benefits of using this software defined approach, so you are directly controlling using the software as a control function is abstracted from the underlying network infrastructure. The complexity network can now be controlled. Policies can be defined centrally and then you can push those policy and when you define these policies, you can use open source tools. Those automated, you can automate them. Second centralized management. You can get a global view of your network and then can push the configuration from a single management station to all these underlying devices. At the same time you are getting into to visibility, so foreign idea admin, they will only have to deal with one management station. They will just push the configuration and this policy really get distributed to all the network devices. They don't have to worry about even if it's a multi vendor.
Speaker 1:
5:06
Third thing is flexibility in the network, so it sort of using the complexity now the network can either he adopt to new requirements, new changes which are happening, so on demand. If the largest sources coming up like a storage or any application or any infrastructure changes, they can be quickly deployed. They can adopt to the network changes and for the service provider or a cloud provider, the use case will be on demand bandwidth. They can offer it more granular control from a single management entity to push these policy changes. Quality of service configuration, so service provider can apply the sqs policy from a single stage. One more use case I see the service provided is network virtualization for multiple customers, multitenancy, multiple tenants with multiple tenants. Netbook resources are better utilized by creating or by segregating the network, and each segment has it so uncontrolled. Each segment is dedicated for customer service provided in this case will be able to control all the network infrastructure from a centralized management dark history. So to summarize, software defined networking, the shift has happened from hardware to software and then separating out the control plane from the underlying infrastructure hardware.
Speaker 1:
6:42
Now that we talked about software defined networking, let's also define NFV network function virtualization. They have both glossary closely related technology. Border technologies talk about the automation and the virtualization piece over NFV network function. Virtualization is moving away. Services like you know, these new functions like load balancing, caching, firewall and security from a dedicated hardware into a virtualized environment. Software defined networking technology, hemps provision these nfe services. Again, software defined networking technology helps provision these network function virtualization services like load balancing, caching firewall, one security and more, and now let me also bring in one term which is vnf virtual network function, the netvault function that runs inside the virtual machines, Aldi's, vns. These are real objects which are running inside the hypervisor.
Speaker 1:
7:58
You can see an enterprise is using network function virtual in their enterprise network and have deployed neck, but functions like load balancer, caching security as vns, you can also think of and I see as a framework architecture, so nfv is a framework or an architecture and vns are the actual functions which are deployed or these are the actual objects which are deployed in these virtual environment, so vnf is using NFC principles and it's just a component then a part of the nfe and if he is a super set and the interface, just a bark off that network. Function virtualization. Let's summarize this episode. Software defined networking shift from hardware to segregation, separation of control plane and the data in a way to make network control separate from the underlying infrastructure. Then we talked about network function virtualization, which is a concept of freedom book and architecture of moving away from services like those caching and load balancing services from dedicated hardware and bns. Are these objects vetoed? Waterlase vitro virtualizes the services on anything.
Speaker 2:
9:31
Thank you.
Intro to the SD-WAN 360 Podcast
What is this Episode About?
What is Software Defined? SDN=Software Defined Networking
Control Plane and Data Plane
What is the shift happening with SDN?
What are the benefits of using SDN approach?
Use case for SDN in Service Provider space?
What is NFV?
What is VNF?
Episode Summary
×

Listen to this podcast on