Subscribe / Unsubscribe Enewsletters | Login | Register

Pencil Banner

Understanding how SDN and NFV can work together

Ed Tittel | Jan. 29, 2014
As software-defined networking and network function virtualization begin to take hold in the enterprise, it's worth examining each concept to see how they complement each other. The end result: More generic network hardware and more open software.

The self-professed goal of the organization is to "define the requirements and architecture for the virtualization of network functions." Its predictable aims, dear to all service providers, are helping customers reduce capital and operations expenses, speeding time to market for service elements and providing flexible, agile solutions delivered in software running on industry-standard server hardware elements.

Ultimately, NFV is about virtualizing IT resources in software so that virtual implementations may be used to provide important network functions, rather than requiring the presence of one or more specialized physical devices. These virtual devices appear and behave like their physical counterparts on the networks they serve without the need for individual devices to fill their various specialized functions.

At present, the primary focus for NFV in today's marketplace targets the following niches:

  • Virtual Switching, or physical ports that link to virtual ports on virtual servers, where virtual routers employ virtualized IPsec and SSL VPN gateways
  • Virtualized Network Appliances, where network functions that could employ dedicated devices can instead employ virtualized appliances for a range of specialized functions
  • Virtualized Network Services, which provide software-based network monitoring and management services, including traffic analysis, network monitoring and alerting, load balancing and quality or class of service handling
  • Virtualized Applications, which deliver network-optimized frameworks and APIs for cloud applications to support an increasingly mobile or BYOD-based user population

SDN, NFV More Complementary Than Competitive
To the relief of all parties involved — primarily the enterprises and consumers of high-end networking on the SDN side, and the service providers who assembled themselves to get behind virtualized network functions on the NFV side — SDN and NFV dovetail nicely.

Together, in fact, they represent a path toward more generic network hardware and more open software, where the centralized control and management decreed in SDN can in part be realized through the virtualized functions and capabilities that come from NVF. This applies especially for network management applications and services for monitoring, management, traffic analysis, load balancing and so forth.

Both SDN and NFV capitalize and depend heavily upon virtualization to enable their respective capabilities -- and to deliver upon their promises to separate connections and packet handling from overall network control (SDN) while combining and consolidating specialized functions and capabilities on standard hardware elements (NFV).

Adoption of what Tom Nolle calls a "software-overlay network model" means that, in a conglomeration of cloud-hosted virtual functions, NFV makes use of services as tenants atop NFV infrastructures. Here, tunnels and virtual switches isolate virtual functions to prevent interaction, stymie malicious snooping or attack, and link to cloud-based virtual network interfaces such as those described in OpenStack Neutron.

It appears, then, that the kinds of functions that NFV seeks to deliver work well within the framework defined for SDN, and that services defined for NFV will help provide the necessary abstraction and separation of the network control and data/packet planes.

It might be serendipity at work, but this combination appears to offer potent potential for the next revolution in networking. At any rate, it will be fascinating to see how things play out in 2014 and beyond.

 

Previous Page  1  2 

Sign up for CIO Asia eNewsletters.