Making Sense of the Myriad SDN Offerings

With the range of software-defined networking (SDN) announcements coming from vendors large and small it is hard to figure out which SDN approach is best for what.

This vendor-written tech primer has been edited by Network World to eliminate product promotion, but readers should note it will likely favor the submitter's approach.

With the range of software-defined networking (SDN) announcements coming from vendors large and small it is hard to figure out which SDN approach is best for what.

One way to get your arms around it is to organize the various SDN announcements into buckets of common features and functionality. As you can see below, we can classify them into four buckets: 1) legacy proprietary systems; 2) overlay network virtualization; 3) abstracted network management systems; and, 4) open SDN architectures.

[ BACKGROUND: Network administrators look to SDN with hope, concern ]

Now, let's analyze each of them.

* Legacy proprietary systems need no explanation. Because these systems were built with a distributed control plane architecture, we've been manually provisioning proprietary protocols on each interface of each device for every network service request for the last 20 years. While this is a mature and well-understood way to build and manage networks, it seems to be failing in customer applications where business agility, automated provisioning and best-in-class operational costs are paramount.

* Overlay network virtualization arose to address the fundamental inability of legacy networks to support the dynamic nature of virtualized and cloud data center workloads. Overlay network virtualization products exclusively use network encapsulation or tunnels to dynamically tunnel traffic between virtual hosts, thus circumventing the static nature of traditional L2 and L3 network protocols and addressing schemes.

Overlay network virtualization products implement control of virtual switches operating on virtual hosts using inherently closed, proprietary control protocols to direct traffic. As a result, these solutions tend to be purpose-built applications exclusively built to handle network tunneling for virtual workloads, and nothing else. They are not capable of addressing other limitations of legacy networking systems, since overlay networks are inherently detached from the physical network control plane.

* Abstracted network management systems are a relatively new attempt by legacy vendors to centralize management of multiple types of devices via a management plane abstraction to multiple underlying device operating systems. While it is a step forward in centralizing the management and configuration of devices, it has a number of shortcomings.

First, these management abstractions are inherently vendor-specific. Second, since the abstractions are simply APIs sitting on top of CLI commands, there are inherent limitations that result from different feature sets enabled with different CLI commands on different product offerings. While it is useful for centralizing some basic configurations, abstracted network management systems can't be used to dynamically program or automate a network of multi-vendor devices, which is the ultimate goal of SDN.

[ ALSO SEE: Five needs driving SDNs ]

* Open SDN architectures represent a fundamental change in networking architectures. An open SDN introduces centralized software controllers that implement a common data plane abstraction that unifies the entire network fabric southbound, and publishes open APIs for software applications northbound. With this open architecture, a fabric of multi-vendor devices can be aggregated into a single policy domain that can be programmed and automated using standard software (not CLI).

Open SDN architectures leverage an industry standard data plane abstraction protocol, like OpenFlow, which provide direct access to the data plane hardware and forwarding flow tables -- not just a CLI proxy mechanism. And, OpenFlow can operate across a variety of physical and virtual switches, as well as vendor architectures. As a result, it is now possible for an Open SDN controller to program and automate a multi-vendor network using standard software protocols, like OpenFlow and RESTful APIs. Importantly, network virtualization becomes just one of many applications possible with an open SDN architecture.

As customers consider moving toward SDN they will need to consider what functional and architectural benefits best meet their needs. Does a pure tunnel-oriented virtualization architecture meet their scalability and broader application needs? Is a proprietary network architecture acceptable? Or, do they want to evolve toward an open architecture comparable to what they experience today in the server world?

These and other questions should customers help guide their decision-making process in the powerful new era of software-defined networking.

Big Switch Networks is the leader in Open Software-Defined Networking. The company's Open SDN platform embraces industry standards, open APIs, open source, and vendor-neutral support for both physical and virtual networking infrastructure. Big Switch Networks Open SDN Suite supports a broad range of networking applications, including network virtualization for public and private cloud data centers built OpenStack, CloudStack and other platforms. For additional information follow us @bigswitch or visit: bigswitch.comA

Read more about lan and wan in Network World's LAN & WAN section.

This story, "Making Sense of the Myriad SDN Offerings" was originally published by Network World.

Copyright © 2013 IDG Communications, Inc.

Discover what your peers are reading. Sign up for our FREE email newsletters today!