Friday, 14 April 2017

Network Function Virtualization Part 2


Hello everyone,

After discussing about hypervisors and their functions in the last post, I am shifting your focus back to NFV.  I am sure you will be appreciating the hypervisors' role in NFV in the next few posts.

In this post, we are discussing about the need & objectives of Network Virtualization.

Why Network Virtualization is required ?

In a network environment there are different network elements configured or installed to serve some specific purpose. For example, Router - its job is to interconnect two different networks and route the packets to different destinations based on the destination IP addresses. Switches - their job is to forward the frames /data to different destinations within a network. Firewall- to block unwanted packets entering into a network and prevent threats from hackers. Servers- to store customer information/data with security and the list continues.

Many of the times, all the above mentioned network elements serve the same purpose throughout their life :) Also, their configurations change very rarely unless there is a major restructuring in business functions.

If a little thought can be given on the functions of these network elements, we understand that we are not using these devices up to their potential :) i.e. Why Router should do the function of only routing? Why Switch only should forward the data ? Why Firewall only is required for security ? , etc.

Strange thoughts Right ?

Yes! These strange thoughts only led to the development of virtualization.

Let me add few more to the list.

Why everyone need dedicated infrastructure ? Can there be a model where a high volume infrastructure is set up and everyone share this infrastructure depending on their requirements ?

Can there be a provision for scaling it up on need basis ? Will it not reduce their CAPEX and OPEX. And more importantly hassle free operations ?

Absolutely Yes!!

Basically NFV aiming is at sharing the common Network Infrastructure and need base utilisation of the network services

Another way of looking at NFV is as follows :

What does these Router or Switch hardware basically consists of ? It is the same things a CPU, Memory /RAM, ROM and an Operating System.

The network functionalities like routing, switching, etc are achieved through either ASICs ( Application Specific Integrated circuits) or Softwares

If an ASIC is used to realize the functionality, then it is hardware specific which means a router hardware can do only routing and not switching.

If the functionality is realized through software, then by changing the software we can change the functionality of the hardware. This means a router hardware can also function as a switch, if that respective software (software of switch) is made run on top it.

So decoupling the network functions from the hardware specific devices is another objective of NFV.

By achieving this objective a general purpose hardware can perform multiple network functions thereby eliminating the need of functional specific proprietary hardware.

Will brief about NFV Framework and Architecture in the next post. Till then have a great time!!

No comments:

Post a Comment