Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

SDN and NFV: Defining two different aspects of the future of networking

CK Lam, Director of Data Centre Fabric and Virtualization for Asia Pacific, Brocade | Feb. 23, 2016
This article outlines the role of SDN and NFV and goes on to consider their use in context with other virtualisation technologies.

This vendor-written piece has been edited by Executive Networks Media to eliminate product promotion, but readers should note it will likely favour the submitter's approach.

Software Defined networking (SDN) and Network Function Virtualisation (NFV) have become hot topics in the networking industry in the last few years. While these technologies are interlinked, and often mistakenly used interchangeably, understanding the difference is important to getting maximum business value from adopting either, or both. This article outlines the role of each technology and goes on to consider their use in context with other virtualisation technologies. 

SDN versus NFV

SDN started its life inside university campus networks. As researchers were experimenting with new protocols they were frustrated by the need to change the software in the network devices each time they wanted to try a new approach. Meanwhile, web-based companies who were dissatisfied with the sluggish pace of innovation in traditional networking began investing in SDN in order to get the scale and control they needed in their hyperscale data centres. 

While SDN was created by researchers and data centre architects, NFV was initially created by various large service providers to shift from hardware centric to software centric infrastructure. Software-based features will speed up deployment of new network services, advance revenue growth yet reduce operating costs. Put simply, SDN is a new way to manipulate the network, and NFV is a new type of infrastructure to be manipulated. SDN is about controlling network hardware, whereas NFV is about taking what used to be specialized hardware and creating it in software on commodity servers.  

Key differences?

There are key differences between SDN and NFV but the confusion stems from four commonalities between the two: First, both have arisen from customer demand for more flexibility and interoperability, rather than the advent of a particular technology. The second is timing; the concepts emerged in quick succession. Thirdly, coexistence - they can and are used together. Finally, NFV and SDN are used in conjunction with a variety of other new technologies. Having said this, there are ways to set the technologies apart that are worth mentioning.

One of the key differences is that SDN separates the control plane that governs a network from the forwarding plane that sends packets through it, giving IT more control over the behaviour and performance of their networks. SDN addresses the management complexity of rapidly growing and distributed networks by centralising control and enabling programmability to achieve desired behaviours. Importantly, the standards-based decoupling of control and data planes is meant to allow separate purchasing decisions for software and hardware.

In contrast, NFV takes the network processes that are traditionally associated with specialised proprietary hardware (such as routing, firewalls, and application delivery controllers) and converts them to virtualised software platforms that can run on standard commodity hardware, most commonly x86 servers. These functions can be moved within networks on demand and scaled up and down as needed, without the delay and cost of installing new hardware devices. In addition, NFV enables fast /low cost feature upgrades resulting in rapid innovation in service offerings (months or quarters instead of years or decades). As with SDN, the NFV architecture is meant to allow separate purchasing decisions for software and hardware.

 

1  2  Next Page 

Sign up for CIO Asia eNewsletters.