Mike Fratto

Network Computing Editor


Upcoming Events

Where the Cloud Touches Down: Simplifying Data Center Infrastructure Management

Thursday, July 25, 2013
10:00 AM PT/1:00 PM ET

In most data centers, DCIM rests on a shaky foundation of manual record keeping and scattered documentation. OpManager replaces data center documentation with a single repository for data, QRCodes for asset tracking, accurate 3D mapping of asset locations, and a configuration management database (CMDB). In this webcast, sponsored by ManageEngine, you will see how a real-world datacenter mapping stored in racktables gets imported into OpManager, which then provides a 3D visualization of where assets actually are. You'll also see how the QR Code generator helps you make the link between real assets and the monitoring world, and how the layered CMDB provides a single point of view for all your configuration data.

Register Now!

A Network Computing Webinar:
SDN First Steps

Thursday, August 8, 2013
11:00 AM PT / 2:00 PM ET

This webinar will help attendees understand the overall concept of SDN and its benefits, describe the different conceptual approaches to SDN, and examine the various technologies, both proprietary and open source, that are emerging. It will also help users decide whether SDN makes sense in their environment, and outline the first steps IT can take for testing SDN technologies.

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

See more from this blogger

Brocade, Cisco, End-to-End FCoE And Who's On First

I took some heat, in a good natured way, about my article Brocade First To Market With Native End-to-End FCoE . Brad Hedlund, Brian Gracely, and Stu Miniman contend that Cisco is first with end-to-end FCoE. In my original story, the headline "Brocade First To Market With Native End-to-End FCoE" was inaccurate. After talking to Brocade and Cisco in depth, the more accurate title is "Brocade First To Market With End-to-End Ethernet FCoE." I was sort of right and sort of wrong. Let me explain.

In July 2010, Cisco announced that its Nexus 5000 family was the first to support end-to-end FCoE. While Cisco uses FCoE at the edge and FC between switches, this is compliant with Fibre Channel standards because FC-BB-5, the standard defining FC over a different layer-two protocols, doesn't say that the end-to-end connection has to be FCoE. The standard only specifies how FCoE should work when it is used. Vendors are free to do whatever they want between switches, provided that FC requirements such as lossless operation are preserved and that FC frame order is maintained. In this case, Cisco's claim to be first with end-to-end FCoE is correct, but they sprinkle some FC in the middle.

In the next maintenance release of the Nexus 5000 NX-OS, Cisco will support FCoE layer 2 links between switches. The feature is available today, but it is an unsupported configuration which customers can use to trial FCoE. But even in that case, the Nexus 5000, which is a Fiber Channel Forwarder, will still have to de-capsulate the FCoE frame, process it as FC, and encapsulate it back into FCoE before sending it along to its next hop. J. Michel Metz, FCoE program manager for Cisco, says the encaps/decaps is necessary for FC processing. I am taking his word on it. I have hit the end of my understanding at the moment. Hah.

Brocade is correct in saying that VDX is the first Ethernet end to end FCoE product suite. Brocade's architecture--and some of this will have be figured out once product is shipping--works like this. Instead of processing each frame through a fiber channel forwarders (FCF) at each hop, Brocade uses a Virtual Chassis Switch (VCS) to distribute the intelligence among all the switches. Once the route decision is made at the VDX network ingress point using Fabric Shortest Path First (FSPF)--which Cisco also uses on the Nexus 5000--the frame is sent along. This appears to be standard operating mode in light of FC-BB-5 (clause 7.5 in particular).

Brocade also does some magic by using equal-cost links at a more granular level than per flow. Remember that FC is just SCSI frames running over a network and FC assumes that the fabric is lossless, has low latency and jitter, and frames always arrive in order. Ethernet is the opposite. Loss due to congestion is built in by design while handling delay, jitter, and order is left to upper layer protocols, if needed. Cisco's Nexus 5000 uses equal cost multi-pathing at the flow level, ensuring that each FC or FCoE frame in a flow--a distinct connection between two nodes--always traverses the same path, or in the event of a failure, an equal cost path. This ensures that order is maintained. Brocade's VCS uses multiple paths at the frame level, meaning the same flow can be distributed across multiple links, which Brocade does for FC as well. That means Brocade has to ensure that frames are sent to the end node in the proper order, because mis-ordered frames in FC can cause corruption.


Page:  1 | 2  | Next Page »


Related Reading


More Insights


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. | Please read our commenting policy.
 
Vendor Comparisons
Network Computing’s Vendor Comparisons provide extensive details on products and services, including downloadable feature matrices. Our categories include:

Research and Reports

Network Computing: April 2013



TechWeb Careers