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

News Analysis  

NEC Lends Microsoft a Hand in SDN

January 22, 2013 | Craig Matsumoto |
NEC Corp. has launched a virtual switch supporting OpenFlow 1.0, bringing OpenFlow into the Microsoft Corp. virtual-networking environment.

The new ProgrammableFlow PF1000, launched to general availability on Tuesday, is analogous to VMware Inc.'s vSwitch, or Cisco Systems Inc.'s ASR 1000v, in that it's a software construct that handles switching between virtual machines. Target uses include data-center and cloud applications.

The PF1000 runs on Hyper-V, the hypervisor Microsoft has created to compete with VMware's. NEC also claims it's the first virtual switch running OpenFlow. The PF1000 can support 1,280 ports (combining virtual and physical switch ports) and 260,000 data flows, NEC claims.

At the same time, NEC announced a ProgrammableFlow upgrade that includes IPv6 and OpenStack support.

Why this matters
VMware doesn't offer OpenFlow on virtual switches, as Roy Chua of SDNCentral points out in his analysis. (It does have a workaround, as detailed on the IP Space blog.)

So, this is actually a nice announcement for Microsoft, giving Hyper-V something to brag about versus VMware's ESXi.

On NEC's side, the company's ProgrammableFlow line of switches now has increased relevance in the cloud.

NEC's moves don't make or break the switching market, since the company's sales remain mostly in Japan -- but ProgrammableFlow is meant to change all that, by using OpenFlow and SDN as levers. NEC did announce one customer for the PF1000, and it's not based in Japan: Edgenet Inc., which develops sales engines for online retailers.

Lately, a lot of talk around SDN has emphasized the need to support protocols other than OpenFlow, but NEC insists that OpenFlow's importance hasn't diminished. "The customers we talk to see the investment protection of OpenFlow being a lot more solid than any particuar promise by any particular vendor," says Don Clark, NEC's U.S. director of business development.

For more

— 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.
 
White Papers SPONSORED CONTENT
Featured