In a recent review, I wrote about consolidating FC and Ethernet networks using FCoE (Fibre Channel over Ethernet) and Cisco's new Nexus 5000 switch. As the review showed, the solution merges the two transport protocols easily, allowing FC frames to navigate through a 10 Gig Ethernet connection without giving up features or performance.
Add a CNA (converged network adapter) to a server, and you can give your applications easy access to FC storage attached to a converged network. Essentially a 10 Gig Ethernet NIC with a split FC personality, the CNA plays both roles at once, which brings several financial and practical benefits.
But what wasn't explicitly addressed in the review is FCoE's effect on server virtualization. For example, what happens when you bring together VMware ESX, VMotion, and FCoE? Is there any advantage over the traditional FC approach?
Emulex made its Demo lab available to me to help answer those questions. The lab included three VMware ESX servers connected to a fabric network using either old-fashioned FC cards or the new CNA.
This annotated topology map (please click here for a larger image) taken with Cisco Fabric Manager, shows my test bed. On the left are the FCoE players, an ESX server with an Emulex LP21000 CNA, and connected to it, the Cisco Nexus 5000 switch.
On the right side are the FC devices with two ESX servers, each mounting Emulex LPe11000 adapters, and connected to the Cisco MDS switch.
The yellow line shows the path from the test VM (middle) to the MDS switch and then to its storage devices.
One side note: The Emulex adapters implement NPIV (N_Port ID virtualization), a useful feature that provides each VM with a virtual WWN (worldwide name). NPIV is a much more flexible alternative to having only one WWN assigned to the ESX server, and shared by all its VMs.
Using VMotion, it was a snap to move the test VM from the original server to the CNA-equipped ESX server, while maintaining access to its LUNs -- handy, should you want to perform maintenance on the original ESX server or balance the load across the two. Once again, the server on the left doesn't have native FC adapters, only a CNA.
I had intended to post a movie clip of the test VM moving to the new ESX server using VMotion, but the action lasted only a few seconds. Not much of a movie, but that's how long it took to drag the test VM from one ESX server to another, working on the VMware Infrastructure Client (the green arrow, top left on the image link, indicates the direction of the move).