Why not fcoe

The only realistic way to do this in the data center to date has been to build a Large, Flat Layer-2 Network. I make the claim that no smart network operator would prefer a large flat layer-2 network over a L3 routed ECMP design.

I suppose many people with the surname 'Anon' and an IP address beginning with So with FCOE we have a technology that seems to be only taking off in the proprietary compute systems offered by a single emerging server vendor - Cisco. It requires a complete network upgrade, special purpose NICs, a new network architecture that no smart network operator would prefer, and doesn't work with any technology that enables stateful VM live migrations which are the main driver for flatter networks in the first place.

Here are the latest Insider stories. More Insider Sign Out. Sign In Register. Sign Out Sign In Register. Latest Insider. Check out the latest Insider stories here.

More from the IDG Network. Tablet deathmatch: HP TouchPad vs. Apple iPad 2. The cheaper I can store all my bits the better - cue better areal densities, tape pundits, etc. Join the Network World communities on Facebook and LinkedIn to comment on topics that are top of mind. Our architects are happy to provide free design assistance for full scale data centers, colo-space, and upgrades. Learn more about how and why to buy from us here. Talk with an Expert Get a quote Contact Us. What is FCOE?

A Brief Overview. Data Center Cabling Solutions. FCOE creates a lower entropy system by merging fiber channel with Ethernet. You Can Share It :. Facebook Twitter Google. Latest Posts. For Cisco this means buying a Cisco Nexus , and possibly Nexus as edge devices. Compare this to iSCSI where you CAN use your existing Ethernet infrastructure and progressively plan an upgrade to new hardware, possibly around the Cisco Nexus as a core switch and the upgrade path is much more organic, and fit into existing budgeting and project processes.

Take the time to research why many people are FC biased, and you will often find that its historical. One of the most hidden, least realised and unknown shortcomings of FCoE is the lack of scale. That is, we cannot create data centres using Ethernet VLANs with more than fifty to a hundred switches before we lose stability.

Note this is also true for Fibrechannel, however, data centres with more than fifty FC switches in a single network is exceptional…and unlikely. There are two possibilities here, either its a low cost way of scaling the Nexus to meet customer requirements or its an admission that FCoE cannot scale and the need to keep L2 switch domains very small is high priority. This might be less of a problem if we can use very large switches, but building lossless, low latency, Fibrechannel-capable is a really expensive proposition.

Therefore, just like Fibrechannel, Ethernet storage networks will mostly consist of small switches for storage connections only. Evidence: The path to FCoE is not certain. Be smart and make your own choices by considering what will work in your Data Centre. FCoE is by no means the default or only choice for storage networking, and I believe it will be optional for the vast majority of the computer rooms because of late standards, high cost and significant learning curve.

This may mean that FCoE will only ever be a niche technology for legacy FC platform integration and not as a standalone high performance technology. Network Break is round table podcast on news, views and industry events. Join Ethan, Drew and myself as we talk about what happened this week in networking. In the time it takes to have a coffee.

Why did someone bother to create FCoE? A bit of Fibrechannel History Fibrechannel was designed as a block transport protocol to support lossless and low latency transfer of data across a data network.

Why is it a Layer 2 technology? Why is Fibrechannel still important? Is Fibrechannel Dead? Storage versus Networks It seems to me, that the motivation of the storage vendors to create and use FC was to create a proprietary protocol that only they supported. This will require a change in data networking Why not choose Ethernet or IP at that time? Wasted bandwidth has never been a problem. The Internet itself is testimony to this. So, who cares about throughput? FCoE lacks key standards At time of writing, the only FCoE implementations come from Cisco and you require a full networking implementation from Cisco.

Note this is also true for Fibrechannel, however, data centres with more than fifty FC switches in a single network is exceptional…and unlikely Does this really matter? Conclusion The path to FCoE is not certain. Network Break Podcast Network Break is round table podcast on news, views and industry events.