Upcoming Events

Cloud Connect
Santa Clara
Feb 13-16, 2012

Cloud Connect brings together the entire cloud eco-system to better understand the transformation we're experiencing and promises to be the defining event of the cloud computing industry. Learn about the latest cloud technologies and platforms from thought leaders in Cloud Connect’s comprehensive conference.

Register Now!

More Events »

Subscribe to Newsletter

  • Keep up with all of the latest news and analysis on the fast-moving IT industry with Network Computing newsletters.
Sign Up

Email Email  Print  Share


Xsigo Goes Ethernet

Tags: , , , ,

Channel: Data Center, Networking & Mgmt, Next Gen Network, Servers & Storage

The all-Ethernet data center took a step forward this week with Xsigo's introduction of its Ethernet-based IOV solution at VMworld. Xsigo is hardly the first vendor to introduce I/O Virtualization solutions based on Ethernet, which have been advocated for sometime by Aprius, Virtensys and Next I/O. Xsigo is the first vendor, however, to use the existing Ethernet adapter within the server to connect with the external card cage that houses the I/O adapter. Other solutions require replacing the adapter with a proprietary host bus adapter.

By not replacing the card within the server, Xsigo claims to dramatically reduce the time and complexity needed to enter into IOV. Data center managers need to simply plug-in the server to Xsigo's external chassis, load Xsigo's proprietary drivers and then enable IOV as needed. Xsigo contends that with competing solutions, data center managers would need to schedule server downtime, shut down server, remove cabling, de-rack the server, remove existing I/O and install new card and then re-rack server, install cabling, bring server up, load drivers, re-map I/O resources and bring applications back up.

"Be reasonable here," says Craig Thompson, vice president of marketing at Aprius "any virtual I/O infrastructure requires some modification of the environment; you're eliminating cards from servers as part of the move to pooling I/O, so you can't realize the efficiencies of virtual I/O in installed servers without touching some aspect of the server I/O."

In fact, the Xsigo approach may not necessarily require cards to be eliminated from servers; Xsigo just requires expensive, proprietary I/O  modules in the external card cage. But giving up on that simplicity of deployment also comes at a high price. Xsigo wouldn't say how much the actual I/O adapters cost for its solutions, but did say the VP560 external chassis, which includes thirty-two 10GbE ports, four IO modules and up to forty uplink ports, starts at $35,000. The larger VP780 includes thirty-two 10GbE ports, up to fifteen IO modules and up to 150 uplink ports starting at $45,000. By contrast Aprius uses existing PCI cards.

Still Xsigo's move is important in a number of ways. Two months ago, we criticized the Dell-Xsigo  partnership for all that it wasn't yielding. We argued at the time that Infiniband, while used within storage environments, didn't reflect the reality of most data centers. The introduction of an Ethernet solution addresses that challenge for Xsigo allowing it to play in both the very high and mid-range IOV markets. For Xsigo competitors, the introduction will complicate their pitches significantly. Xsigo is no longer "the Infiniband" solution, making differentiation more difficult. Perhaps the play on this front will need to revolve around standards adoption and price, two areas where Xsigo remains weaker.

Related Stories

Related Reading


More next-gen-network Insights



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.
 

Next Gen Network Reports

Premium Content

Research and Reports

Hypervisor Derby
August 2011

Network Computing: August 2011

TechWeb Careers