Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

12/21/2009
04:32 PM
George Crump
George Crump
Commentary
50%
50%

2010 Year Of Fibre Channel-Over-Ethernet?

Will 2010 be the year of Fibre Channel-Over-Ethernet (FCoE)? I am always hesitant to predict that any particular year with be "the year" but I do think that FCoE will move out of conversation and testing phases and more into production.

Will 2010 be the year of Fibre Channel-Over-Ethernet (FCoE)? I am always hesitant to predict that any particular year with be "the year" but I do think that FCoE will move out of conversation and testing phases and more into production.When it comes to something like infrastructure, changes come relatively slowly. The upgrade of previous storage infrastructures all came slowly and often did not occur until the new version of the infrastructure was the same price and the prior version. 2GB FC to 4GB FC as an example. There are three reasons why I think the switch to FCoE as a protocol of choice may come faster than previous infrastructure upgrades.

First FCoE like other infrastructure upgrades is a relatively seamless move, not much changes from a protocol perspective; the storage FC side is still managed the same as is the IP side. While FCoE does require new cards, cables and switches it does not require many new skills. Those cards, cables and switches are going to be purchased anyway as the environment expands. The decision point is will they be FCoE or the current protocol?

Second FCoE is ideally suited to be the infrastructure of choice for server virtualization projects where the limitations of a lack of a consolidated infrastructure are most telling. With the typical virtual host having two or four quad-port ethernet ports and typically two dual ported FC cards, the cable count in a rack of these servers quickly becomes a nest of unmanageable spaghetti. FCoE can reduce the size of that mess considerably.

Third there may be a more universal need for performance than we have seen in the past. Previous speed bumps in infrastructure were only needed by a few organizations that were pushing the envelope of performance. Other organizations simply got the performance boost as the new infrastructure became as inexpensive as the old. Now however, thanks again to server virtualization, data centers of all sizes are generating performance requirements that are saturating existing infrastructures.

Will 2010 be the year for FCoE? Certainly companies like Brocade, Cisco, Emulex and QLogic are all offering mature FCoE technology. However, as we discussed in our article "Planning for FCoE", most data centers are not going to do a wholesale change out to the protocol, it will be more of a gradual roll in. Many of these manufacturers are banking on 2011 to the "the year".

My opinion is that it will take five or more years for FCoE to become the dominant infrastructure in the data center but that each year we will see progress toward that domination. In truth however we will likely never be at a point where FCoE is the only infrastructure used. There will simply be too many point cases where other technology, like faster dedicated IP, faster dedicate FC or even I/O virtualization, may be more appropriate.

IT managers would be well advised to begin production deployments of FCoE in the coming year but to do so gradually as the need warrants. With a gradual roll out of the technology however it is important to make sure the vendors that supply your FCoE infrastructure continue to support the dedicated versions of the protocols. Finally keep your eyes open on I/O Virtualization which may be a cost effective alternative.

Track us on Twitter: http://twitter.com/storageswiss

Subscribe to our RSS feed.

George Crump is lead analyst of Storage Switzerland, an IT analyst firm focused on the storage and virtualization segments. Find Storage Switzerland's disclosure statement here.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-23381
PUBLISHED: 2021-04-18
This affects all versions of package killing. If attacker-controlled user input is given, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23374
PUBLISHED: 2021-04-18
This affects all versions of package ps-visitor. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23375
PUBLISHED: 2021-04-18
This affects all versions of package psnode. If attacker-controlled user input is given to the kill function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23376
PUBLISHED: 2021-04-18
This affects all versions of package ffmpegdotjs. If attacker-controlled user input is given to the trimvideo function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.
CVE-2021-23377
PUBLISHED: 2021-04-18
This affects all versions of package onion-oled-js. If attacker-controlled user input is given to the scroll function, it is possible for an attacker to execute arbitrary commands. This is due to use of the child_process exec function without input sanitization.