Discuss Software Defined Networking and Network Function Virtualization and relate the topics to the OSI Model and TCP/IP.
Discuss if you think Software Defined Networking is simply hype or if it has merit.
Expert Answer
Before discuss the term Software Defined Networking and Network Function Virtualization, first we need to understand their requirements in IT and Networking area. Why IT organization accepting these as network solution.
We need to understand one more term like cloud computing here so let move forward and understand the cloud computing here
Cloud computing means you application can be accessed by you remotely. applcation can deploy at central remote server. if we take term broad then we can we user can avail serveices remotely then those serices are called cloud servcies
We can take serval example of cloud applciation or services like google map servcies, amazon AWS services , Amazon applciation , google search engine. these all serices are deployed at centeral location somewhere and can be access from anywhere from outer world. no country boundation are there.
if you access google search engine from country a to find out the global data and the same request intiated from country b at same time then the result of both the request will be same that means we are acccessing the same application instance from different location.
There are two models basically which is followed in cloud computing
1. Deployement model { it can be public, private, hybird and comunity level }
2. Servics model : It can be three type
A. Application as a service ( i.e play games over the internet, facebook uses etc.)
B. Platform as a service ( accessing database and web servers like google map etc. )
C. Infrastructure as as services ( like Virtual machine, storage , network and servers etc.)
When we talk about Software Defined Networking and Network Function Virtualization then we will be concentrating on infrastructure as a services beacuse google or amazon like big IT gent are used these services
specially in case clustering ( when one server goes down then without getting applciation failed, whole application shifted to another server called slaves server or multiple master servers.)
Now move to the original question that first we understand that where the OSI model failed and when the Software Defined Networking and Network Function Virtualization concept comes into the
picture.google itself provides serval differnet services like google email services , google map etc. now let suppose google organization typically using number of servers ( hadwares ) to make available these services to public.
now suppose one of the hardware got failed thenin that case google email services and google map services will get down and end users doesn’t avail that services for a particualr time until hardware or servers doesn’t get up back.
si retify the problems at hardware level takes lots of time ( it may be few days or months ). if google stop their services for few days or month then this thing will make big loss for the organization so
to avoid these kind of situation they takes help of those applciation which are capable to control the network trafic at applciation level ( not at hardware level)
Software Defined Networking and Network Function Virtualization are the concept under the same category which provides the capability to controll the trafic dynamically without stoping the services or if in case when server got failed.
With Software defined networking, the network administrator can change any network switch’s rules when necessary prioritizing, de-prioritizing or even blocking specific types of packets with
a very low level of control. This is especially helpful in a multi-tenant architecture ( cloud computing ) , because it allows the network administrator to manage traffic loads in a flexible
and more efficient way.
Network function virtualization is the concept of virtualizing the network nodes ( computers ) so that they can communicate with each other without buying or dealing with physical hardware.
in a single server ( physical hardware ), serval virtual instacne can be run using virtual machine concept . and each instance will be treated as sperate device having dedicated ip address.
now sending packet from one virtual device ( virtual IP address ) to another can be handled through Software defined networking over NFV(Network function virtualization) setup. this is the basic difference between SFN and NFV.
Discuss if you think Software Defined Networking is simply hype or if it has merit ?
Software Defined Networking is not hype, it adds big advantage to the big IT gent so that they can work at differnet location at the same time with large number of employees. beacuse to deploy hardware devices to cater thease requirement is not really poosible
beacuse every second , thousand of devices communcates with each other over the network and if main servcer goes down then they may get strucked so avoid these type of situation , typical virtual machine concepts came. and using
Software Defined Networking , it is easy to communicate all those virtual machine with each other.