NFV aims to virtualize all physical network resources beneath a hypervisor, which allows the network to grow without the addition of more devices.
In this approach, the control plane decides where to send traffic, while the hardware continues to direct and handle the traffic. SDN abstracts physical networking resources –switches, routers and so on – and moves decision making to a virtual network control plane. SDN and NFV differ in how they separate functions and abstract resources. SDN further allows configuration and behavior to be programmatically defined and modified. Thus, NFV provides basic networking functions, while SDN controls and orchestrates them for specific uses. At the same time, SDN's networking control functions for routing, policy definition and applications run in a virtual machine somewhere on the network. When SDN executes on an NFV infrastructure, SDN forwards data packets from one network device to another.
#WHAT ARE THE SIMILARITIES BETWEEN HARDWARE AND SOFTWARE SOFTWARE#
Thus, both depend heavily on virtualization to enable network design and infrastructure to be abstracted in software and then implemented by underlying software across hardware platforms and devices. SDN seeks to separate network control functions from network forwarding functions, while NFV seeks to abstract network forwarding and other networking functions from the hardware on which it runs. The core similarity between software-defined networking (SDN) and network functions virtualization (NFV) is that they both use network abstraction.
While there has been much talk about the power of bringing virtualization to the network, confusion abounds about two different but related approaches: software-defined networking and network functions virtualization.
0 kommentar(er)
