Access your Pro+ Content below.
End-to-end FCoE for network convergence won't work!
This article is part of the December 2011 Vol. 2, No. 6 issue of Network Evolution
In the first part of this face-off on FCoE network convergence, Stuart Miniman discussed FCoE starting at the edge then moving into the rack. In this second part, storage and networking expert, Stephen Foskett argues that FCoE at the edge might be a step toward network convergence, but end-to-end FCoE needs a lot more engineering and isn't reliable. All last year I watched storage and networking vendors twisting and turning to convince the world they have delivered an end-to-end FCoE protocol. In fact, the products they released are largely inadequate. What’s more, they’ve never addressed the burning question: Why bother with an end-to-end strategy for network convergence when the FCoE protocol at the edge is more practical? It’s important to first note that moving enterprise storage traffic to Ethernet networks seems like a match made in hell. The SCSI protocol requires delivery of packets that are lossless and in order, but Ethernet was designed for “best effort” delivery. This won’t cut it for storage, which is a high-volume ...
Access this Pro+ Content for Free!
Features in this issue
Trying to decide cellular vs. Wi-Fi for mobile devices? An enterprise wireless connection policy will help steer mobile devices to the right network.
News in this issue
Hotspot 2.0 and the IEEE 802.11u protocol could allow mobile device users to securely roam between Wi-Fi and cellular networks without stopping to authenticate.
Implementing FCoE network convergence is possible considering the move to 10 GbE and the emergence of data center bridging.
FCoE at the edge can be a step toward network convergence, but end-to-end FCoE needs a whole lot more engineering before it can be reliable.
Think VM mobility and follow-the-sun data centers work for high availability and disaster avoidance? Think again. Long-distance migration is still a problem.