Commentary

Terry Sweeney
 

FCoE Enigma Wrapped In A Riddle

And buried inside a mystery: It's where my mind goes when the subject turns to Fibre Channel over Ethernet (FCoE). And apparently I'm not alone.

And buried inside a mystery: It's where my mind goes when the subject turns to Fibre Channel over Ethernet (FCoE). And apparently I'm not alone.As I understand it, FCoE is a way for SCSI-based block traffic to look more like Fibre Channel, which must be a nod to the demand that any storage network additions play well with the installed base of FC and all its management tools. FCoE also holds out the promise of running traffic over Ethernet -- allegedly a less expensive fabric than FC. To state the glaringly obvious, FCoE doesn't do much to reduce storage complexity, despite all the masking or transparency to those in the data center.

This alphabet soup only looks to get more muddled and acronym-laden as enterprises try extend storage networks across the wide area with Fibre Channel over IP (FCIP), some form of wavelength division multiplexing (WDM), or Sonet/SDH.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Are storage customers really going to put up with this kind of complexity? Or will they simply choose not to afford it? We won't know for at least a year, since that's when the first FCoE products are forecast to hit the streets.

Maybe Brocade has the answer in its new DCX backbone switch, essentially a chassis for whatever network type or storage protocol you want to blend. All yours from Sun, starting at $179,000. Ouch.

You want lots of encapsulation, translation, and protocol conversions in your storage networks? That's fine, the vendors appear to be saying. Just as long as you're prepared to pay.


Related 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

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek 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. InformationWeek 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.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links