Light Reading Mobile – Telecom News, Analysis, Events, and Research

Valley Wonk  
Craig Matsumoto

SDN & the Commodity Question

November 14, 2012 | Craig Matsumoto |

6:00 PM -- I know a lot of people are waiting for software-defined networking (SDN) to bring down the Cisco Systems Inc. empire. Waiting for OpenFlow to commoditize network hardware into the ground.

I get asked about that all the time. I just don't see it happening in the short term.

In the long term, I'm less sure.

The seeds are certainly there. OpenFlow allows a controller to dictate commands to switches; ergo, the switches can be dumb and simple, so the argument goes. The possibilities aren't lost on the new SDN companies -- a Big Switch Networks presentation linked to its commercial launch Tuesday repeatedly mentioned "low-cost Ethernet Switches" as its target devices.

The ingredients are out there, too. Intel Corp., at its recent developer forum, released a DIY kit for a commodity server. It uses Fulcrum Microsystems switch chips, Xeon processors and software from Wind River (well, a Linux kernel anyway).

But commoditization of the hardware is not an easy process for the customers, because right now, you can buy a network and have someone else (usually Cisco) do a lot of the work for you. Assembling your own network out of generic Made-in-Taiwan switches might be fun for Google, but it did take a lot of work.

And the switches still have to perform. I like the basketball analogy posed by Simon Leopold, an analyst with Raymond James Financial Inc., in an SDN report he issued this week: "Imagine how poorly a team would perform if after each pass, the team paused to consult the coach. Rather, the coach provides the general strategy and guidance yet leaves the execution to the team."

There's also the fact that the hardware won't necessarily be cheap. OpenFlow was designed to exploit a router's ternary content-addressable memories (TCAMs), a specialized and costly type of chip. And OpenFlow 1.2 potentially increases the amount of TCAM space you'll need.

So many signs seem to point away from commoditization. And yet -- I can't bring myself to bet against easy and cheap. At the moment, SDN doesn't have either trait on its side, but a lot of people are going to be working to change that.

For what it's worth, the SDN executives whom LRTV spoke to recently don't think hardware vendors are in imminent danger (caveat: two of them are hardware vendors), and Ankur Singla, CEO of Contrail Systems, even cites Cisco and Juniper Networks Inc. as being well poised to break away into a software-dominated future. He's got a point.

Software defined networking presents some challenges for hardware vendors. We've discussed SDN's impact with execs from Contrail Systems, Extreme Networks, vArmour, Embrane and HP

— Craig Matsumoto, Managing Editor, Light Reading



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
More Valley Wonk
The Case for Flexibility Beyond 100G
Comcast joins Google in asking for a flexible-rate optical standard, rather than 400G or terabit, but that's easier said than done
Virtualization Takes the Stage at Interop
Cisco, Juniper and other more traditional Interop speakers might get overshadowed by the forces of virtualization
SDN Still Needs a Gathering Like ONS
The Open Networking Summit has climbed the hype curve, but the conference should cling to its roots as a techie discussion forum for software-defined networking
What OpenDaylight Really Wants to Do
The coalition's chairman says all these companies plan to further the SDN cause and don't have a 'nefarious' angle
Cisco Sees Daylight for SDN
Big vendors are reportedly banding together to unify SDN's approach but is it more about steering the conversation?
White Papers SPONSORED CONTENT
Featured