Network functions virtualization (NFV) explained
SDxCentral notes that network functions virtualization (NFV) is defined by “the decoupling of network functions from proprietary hardware appliances” and using these functions as virtual machines (VMs).1 A network architecture concept, NFV uses IT virtualization technology to virtualize networks into building blocks that can connect or link up to produce communication services.
Techopedia defines NFV as a procedure that “increases and improves network function [and] managing networks”.2 NFV functions by changing how architect networks deliver network services, chaining together disparate classes of network nodes. It then creates a form of communication or makes certain information widely available to specific or general users.
It’s important to note that although networks are meant to be virtualized using NFV, network functions aren’t meant to be virtualized. Firewalls, traffic control, and virtual routing are three of the most common virtual network functions (VNFs). Other functions include working as an alternative to load balancers and routers.
NFV architecture
The European Telecommunications Standards Institute (ETSI) proposed the NFV architecture, which has helped to define the NFV implementation standards. In pursuit of improved stability and interoperability, these NFV architecture components were modeled on the implementation standards.
The following are the components of the NFV architecture:
- VNFs. Software apps that generate network functions, including file sharing, Internet Protocol (IP) configuration and directory services.
- Network functions virtualization Infrastructure (NFVI). These components work from a platform to support software that’s needed for running networking apps. They are made up of the following infrastructure components:
- Compute
- Storage
- Networking
- Management, automation and network orchestration (MANO). Supports the framework for provisioning new VNFs and controlling the NFV infrastructure.