Network virtualization {NVF} Vs
software-defined networking {SDN}     #All you want to know about

Network virtualization {NVF} Vs software-defined networking {SDN} #All you want to know about

Network virtualization may sound a lot like software-defined networking(SDN), but there are actually major differences between these two concepts.


Let’s look at these differences.

Though the term software-defined networking means different

things to different people, this much is clear: SDN allows software

to control the network and its physical devices. SDN is all about

software talking to hardware — you can essentially call it a next generation

network management solution. Though it centralizes

management and allows you to control network switches and

routers through software, SDN doesn’t virtualize all networking

functions and components.

In other words, SDN doesn’t allow you to run the entire network in software. Hardware remains the driving force for the network.
A Software Defined Network (SDN) is an open approach to managing the network.  A centralized controller remotely controls the routers and switches within the network fabric, which are typically located far away at the network’s edge.  SDN uses automation and centralized control to provide speed to network configuration and permit dynamic, on-demand changes to react to fluctuations in the traffic flows.  The SDN solution operates hand-in-hand with server virtualization within data centres.  As servers are brought online or removed from service to react to varying demands for traffic requests, the network can be scaled to map these same traffic flows to the server variations.  The provisioning is automated.  SDN separates the data flow plane from the network control plane to permit this virtualization of the network fabric.


In contrast to SDN, network virtualization completely decouples

network resources from the underlying hardware. All networking

components and functions are faithfully replicated in software.

Virtualization principles are applied to physical network infrastructure

to create a flexible pool of transport capacity that can be

allocated, used, and repurposed on demand.

With your networking resources decoupled from the physical

infrastructure, you basically don’t have to touch the underlying

hardware. Virtual machines can move from one logical domain

to another without anyone having to reconfigure the network or

wire up domain connections. You implement network virtualization

in the hypervisor layer on x86 servers rather than on network

switches. The physical network serves as a packet-forwarding

backplane controlled from a higher level.

Network Function Virtualization (NFV) is similar and interrelated to SDN, but it does not need to be necessarily coupled with SDN.  Although they are often seen together.  NFV is the application of software defined appliances to the network.  These appliances include devices such as edge authentication, firewalls, load balancers, and some routing functions.  Traditionally, these network function appliances were hardware based and now under the NFV approach they are software applications running on network edge servers.  Like SDN, these appliances are centrally controlled and managed, which delivers speedy agility, permitting rapid change to settings and configurations.  Policies and procedural settings can be downloaded and updated dynamically too.  These network appliances are virtualized, exactly like the way the networks are managed with SDN.


要查看或添加评论,请登录

Mohit Bhardwaj ?的更多文章

  • Challenges in the Life of "Automation Engineer"

    Challenges in the Life of "Automation Engineer"

    Being an Automation Engineer can feel like a whirlwind ride through uncharted territories, filled with contradictions…

  • VLANs vs NV vs SDN - All you want to know about!

    VLANs vs NV vs SDN - All you want to know about!

    ?????VLANs versus Network Virtualization versus Software‐Defined Networking is a very common question I see people…

    2 条评论
  • Network to Cloud ?? Engineer, Do you need to make this Transition? ??

    Network to Cloud ?? Engineer, Do you need to make this Transition? ??

    Cisco have literally built Networks and current-day Job profiles of "Network Engineers", so starting this discussion…

    7 条评论
  • Networking for Kubernetes

    Networking for Kubernetes

    Kubernetes (K8s) is an open-source container-orchestration system for automating deployment, scaling, and management of…

    2 条评论
  • Automation and Orchestration

    Automation and Orchestration

    Have you ever wondered what the difference between automation and orchestration is? Wikipedia defines automation as the…

    2 条评论
  • Networks for Future || Things that will change in 2020

    Networks for Future || Things that will change in 2020

    In the past, networking was centered on box-level interoperability and was operated manually. This was complex…

  • AI for Network and Cloud Infrastructure

    AI for Network and Cloud Infrastructure

    Traditional network teams would configure the network to send alerts if a change or event occurs as a trigger to…

    2 条评论
  • SD-WAN : Nuage # All you want to know about

    SD-WAN : Nuage # All you want to know about

    SD-WAN: Extend policy-based automation from the cloud to the enterprise WAN Nuage Networks helped establish…

    2 条评论
  • VMware Virtual Networking Concepts

    VMware Virtual Networking Concepts

    With virtual networking, you can network virtual machines in the same way that you do physical machines and can build…

  • Amazon's AWS # All you want to know about

    Amazon's AWS # All you want to know about

    Amazon Web Services(AWS) is a cloud service from Amazon, which provides services in the form of building blocks, these…

社区洞察

其他会员也浏览了